From: Al Viro <viro@zeniv.linux.org.uk>
To: lkp@lists.01.org
Subject: Re: e56b43b971 ("reimplement path_mountpoint() with less magic"): kernel BUG at fs/namei.c:676!
Date: Tue, 28 Jan 2020 12:45:46 +0000 [thread overview]
Message-ID: <20200128124546.GR23230@ZenIV.linux.org.uk> (raw)
In-Reply-To: <5e2fed51.lXNhkot2j7mH7hZM%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
On Tue, Jan 28, 2020 at 04:14:09PM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes
>
> commit e56b43b971a7c08762fceab330a52b7245041dbc
> Author: Al Viro <viro@zeniv.linux.org.uk>
> AuthorDate: Fri Jan 10 17:17:19 2020 -0500
> Commit: Al Viro <viro@zeniv.linux.org.uk>
> CommitDate: Fri Jan 10 17:43:05 2020 -0500
>
> reimplement path_mountpoint() with less magic
*blink*
Which tree are you looking at? The one you've mentioned has a version
of that commit with fix folded in, and had it there for nearly two weeks -
replacement is
commit c64cd6e34ea340adbb2a0a2f99cc884b96dcdca5
Author: Al Viro <viro@zeniv.linux.org.uk>
AuthorDate: Fri Jan 10 17:17:19 2020 -0500
Commit: Al Viro <viro@zeniv.linux.org.uk>
CommitDate: Wed Jan 15 01:36:06 2020 -0500
reimplement path_mountpoint() with less magic
Moreover, that fixed commit has been pulled into mainline since then, so
whatever tree this has come from would be impossible to merge without
a mainline conflict...
Please, explain.
next prev parent reply other threads:[~2020-01-28 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 8:14 e56b43b971 ("reimplement path_mountpoint() with less magic"): kernel BUG at fs/namei.c:676! kernel test robot
2020-01-28 12:45 ` Al Viro [this message]
2020-01-28 13:09 ` Li, Philip
2020-01-28 13:25 ` Al Viro
2020-01-28 13:30 ` Li, Philip
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=20200128124546.GR23230@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=lkp@lists.01.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.