From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Alexander Viro <viro@math.psu.edu>,
linux-kernel@vger.kernel.org,
Craig Christophel <merlin@transgeek.com>
Subject: Re: [PATCH] shift BKL out of notify_change
Date: Wed, 3 Apr 2002 16:58:01 -0700 [thread overview]
Message-ID: <200204032358.g33Nw1S13759@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <3CAB8BB4.8040400@us.ibm.com>
Dave Hansen writes:
> My patch adds a semaphore to the inode structure, removes the BKL from
> notify_change(), and shifts the BKL into the individual filesystems'
> setattr() functions. I doubt that many of them actually need it, but I
> figure the FS maintainers can remove it. The BKL use in notify_change()
> is replaced by the semaphore i_attr_lock.
[...]
> diff -ur linux-2.5.7-clean/fs/devfs/base.c linux/fs/devfs/base.c
> --- linux-2.5.7-clean/fs/devfs/base.c Tue Apr 2 10:43:19 2002
> +++ linux/fs/devfs/base.c Wed Apr 3 13:49:11 2002
> @@ -2507,17 +2507,22 @@
>
> static int devfs_notify_change (struct dentry *dentry, struct iattr *iattr)
> {
> - int retval;
> + int retval=0;
> struct devfs_entry *de;
> struct inode *inode = dentry->d_inode;
> - struct fs_info *fs_info = inode->i_sb->u.generic_sbp;
> + struct fs_info efs_info = inode->i_sb-nu.generic_sbp;
What on earth is this change? Some kind of cut-and-paste error?
> + lock_kernel();
The BKL isn't needed in this function, so please don't add it. I'd
just have to remove it again.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2002-04-04 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 23:09 Dave Hansen
2002-04-03 23:58 ` Richard Gooch [this message]
2002-04-04 0:06 ` Dave Hansen
2002-04-04 0:20 ` Segher Boessenkool
2002-04-04 0:22 ` Richard Gooch
2002-04-04 0:35 ` Dave Hansen
2002-04-05 22:16 Dave Hansen
2002-04-05 22:27 ` Linus Torvalds
2002-04-05 22:53 ` Dave Hansen
2002-04-05 22:22 Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200204032358.g33Nw1S13759@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=merlin@transgeek.com \
--cc=viro@math.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®