linux-kernel - Re: 2.6.23-rc8-mm2: BUG near reiserfs_xattr

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070927202607.GA3812@infradead.org>
Date:	Thu, 27 Sep 2007 21:26:07 +0100
From:	Christoph Hellwig <hch@...radead.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Laurent Riffard <laurent.riffard@...e.fr>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	reiserfs-devel@...r.kernel.org, Dave Hansen <haveblue@...ibm.com>
Subject: Re: 2.6.23-rc8-mm2: BUG near reiserfs_xattr_set

On Thu, Sep 27, 2007 at 12:48:33PM -0700, Andrew Morton wrote:
> >  __fput+0x124/0x1a9
> >  fput+0x31/0x35
> >  reiserfs_xattr_set+0x291/0x2b0 [reiserfs]
> >  user_set+0x4c/0x57 [reiserfs]
> >  reiserfs_setxattr+0x81/0xf1 [reiserfs]
> >  vfs_setxattr+0x7d/0xfa
> >  setxattr+0xb9/0xd1
> >  sys_lsetxattr+0x4c/0x85
> >  sysenter_past_esp+0x57/0x85
> > 
> > EIP: mnt_drop_write+0x5b/0x9d
> > 
> 
> Hi, Dave!

This sure looks like a result of the reiserfs xattr code beeing
really sucky and passing a NULL vfsmount to dentry_open.

Dave will probably find a bandaid to work around this, but the
right fix is to stop using a file struct here entirely.  If you
look at reiserfs_xattr_set it's not actually used at all except
for passing it to ->prepare_write and ->commit_write which then
don't use it at all.  All that crap should be rewritten to just
pass the dentry around.  Note that all this should not acquire
writer counts on the vfsmount - we have done this already
before calling into the xattr methods.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/