From: Al Viro <viro@ZenIV.linux.org.uk>
To: Greg Dietsche <greg@gregd.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: 3.0 rc3 bug & warning fs/inode.c && fs/fs-writeback.c
Date: Tue, 21 Jun 2011 23:40:27 +0100 [thread overview]
Message-ID: <20110621224027.GA11521@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4E01195F.8040000@gregd.org>
On Tue, Jun 21, 2011 at 05:21:19PM -0500, Greg Dietsche wrote:
> I'm leaning towards might be something else. Correct me if I'm
> wrong, but it seems that 50338b889dc504c69e0cb316ac92d1b9e51f3c8a
> was included in rc3.
Nope - it's in a branch that started before -rc3 but got merged between
-rc3 and -rc4. git log v3.0-rc3 fs/namei.c and watch it not being there
while the same with s/rc3/rc4/ will show it just fine. In fact, the last
commit touching fs/namei.c in -rc3 is the one that introduced the breakage
fixed by 50338b889dc504c69e0cb316ac92d1b9e51f3c8a.
prev parent reply other threads:[~2011-06-21 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 12:25 3.0 rc3 bug & warning fs/inode.c && fs/fs-writeback.c Greg Dietsche
2011-06-21 12:45 ` Al Viro
2011-06-21 12:54 ` Greg Dietsche
2011-06-21 22:21 ` Greg Dietsche
2011-06-21 22:40 ` 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=20110621224027.GA11521@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=greg@gregd.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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.