From: syzbot <syzbot+ea8d1726e1e3367085ce@syzkaller.appspotmail.com>
To: axboe@kernel.dk, djwong@kernel.org, hch@lst.de, jack@suse.cz,
jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
linux-kernel@vger.kernel.org, mark@fasheh.com,
ocfs2-devel@lists.linux.dev, ocfs2-devel@oss.oracle.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in ocfs2_journal_toggle_dirty
Date: Mon, 30 Dec 2024 00:30:01 -0800 [thread overview]
Message-ID: <67725a09.050a0220.2f3838.04bb.GAE@google.com> (raw)
In-Reply-To: <671ff85a.050a0220.11b624.04b3.GAE@google.com>
syzbot has bisected this issue to:
commit 98ded54a33839e7b8f8bed772e01a544f48e33a7
Author: Christoph Hellwig <hch@lst.de>
Date: Wed Mar 30 05:29:10 2022 +0000
loop: remove the racy bd_inode->i_mapping->nrpages asserts
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=144cf0b0580000
start commit: 48f506ad0b68 Merge tag 'soc-fixes-6.13-2' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=164cf0b0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=124cf0b0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a2b862bf4a5409f
dashboard link: https://syzkaller.appspot.com/bug?extid=ea8d1726e1e3367085ce
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=146998c4580000
Reported-by: syzbot+ea8d1726e1e3367085ce@syzkaller.appspotmail.com
Fixes: 98ded54a3383 ("loop: remove the racy bd_inode->i_mapping->nrpages asserts")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-12-30 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 20:47 [syzbot] [ocfs2?] kernel BUG in ocfs2_journal_toggle_dirty syzbot
2024-12-30 8:30 ` syzbot [this message]
2025-02-10 1:16 ` 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=67725a09.050a0220.2f3838.04bb.GAE@google.com \
--to=syzbot+ea8d1726e1e3367085ce@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=ocfs2-devel@oss.oracle.com \
--cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.