From: syzbot <syzbot+2c49971e251e36216d1f@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, amir73il@gmail.com, cai@lca.pw,
crecklin@redhat.com, jack@suse.cz, keescook@chromium.org,
linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING: bad usercopy in fanotify_read
Date: Sat, 16 Mar 2019 07:49:01 -0700 [thread overview]
Message-ID: <0000000000008f302105843741ad@google.com> (raw)
In-Reply-To: <00000000000016f7d40583d79bd9@google.com>
syzbot has bisected this bug to:
commit a8b13aa20afb69161b5123b4f1acc7ea0a03d360
Author: Amir Goldstein <amir73il@gmail.com>
Date: Thu Jan 10 17:04:36 2019 +0000
fanotify: enable FAN_REPORT_FID init flag
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11e78d6f200000
start commit: a8b13aa2 fanotify: enable FAN_REPORT_FID init flag
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=13e78d6f200000
console output: https://syzkaller.appspot.com/x/log.txt?x=15e78d6f200000
kernel config: https://syzkaller.appspot.com/x/.config?x=e9d91b7192a5e96e
dashboard link: https://syzkaller.appspot.com/bug?extid=2c49971e251e36216d1f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1287516f200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ee410b200000
Reported-by: syzbot+2c49971e251e36216d1f@syzkaller.appspotmail.com
Fixes: a8b13aa2 ("fanotify: enable FAN_REPORT_FID init flag")
prev parent reply other threads:[~2019-03-16 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 20:42 WARNING: bad usercopy in fanotify_read syzbot
2019-03-13 6:26 ` Kees Cook
2019-03-13 6:42 ` Amir Goldstein
2019-03-13 14:35 ` Jan Kara
2019-03-13 15:35 ` Kees Cook
2019-03-13 15:47 ` Jan Kara
2019-03-18 18:27 ` Kees Cook
2019-03-19 8:32 ` Jan Kara
2019-03-16 14:49 ` syzbot [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=0000000000008f302105843741ad@google.com \
--to=syzbot+2c49971e251e36216d1f@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=cai@lca.pw \
--cc=crecklin@redhat.com \
--cc=jack@suse.cz \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 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.