From: Andrew Morton <akpm@linux-foundation.org>
To: Jeff Mahoney <jeffm@suse.com>
Cc: "Vladimir V. Saveliev" <vs@namesys.com>,
a.righi@cineca.it, linux-kernel@vger.kernel.org,
reiserfs-dev@namesys.com, Edward Shishkin <edward@namesys.com>,
zam@clusterfs.com
Subject: Re: Fwd: Fw: [2.6.20.4] BUG: dentry xattrs still in use in shrink_dcache_for_umount() with reiserfs
Date: Fri, 20 Apr 2007 17:07:38 -0700 [thread overview]
Message-ID: <20070420170738.e269fcae.akpm@linux-foundation.org> (raw)
In-Reply-To: <46263270.9010108@suse.com>
On Wed, 18 Apr 2007 11:00:00 -0400
Jeff Mahoney <jeffm@suse.com> wrote:
> > Do you think that could be a reason of the extra reference count on xattr_root dentry?
>
> No, I don't think it is. Looking at the code now, it seems obvious, but
> I didn't notice it before and nobody else has reported a problem.
>
> getxattr() doesn't require any VFS locking. When we get down into the
> reiserfs code, it takes a read lock. If we get two concurrent threads
> looking up an xattr before the root has been saved, there's a window
> where REISERFS_SB(s)->xattr_root is NULL but we've already looked it up
> and taken a reference on it.
>
> I have a patch set to clean up the extended attribute code that fixes
> this problem along the way by killing off the xattr locks and using the
> backing files/dirs i_mutex instead. I'll post them to the reiserfs
> mailing list.
Do we have anything suitable for 2.6.21 which will address this crash?
Also, it's not clear to me how many users we can expect to be impacted by it.
I assume that if the same bug is in 2.6.20 then the answer is "not many".
How come Andrea is able to keep hitting it?
Thanks.
next prev parent reply other threads:[~2007-04-21 0:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070413095219.02075323.akpm@linux-foundation.org>
[not found] ` <462536B2.5060308@users.sourceforge.net>
[not found] ` <c04ebacf0704180152qdc72fcdnd0755dbf070b40d2@mail.gmail.com>
2007-04-18 14:16 ` Fwd: Fw: [2.6.20.4] BUG: dentry xattrs still in use in shrink_dcache_for_umount() with reiserfs Vladimir V. Saveliev
2007-04-18 15:00 ` Jeff Mahoney
2007-04-21 0:07 ` Andrew Morton [this message]
2007-04-21 1:45 ` Jeff Mahoney
2007-04-21 13:17 ` Andrea Righi
2007-04-21 14:31 ` Jeff Mahoney
2007-04-21 14:34 ` Jeff Mahoney
2007-04-21 15:26 ` [PATCH] reiserfs: fix xattr root locking/refcount bug Jeff Mahoney
2007-04-21 19:39 ` Andrew Morton
2007-04-22 10:28 ` Andrea Righi
2007-04-22 20:49 ` Jeff Mahoney
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=20070420170738.e269fcae.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.righi@cineca.it \
--cc=edward@namesys.com \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.com \
--cc=vs@namesys.com \
--cc=zam@clusterfs.com \
/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