From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
npiggin@kernel.dk
Subject: Re: Linux 2.6.38-rc5
Date: Wed, 16 Feb 2011 16:39:51 +0000 [thread overview]
Message-ID: <20110216163951.GG22723@ZenIV.linux.org.uk> (raw)
In-Reply-To: <AANLkTi=8O1ZJZ2dWWwmcdV3G8LtrxSHWp=GgLxAYQE3A@mail.gmail.com>
On Wed, Feb 16, 2011 at 08:33:32AM -0800, Linus Torvalds wrote:
> Does it make tons of conceptual sense to pass in 'inode' to
> do_follow_link? No, it's clearly redundant information, which is the
> whole point of the BUG_ON(). But it does allow that extra shared
> sanity test, and we _could_ also then do
>
> - if (!IS_ERR(cookie) && path->dentry->d_inode->i_op->put_link)
> - path->dentry->d_inode->i_op->put_link(path->dentry,
> nd, cookie);
> + if (!IS_ERR(cookie) && inode->i_op->put_link)
> + inode->i_op->put_link(path->dentry, nd, cookie);
>
> since we've verified that 'inode' is 'path->dentry->d_inode', and all
> of those should be stable over all the calls (in the non-RCU case,
> which we are in).
>
> I dunno. I don't care _deeply_, but I do have to say that I much liked
> how you moved the
>
> if (nameidata_dentry_drop_rcu_maybe(nd, path->dentry))
> ..
>
> into do_follow_link(). I think it made it clearer that do_follow_link
> (and __do_follow_link()) aren't done with RCU.
OK, I can live with that. Consider me convinced, let's go with your variant.
Speaking of ugliness: Nick, why the _fuck_ have you reverted non-create case
in do_filp_open() to do_path_lookup()?
next prev parent reply other threads:[~2011-02-16 16:39 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 4:16 Linux 2.6.38-rc5 Linus Torvalds
2011-02-16 11:14 ` Eric Dumazet
2011-02-16 13:55 ` Eric Dumazet
2011-02-16 15:46 ` Linus Torvalds
2011-02-16 16:06 ` Al Viro
2011-02-16 16:19 ` Al Viro
2011-02-16 16:33 ` Linus Torvalds
2011-02-16 16:39 ` Al Viro [this message]
2011-02-16 16:47 ` Eric Dumazet
2011-02-16 16:22 ` Eric Dumazet
2011-02-16 19:26 ` [PATCH] fix backlight brightness on intel LVDS panel after reopening lid Alex Riesen
2011-02-16 19:46 ` Alex Riesen
2011-02-16 19:54 ` Jesse Barnes
2011-02-16 19:59 ` Alex Riesen
2011-02-16 20:05 ` Jesse Barnes
2011-02-16 20:28 ` Alex Riesen
2011-02-17 1:41 ` [PATCH] drm/i915: Do not handle backlight combination mode specially Indan Zupancic
2011-02-17 22:13 ` [PATCH] fix backlight brightness on intel LVDS panel after reopening lid Tino Keitel
2011-02-18 4:57 ` Indan Zupancic
2011-02-19 12:11 ` Alex Riesen
2011-02-19 12:26 ` Alex Riesen
2011-02-19 23:07 ` Linus Torvalds
2011-02-22 21:04 ` Jesse Barnes
2011-02-22 22:31 ` Tino Keitel
2011-02-23 1:09 ` Linus Torvalds
2011-03-04 6:53 ` Indan Zupancic
2011-03-04 18:47 ` Linus Torvalds
2011-03-04 23:32 ` Indan Zupancic
2011-03-06 17:40 ` Alex Riesen
2011-03-10 5:50 ` Indan Zupancic
2011-03-10 6:00 ` Indan Zupancic
2011-03-10 7:49 ` Takashi Iwai
2011-03-10 8:25 ` Takashi Iwai
2011-03-10 10:06 ` Indan Zupancic
2011-03-10 12:59 ` Takashi Iwai
2011-03-10 13:02 ` [PATCH] drm/i915: Revive combination mode for backlight control Takashi Iwai
2011-03-10 19:36 ` Keith Packard
2011-03-11 1:30 ` Indan Zupancic
2011-03-11 1:23 ` Indan Zupancic
2011-03-11 1:28 ` Linus Torvalds
2011-03-11 7:26 ` Takashi Iwai
2011-03-11 9:08 ` Indan Zupancic
2011-03-11 7:34 ` Keith Packard
2011-03-10 8:45 ` [PATCH] fix backlight brightness on intel LVDS panel after reopening lid Indan Zupancic
2011-03-10 12:51 ` Takashi Iwai
2011-03-05 0:26 ` Peter Stuge
2011-02-23 1:32 ` Indan Zupancic
2011-02-20 14:03 ` Linux 2.6.38-rc5 Paul Rolland
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=20110216163951.GG22723@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=torvalds@linux-foundation.org \
/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