From: Al Viro <viro@zeniv.linux.org.uk>
To: syzbot <syzbot+494c7ddf66acac0ad747@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: general protection fault in do_move_mount
Date: Thu, 9 May 2019 07:33:55 +0100 [thread overview]
Message-ID: <20190509063355.GR23075@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20190509063034.GQ23075@ZenIV.linux.org.uk>
On Thu, May 09, 2019 at 07:30:34AM +0100, Al Viro wrote:
> On Wed, May 08, 2019 at 10:40:06PM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit: 80f23212 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=11ab8dd0a00000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=40a58b399941db7e
> > dashboard link: https://syzkaller.appspot.com/bug?extid=494c7ddf66acac0ad747
> > compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> >
> > Unfortunately, I don't have any reproducer for this crash yet.
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+494c7ddf66acac0ad747@syzkaller.appspotmail.com
>
> *Ugh*
>
> That's a bloody dumb leftover from very old variant of that thing;
> the following should fix it.
In vfs.git#fixes, will send a pull request tomorrow...
prev parent reply other threads:[~2019-05-09 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 5:40 general protection fault in do_move_mount syzbot
2019-05-09 6:30 ` Al Viro
2019-05-09 6:33 ` 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=20190509063355.GR23075@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+494c7ddf66acac0ad747@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).