linux-kernel - Re: 2.6.30-rc3: reiserfs: WARNING: at fs/namei.c:1251 lookup_one

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] [day] [month] [year] [list]

Message-ID: <20090429071811.GH8633@ZenIV.linux.org.uk>
Date:	Wed, 29 Apr 2009 08:18:11 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Jeff Mahoney <jeffm@...e.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Alexander Beregalov <a.beregalov@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	ReiserFS Development List <reiserfs-devel@...r.kernel.org>,
	David <david@...olicited.net>
Subject: Re: 2.6.30-rc3: reiserfs: WARNING: at fs/namei.c:1251
	lookup_one_len

On Wed, Apr 29, 2009 at 02:51:23AM -0400, Jeff Mahoney wrote:
> > A number of people are reporting this.  Al Viro said
> > 
> > : Yeah, the sanity check had caught another place misusing lookup_one_len().
> > : I'd keep the warning in place for now; I think I know how to deal with
> > : reiserfs side of things, but if it turns out too invasive for post-rc3,
> > : we can always turn the check off just for -final.  For now I'd keep the
> > : check in place, just to see if anything else runs into it.
> > 
> > It would be nice to plug this sooner rather than later please, to save
> > a bit of bug-reporting bandwidth.
> 
> I have a fix for this that I need to test. I've been traveling and
> haven't had a chance to. I'm back in the office and will be able to
> later today.

Could you Cc me on that?
--
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/