From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+15927486a4f1bfcbaf91@syzkaller.appspotmail.com>
Cc: amir73il@gmail.com, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in fanotify_handle_event
Date: Fri, 26 Apr 2019 12:55:11 +0200 [thread overview]
Message-ID: <20190426105511.GA18333@quack2.suse.cz> (raw)
In-Reply-To: <000000000000d97b380586d1205f@google.com>
On Thu 18-04-19 10:14:00, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 77115225acc67d9ac4b15f04dd138006b9cd1ef2
> Author: Amir Goldstein <amir73il@gmail.com>
> Date: Thu Jan 10 17:04:37 2019 +0000
>
> fanotify: cache fsid in fsnotify_mark_connector
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1627632d200000
> start commit: 3f018f4a Add linux-next specific files for 20190418
> git tree: linux-next
> final crash: https://syzkaller.appspot.com/x/report.txt?x=1527632d200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1127632d200000
> kernel config: https://syzkaller.appspot.com/x/.config?x=faa7bdc352fc157e
> dashboard link: https://syzkaller.appspot.com/bug?extid=15927486a4f1bfcbaf91
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155543d3200000
>
> Reported-by: syzbot+15927486a4f1bfcbaf91@syzkaller.appspotmail.com
> Fixes: 77115225acc6 ("fanotify: cache fsid in fsnotify_mark_connector")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Let syzbot test the fix:
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git fsnotify
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2019-04-26 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 17:06 general protection fault in fanotify_handle_event syzbot
2019-04-18 17:14 ` syzbot
2019-04-19 9:33 ` Amir Goldstein
2019-04-23 16:27 ` Jan Kara
2019-04-23 18:05 ` Amir Goldstein
2019-04-24 11:46 ` Jan Kara
2019-04-26 10:55 ` Jan Kara [this message]
2019-04-26 11:13 ` syzbot
2019-04-29 2:10 ` Jan Kara
2019-04-29 5:36 ` syzbot
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=20190426105511.GA18333@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+15927486a4f1bfcbaf91@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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).