From: syzbot <syzbot+fd15ff734dace9e16437@syzkaller.appspotmail.com>
To: axboe@kernel.dk, bcrl@kvack.org, hch@lst.de, linux-aio@kvack.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ming.lei@redhat.com, syzkaller-bugs@googlegroups.com,
tj@kernel.org, viro@zeniv.linux.org.uk, vkabatov@redhat.com
Subject: Re: general protection fault in percpu_ref_exit
Date: Thu, 08 Oct 2020 13:28:10 -0700 [thread overview]
Message-ID: <000000000000b1412b05b12eab0a@google.com> (raw)
In-Reply-To: <00000000000084dcbd05b12a3736@google.com>
syzbot has bisected this issue to:
commit 2b0d3d3e4fcfb19d10f9a82910b8f0f05c56ee3e
Author: Ming Lei <ming.lei@redhat.com>
Date: Thu Oct 1 15:48:41 2020 +0000
percpu_ref: reduce memory footprint of percpu_ref in fast path
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=126930d0500000
start commit: 8b787da7 Add linux-next specific files for 20201007
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=116930d0500000
console output: https://syzkaller.appspot.com/x/log.txt?x=166930d0500000
kernel config: https://syzkaller.appspot.com/x/.config?x=aac055e9c8fbd2b8
dashboard link: https://syzkaller.appspot.com/bug?extid=fd15ff734dace9e16437
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=119a0568500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=106c0a8b900000
Reported-by: syzbot+fd15ff734dace9e16437@syzkaller.appspotmail.com
Fixes: 2b0d3d3e4fcf ("percpu_ref: reduce memory footprint of percpu_ref in fast path")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-10-08 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 15:09 general protection fault in percpu_ref_exit syzbot
2020-10-08 20:28 ` syzbot [this message]
2020-10-09 1:23 ` Jens Axboe
2020-10-09 4:05 ` Ming Lei
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=000000000000b1412b05b12eab0a@google.com \
--to=syzbot+fd15ff734dace9e16437@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=bcrl@kvack.org \
--cc=hch@lst.de \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=vkabatov@redhat.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