From: Linus Torvalds <torvalds@linux-foundation.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Alexey Dobriyan <adobriyan@gmail.com>,
ebiederm@xmission.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.27-rc7-sha1: EIP at proc_sys_compare+0x36/0x50
Date: Sun, 28 Sep 2008 13:59:33 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0809281355540.3265@nehalem.linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0809281350410.3265@nehalem.linux-foundation.org>
On Sun, 28 Sep 2008, Linus Torvalds wrote:
>
> NOTE! Totally untested patch! It looks sane and really obvious, but maybe
> it has some insane and non-obvious bug.
Oh. I think I see at least a _potential_ insane and non-obvious bug: if
somebody actually is going to do a __d_drop() _inside_ their d_compare(),
this would fail horribly because we now assume that the dentry is still
fine, since we held d_lock.
Of course, I think that would be very very buggy of a filesystem to do (we
don't even pass in the dentry as an argument - you have to figure it out
from the qstr, and a filesystem really should not do that!), but /proc
_does_ look up the dentry in question, maybe some other insane filesystem
does too and then does the __d_drop.
I'm not seeing it, though. So I still think the patch is sane and good,
but somebody really needs to double- or triple-check me on it.
Linus
next prev parent reply other threads:[~2008-09-28 21:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 15:20 Alexey Dobriyan
2008-09-26 15:47 ` Linus Torvalds
2008-09-27 8:44 ` Eric W. Biederman
2008-09-28 20:38 ` Linus Torvalds
2008-09-28 14:18 ` Al Viro
2008-09-28 19:28 ` Hugh Dickins
2008-09-28 20:55 ` Linus Torvalds
2008-09-28 20:59 ` Linus Torvalds [this message]
2008-09-28 22:07 ` Hugh Dickins
2008-09-29 3:05 ` Eric W. Biederman
2008-09-28 20:46 ` Linus Torvalds
2008-09-28 20:50 ` Linus Torvalds
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=alpine.LFD.1.10.0809281355540.3265@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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
Powered by JetHome