From: Rafael Alejandro Diaz Cruz <rafad900@gmail.com>
To: linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [jfs?] [fat?] general protection fault in txEnd
Date: Mon, 30 Mar 2026 16:32:46 -0700 [thread overview]
Message-ID: <acsIHnU7DPhd42Bz@tradnomic.core> (raw)
[-- Attachment #1: Type: text/plain, Size: 10 bytes --]
#syz test
[-- Attachment #2: 0001-jfs-prevent-null-log-deference-from-superblock-durin.patch --]
[-- Type: text/x-diff, Size: 1151 bytes --]
From da93920ddc6ccfe238f98e6e060700566f4052c0 Mon Sep 17 00:00:00 2001
From: rafad900 <19312533+rafad900@users.noreply.github.com>
Date: Mon, 30 Mar 2026 13:33:13 -0700
Subject: [PATCH] jfs: prevent null log deference from superblock during
read only mode
Clearing the inode pointer is necessary to ensure no memory leaks
after txBegin fails to initialize the superblock during read only
mode.
Signed-off-by: rafad900 <19312533+rafad900@users.noreply.github.com>
---
fs/jfs/namei.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/fs/jfs/namei.c b/fs/jfs/namei.c
index 60c4a0e0fca5..3a5f45cdeae0 100644
--- a/fs/jfs/namei.c
+++ b/fs/jfs/namei.c
@@ -97,7 +97,13 @@ static int jfs_create(struct mnt_idmap *idmap, struct inode *dip,
}
tid = txBegin(dip->i_sb, 0);
-
+ if (tid == 0) {
+ jfs_err("jfs_create: unable to create tblk due to read only filesystem");
+ free_ea_wmap(ip);
+ clear_nlink(ip);
+ discard_new_inode(ip);
+ return -EROFS;
+ }
mutex_lock_nested(&JFS_IP(dip)->commit_mutex, COMMIT_MUTEX_PARENT);
mutex_lock_nested(&JFS_IP(ip)->commit_mutex, COMMIT_MUTEX_CHILD);
--
2.43.0
next reply other threads:[~2026-03-30 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 23:32 Rafael Alejandro Diaz Cruz [this message]
2026-03-31 0:19 ` [syzbot] [jfs] general protection fault in txEnd syzbot
-- strict thread matches above, loose matches on Subject: below --
2026-03-30 21:15 [syzbot] [jfs?] [fat?] " Rafael Alejandro Diaz Cruz
2026-03-28 2:20 Rafael Alejandro Diaz Cruz
2022-12-23 23:37 syzbot
2023-03-30 10:03 ` Aleksandr Nogikh
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=acsIHnU7DPhd42Bz@tradnomic.core \
--to=rafad900@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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