From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+08df3e4c9b304b37cb04@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] general protection fault in rtlock_slowlock_locked
Date: Sat, 8 Nov 2025 15:43:30 +0800 [thread overview]
Message-ID: <20251108074339.9025-1-hdanton@sina.com> (raw)
In-Reply-To: <690ec096.a70a0220.22f260.0070.GAE@google.com>
> Date: Fri, 07 Nov 2025 20:01:26 -0800
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: da32d155f4a8 Merge tag 'gpio-fixes-for-v6.18-rc5' of git:/..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=118faa58580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=41ad820f608cb833
> dashboard link: https://syzkaller.appspot.com/bug?extid=08df3e4c9b304b37cb04
> compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=103d4412580000
#syz test
--- x/fs/jfs/jfs_logmgr.c
+++ y/fs/jfs/jfs_logmgr.c
@@ -149,6 +149,7 @@ do { \
* of log page
*/
#define lbmDIRECT 0x0100
+#define lbmInflight 0x0200
/*
* Global list of active external journals
@@ -1861,6 +1862,8 @@ static void lbmLogShutdown(struct jfs_lo
while (lbuf) {
struct lbuf *next = lbuf->l_freelist;
__free_page(lbuf->l_page);
+ while (lbuf->l_flag & lbmInflight)
+ schedule_timeout_idle(HZ);
kfree(lbuf);
lbuf = next;
}
@@ -2130,6 +2133,7 @@ static void lbmStartIO(struct lbuf * bp)
bio->bi_iter.bi_size = 0;
lbmIODone(bio);
} else {
+ bp->l_flag |= lbmInflight;
submit_bio(bio);
INCREMENT(lmStat.submitted);
}
@@ -2226,6 +2230,7 @@ static void lbmIODone(struct bio *bio)
if (bp->l_flag & lbmDIRECT) {
LCACHE_WAKEUP(&bp->l_ioevent);
LCACHE_UNLOCK(flags);
+ bp->l_flag &= ~lbmInflight;
return;
}
@@ -2305,6 +2310,7 @@ static void lbmIODone(struct bio *bio)
LCACHE_UNLOCK(flags); /* unlock+enable */
}
+ bp->l_flag &= ~lbmInflight;
}
int jfsIOWait(void *arg)
--
next prev parent reply other threads:[~2025-11-08 7:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 16:01 [syzbot] [ntfs3?] [usb?] " syzbot
2025-11-08 4:01 ` [syzbot] [block?] " syzbot
2025-11-08 7:43 ` Hillf Danton [this message]
2025-11-08 8:11 ` syzbot
2025-11-10 12:13 ` Edward Adam Davis
2025-11-10 12:52 ` syzbot
2025-11-10 13:08 ` Edward Adam Davis
2025-11-10 13:26 ` syzbot
2025-11-10 14:18 ` Edward Adam Davis
2025-11-10 14:41 ` syzbot
2025-11-10 14:50 ` Edward Adam Davis
2025-11-10 15:17 ` syzbot
2025-11-10 23:20 ` Edward Adam Davis
2025-11-11 0:12 ` syzbot
2026-08-10 18:35 ` [syzbot] [jfs?] " 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=20251108074339.9025-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+08df3e4c9b304b37cb04@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®