Linux block layer
 help / color / mirror / Atom feed
From: syzbot <syzbot+08df3e4c9b304b37cb04@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, axboe@kernel.dk,
	 dave.kleikamp@oracle.com, eadavis@qq.com, hdanton@sina.com,
	 jfs-discussion@lists.sourceforge.net,
	linux-block@vger.kernel.org,  linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org,  ntfs3@lists.linux.dev,
	shaggy@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [jfs?] general protection fault in rtlock_slowlock_locked
Date: Mon, 10 Aug 2026 11:35:02 -0700	[thread overview]
Message-ID: <6a7a19d6.b50370da.49fe0.0058.GAE@google.com> (raw)
In-Reply-To: <68dea1d7.050a0220.25d7ab.07bc.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit b15e4310633f90072d66cc9b6692acbf6b4d7d00
Author: Edward Adam Davis <eadavis@qq.com>
Date:   Tue Dec 16 13:57:51 2025 +0000

    jfs: Set the lbmDone flag at the end of lbmIODone

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17b1a079580000
start commit:   6bd9ed02871f Merge tag 'cgroup-for-6.19-rc8-fixes' of git:..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=151a39927f1e10b4
dashboard link: https://syzkaller.appspot.com/bug?extid=08df3e4c9b304b37cb04
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16ad7322580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: jfs: Set the lbmDone flag at the end of lbmIODone

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

      parent reply	other threads:[~2026-08-10 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <68dea1d7.050a0220.25d7ab.07bc.GAE@google.com>
2025-11-08  4:01 ` [syzbot] [block?] general protection fault in rtlock_slowlock_locked syzbot
2026-08-10 18:35 ` syzbot [this message]

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=6a7a19d6.b50370da.49fe0.0058.GAE@google.com \
    --to=syzbot+08df3e4c9b304b37cb04@syzkaller.appspotmail.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=axboe@kernel.dk \
    --cc=dave.kleikamp@oracle.com \
    --cc=eadavis@qq.com \
    --cc=hdanton@sina.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=shaggy@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox