Thread (2 messages) 2 messages, 2 authors, 2008-09-22

Re: [PATCH 1/10] VFS: Fix error handling ofwrite_super_lockfs/unlockfs

From: Takashi Sato <hidden>
Date: 2008-09-22 12:52:33
Also in: dm-devel, linux-fsdevel, linux-xfs, lkml

Hi,
On Mon, Sep 22, 2008 at 07:55:26PM +0900, Takashi Sato wrote:
quoted
I've changed the type of write_super_lockfs and unlockfs from "void" to
"int" so that they can return an error.
Returning an error from the freeze operation makes sense, but for the
unfreeze I don't see the point.  You must however change all existing
instances to actually return a value (even if it's always 0 for now)
to avoid breaking git bisect.
I thought unlockfs should return an error because ext3_unlockfs()
might cause I/O error in writing a super block.
But it is an internal error and the unfreezing succeeds.
So I will consider returning 0.
If you touch all instances anyway, it would be nice to rename them
to freeze / unfreze as the current names are more confusing.
I will consider renaming.

Cheers, Takashi
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help