From: syzbot <syzbot+d16facb00df3f446511c@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [jfs?] KASAN: slab-use-after-free Read in lmLogInit
Date: Thu, 22 Aug 2024 00:18:26 -0700 [thread overview]
Message-ID: <000000000000033fee062040778e@google.com> (raw)
In-Reply-To: <000000000000ab44fc06203f0d28@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [jfs?] KASAN: slab-use-after-free Read in lmLogInit
Author: lizhi.xu@windriver.com
why integrity chaneged?
#syz test: upstream df6cbc62cc9b
diff --git a/fs/jfs/jfs_logmgr.c b/fs/jfs/jfs_logmgr.c
index 9609349e92e5..cc33178f720a 100644
--- a/fs/jfs/jfs_logmgr.c
+++ b/fs/jfs/jfs_logmgr.c
@@ -1963,11 +1963,14 @@ static int lbmRead(struct jfs_log * log, int pn, struct lbuf ** bpp)
{
struct bio *bio;
struct lbuf *bp;
+ int no_integrity = log->no_integrity;
/*
* allocate a log buffer
*/
+ printk("log1: %p, integrity: %d, %s\n", log, log->no_integrity, __func__);
*bpp = bp = lbmAllocate(log, pn);
+ printk("log2: %p, integrity: %d, %s\n", log, log->no_integrity, __func__);
jfs_info("lbmRead: bp:0x%p pn:0x%x", bp, pn);
bp->l_flag |= lbmREAD;
@@ -1979,8 +1982,9 @@ static int lbmRead(struct jfs_log * log, int pn, struct lbuf ** bpp)
bio->bi_end_io = lbmIODone;
bio->bi_private = bp;
+ printk("log3: %p, integrity: %d, %s\n", log, log->no_integrity, __func__);
/*check if journaling to disk has been disabled*/
- if (log->no_integrity) {
+ if (no_integrity) {
bio->bi_iter.bi_size = 0;
lbmIODone(bio);
} else {
next prev parent reply other threads:[~2024-08-22 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 5:37 [syzbot] [jfs?] KASAN: slab-use-after-free Read in lmLogInit syzbot
2024-08-22 7:18 ` syzbot [this message]
2024-08-26 9:02 ` [syzbot] " syzbot
2025-02-13 6:17 ` 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=000000000000033fee062040778e@google.com \
--to=syzbot+d16facb00df3f446511c@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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