From: syzbot <syzbot+1145ec2e23165570c3ac@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, clm@fb.com, dan.carpenter@oracle.com,
dave@stgolabs.net, dhowells@redhat.com, dsterba@suse.com,
dvyukov@google.com, ebiederm@xmission.com, jbacik@fb.com,
ktkhai@virtuozzo.com, ktsanaktsidis@zendesk.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, manfred@colorfullife.com, mhocko@suse.com,
nborisov@suse.com, penguin-kernel@I-love.SAKURA.ne.jp,
penguin-kernel@i-love.sakura.ne.jp, rppt@linux.vnet.ibm.com,
sfr@canb.auug.org.au, shakeelb@google.com,
syzkaller-bugs@googlegroups.com, vdavydov.dev@gmail.com,
willy@infradead.org
Subject: Re: general protection fault in put_pid
Date: Wed, 27 Mar 2019 13:10:01 -0700 [thread overview]
Message-ID: <000000000000c58fcf058519059e@google.com> (raw)
In-Reply-To: <00000000000051ee78057cc4d98f@google.com>
syzbot has bisected this bug to:
commit b9b8a41adeff5666b402996020b698504c927353
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date: Mon Aug 20 08:25:33 2018 +0000
btrfs: use after free in btrfs_quota_enable
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14155a1f200000
start commit: f5d58277 Merge branch 'for-linus' of git://git.kernel.org/..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=16155a1f200000
console output: https://syzkaller.appspot.com/x/log.txt?x=12155a1f200000
kernel config: https://syzkaller.appspot.com/x/.config?x=c8970c89a0efbb23
dashboard link: https://syzkaller.appspot.com/bug?extid=1145ec2e23165570c3ac
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16803afb400000
Reported-by: syzbot+1145ec2e23165570c3ac@syzkaller.appspotmail.com
Fixes: b9b8a41adeff ("btrfs: use after free in btrfs_quota_enable")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-03-27 20:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 20:23 general protection fault in put_pid syzbot
2018-12-12 10:55 ` Dmitry Vyukov
2018-12-19 9:04 ` Manfred Spraul
2018-12-20 15:36 ` Dmitry Vyukov
2018-12-22 19:07 ` Manfred Spraul
2018-12-23 7:37 ` Dmitry Vyukov
2018-12-23 9:57 ` Dmitry Vyukov
2018-12-23 10:30 ` Dmitry Vyukov
2018-12-23 10:42 ` Dmitry Vyukov
2018-12-23 12:32 ` Manfred Spraul
2018-12-25 9:35 ` Dmitry Vyukov
2018-12-26 9:03 ` Dmitry Vyukov
2018-12-30 9:31 ` Dmitry Vyukov
2018-12-31 6:35 ` Dmitry Vyukov
2018-12-25 9:41 ` Dmitry Vyukov
2018-12-23 12:25 ` Manfred Spraul
2019-01-03 22:18 ` Shakeel Butt
2019-01-07 18:04 ` Manfred Spraul
2019-01-07 18:22 ` Shakeel Butt
2019-03-27 20:10 ` syzbot [this message]
2019-03-27 20:27 ` Matthew Wilcox
2019-03-27 22:51 ` David Sterba
2019-11-07 13:42 ` 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=000000000000c58fcf058519059e@google.com \
--to=syzbot+1145ec2e23165570c3ac@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=dan.carpenter@oracle.com \
--cc=dave@stgolabs.net \
--cc=dhowells@redhat.com \
--cc=dsterba@suse.com \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=jbacik@fb.com \
--cc=ktkhai@virtuozzo.com \
--cc=ktsanaktsidis@zendesk.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--cc=mhocko@suse.com \
--cc=nborisov@suse.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rppt@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=shakeelb@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vdavydov.dev@gmail.com \
--cc=willy@infradead.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).