linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+fcdd69a8426baab36109@syzkaller.appspotmail.com>
To: axboe@kernel.dk, ground_handling@unex-aviation.co.id,
	hare@suse.de, hch@lst.de, jack@suse.cz, jeffm@suse.com,
	linux-kernel@vger.kernel.org, mszeredi@redhat.com,
	reiserfs-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	yukuai3@huawei.com
Subject: Re: [syzbot] WARNING in reiserfs_put_super
Date: Sun, 25 Jul 2021 12:50:09 -0700	[thread overview]
Message-ID: <000000000000ba466405c7f7f1c7@google.com> (raw)
In-Reply-To: <000000000000ebd6da05b00bcea6@google.com>

syzbot has bisected this issue to:

commit f902b02600028dfc0c9df811eb711ac7d7fca09f
Author: Christoph Hellwig <hch@lst.de>
Date:   Thu Nov 14 14:34:32 2019 +0000

    block: refactor rescan_partitions

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=166889b2300000
start commit:   90d856e71443 Add linux-next specific files for 20210723
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=156889b2300000
console output: https://syzkaller.appspot.com/x/log.txt?x=116889b2300000
kernel config:  https://syzkaller.appspot.com/x/.config?x=298516715f6ad5cd
dashboard link: https://syzkaller.appspot.com/bug?extid=fcdd69a8426baab36109
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=146b2066300000

Reported-by: syzbot+fcdd69a8426baab36109@syzkaller.appspotmail.com
Fixes: f902b0260002 ("block: refactor rescan_partitions")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2021-07-25 19:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24  9:27 WARNING in reiserfs_put_super syzbot
2021-07-25 13:44 ` [syzbot] " syzbot
2021-07-25 19:50 ` syzbot [this message]
2021-07-26 18:20   ` Jan Kara

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=000000000000ba466405c7f7f1c7@google.com \
    --to=syzbot+fcdd69a8426baab36109@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=ground_handling@unex-aviation.co.id \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=jeffm@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mszeredi@redhat.com \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yukuai3@huawei.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;
as well as URLs for NNTP newsgroup(s).