From: syzbot <syzbot+838eb0878ffd51f27c41@syzkaller.appspotmail.com>
To: dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: KASAN: slab-out-of-bounds Write in pipe_write
Date: Mon, 02 Dec 2019 11:54:00 -0800 [thread overview]
Message-ID: <000000000000d6c9870598bdf090@google.com> (raw)
In-Reply-To: <000000000000a6324b0598b2eb59@google.com>
syzbot has bisected this bug to:
commit a194dfe6e6f6f7205eea850a420f2bc6a1541209
Author: David Howells <dhowells@redhat.com>
Date: Fri Sep 20 15:32:19 2019 +0000
pipe: Rearrange sequence in pipe_write() to preallocate slot
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16085abce00000
start commit: b94ae8ad Merge tag 'seccomp-v5.5-rc1' of git://git.kernel...
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=15085abce00000
console output: https://syzkaller.appspot.com/x/log.txt?x=11085abce00000
kernel config: https://syzkaller.appspot.com/x/.config?x=ff560c3de405258c
dashboard link: https://syzkaller.appspot.com/bug?extid=838eb0878ffd51f27c41
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=146a9f86e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1791d82ae00000
Reported-by: syzbot+838eb0878ffd51f27c41@syzkaller.appspotmail.com
Fixes: a194dfe6e6f6 ("pipe: Rearrange sequence in pipe_write() to
preallocate slot")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-12-02 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 6:45 KASAN: slab-out-of-bounds Write in pipe_write syzbot
2019-12-02 19:54 ` syzbot [this message]
2019-12-05 7:45 ` Eric Biggers
2019-12-05 16:33 ` David Howells
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=000000000000d6c9870598bdf090@google.com \
--to=syzbot+838eb0878ffd51f27c41@syzkaller.appspotmail.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).