[lkml]   [2002]   [Apr]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [WTF] ->setattr() locking changes

On Sat, 6 Apr 2002, Alexander Viro wrote:
> a) where the hell is update to Documentation/filesystems/* ?
> b) Dave, meet grep. grep, meet Dave. Have a happy relationship...

Al, don't blame Dave, blame me. I told Dave to use i_sem instead of a
special semaphore, just because it seems to be the right thing.

> _Please_, grep before doing global changes. Trivial search for
> notify_change() would show several calls under ->i_sem. E.g. one
> in fs/nfsd/vfs.c. Or in hpfs_unlink().

Hmm.. I don't think the fs/nfsd/vfs.c case is "obviously" under i_sem.
Certainly not from grepping. Where?

The hpfs/namei.c one definitely needs the removal of the up/down, though.
Altghough for the life of me I don't see why the filesystem _does_ that at
all, since it should have been done by the upper layers already, no?

Oh, and Andrew pointed out that in the ext3 case the BKL was forgotten.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:25    [W:0.053 / U:6.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site