From: David Sterba <dsterba@suse.cz>
To: Matthew Wilcox <willy@infradead.org>
Cc: syzbot <syzbot+1145ec2e23165570c3ac@syzkaller.appspotmail.com>,
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,
rppt@linux.vnet.ibm.com, sfr@canb.auug.org.au,
shakeelb@google.com, syzkaller-bugs@googlegroups.com,
vdavydov.dev@gmail.com
Subject: Re: general protection fault in put_pid
Date: Wed, 27 Mar 2019 23:51:03 +0100 [thread overview]
Message-ID: <20190327225102.GB29086@twin.jikos.cz> (raw)
In-Reply-To: <20190327202712.GT10344@bombadil.infradead.org>
On Wed, Mar 27, 2019 at 01:27:12PM -0700, Matthew Wilcox wrote:
> On Wed, Mar 27, 2019 at 01:10:01PM -0700, syzbot wrote:
> > 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
>
> Not plausible. Try again.
Agreed, grep for 'btrfs' in the console log does not show anything, ie.
no messages, slab caches nor functions on the stack.
next prev parent reply other threads:[~2019-03-27 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000051ee78057cc4d98f@google.com>
2019-03-27 20:10 ` general protection fault in put_pid syzbot
2019-03-27 20:27 ` Matthew Wilcox
2019-03-27 22:51 ` David Sterba [this message]
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=20190327225102.GB29086@twin.jikos.cz \
--to=dsterba@suse.cz \
--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=syzbot+1145ec2e23165570c3ac@syzkaller.appspotmail.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).