From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Beregalov <a.beregalov@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ReiserFS Development List <reiserfs-devel@vger.kernel.org>,
David <david@unsolicited.net>
Subject: Re: 2.6.30-rc3: reiserfs: WARNING: at fs/namei.c:1251 lookup_one_len
Date: Wed, 29 Apr 2009 08:18:11 +0100 [thread overview]
Message-ID: <20090429071811.GH8633@ZenIV.linux.org.uk> (raw)
In-Reply-To: <49F7F8EB.1080907@suse.com>
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?
prev parent reply other threads:[~2009-04-29 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 0:15 2.6.30-rc3: reiserfs: WARNING: at fs/namei.c:1251 lookup_one_len Alexander Beregalov
2009-04-29 3:13 ` Andrew Morton
2009-04-29 4:51 ` Al Viro
2009-04-29 6:51 ` Jeff Mahoney
2009-04-29 7:18 ` Al Viro [this message]
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=20090429071811.GH8633@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=a.beregalov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@unsolicited.net \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.