From: "syzbot" <syzbot@kernel.org>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: immersa.bartosz.chronowski@gmail.com, syzbot@lists.linux.dev
Subject: [PATCH RFC v4] jfs: validate dmap start before block map operations
Date: Mon, 27 Jul 2026 18:48:37 +0000 (UTC) [thread overview]
Message-ID: <d1405703-afc9-40f9-bc57-ddedf66f35da@mail.kernel.org> (raw)
A corrupted JFS filesystem image can cause a state where the block
allocation map (bmap) and the dmap pages are out of sync. Specifically, if
a dmap page's `dp->start` is corrupted, it can lead to a mismatch during
block allocation or update operations. The block allocator calculates the
returned block number based on `dp->start` (i.e., `dp->start +
block_index`), while the bitmap update is derived from the block's relative
position within the dmap. If `dp->start` does not match the expected start
block number for that dmap's position in the bmap, the allocator may return
a block number that is already in use (e.g., as an inode table block or
metadata), while marking a completely different block as allocated. This
mismatch leads to duplicate allocations. When a thread later attempts to
lock this duplicate block (for example, during a directory btree split),
`txLock()` detects a metapage conflict because the block is already locked
for another purpose, triggering a kernel BUG:
kernel BUG at fs/jfs/jfs_txnmgr.c:836!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
RIP: 0010:txLock+0x1cc3/0x1d10 fs/jfs/jfs_txnmgr.c:836
Call Trace:
<TASK>
dtSplitRoot+0x38d/0x18a0 fs/jfs/jfs_dtree.c:1924
dtSplitUp fs/jfs/jfs_dtree.c:990 [inline]
dtInsert+0xeb2/0x5890 fs/jfs/jfs_dtree.c:868
jfs_create+0x730/0xae0 fs/jfs/namei.c:138
...
To fix this, validate that the `dp->start` of the dmap page matches the
expected start block number before performing block map operations.
Rejecting a mismatched start with `-EIO` prevents duplicate allocations
before `txLock()` is reached. Additionally, preserve the existing
independent geometry check (`dp->tree.budmin < 0`) in `dbAllocCtl()`. Both
a mismatched start and a negative `budmin` will now fail with `-EIO` early,
preventing corrupted dmap structures from causing duplicate allocations and
subsequent transaction lock crashes.
Assisted-by: Gemini:gemini-3.5-flash Gemini:gemini-3.1-pro-preview syzbot
Reported-by: syzbot+a843f6ae2130a987d63b@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=a843f6ae2130a987d63b
Link: https://syzkaller.appspot.com/ai_job?id=30db4661-77f8-49bf-8389-8df570488e85
To: <jfs-discussion@lists.sourceforge.net>
To: "Dave Kleikamp" <shaggy@kernel.org>
Cc: "Kees Cook" <kees@kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Cc: "Yun Zhou" <yun.zhou@windriver.com>
Cc: "Zheng Yu" <zheng.yu@northwestern.edu>
---
v4:
- Renamed dbValidateDmap to db_validate_dmap to follow kernel naming conventions.
- Preserved the existing dp->tree.budmin < 0 check in dbAllocCtl instead of replacing it.
v3:
- Renamed the patch to "jfs: validate dmap start before block map operations".
- Simplified dbValidateDmap() to only validate that the dmap dp->start matches the expected start block number, removing unproven integrity checks.
- Updated the commit description to explain the exact root cause of the selection/update mismatch and how validating dp->start prevents duplicate allocations before txLock() is reached.
https://lore.kernel.org/all/7c3c4fb4-ccbd-486f-b087-6074364ee206@mail.kernel.org/T/
v2:
- Replaced the approach of propagating errors from txLock() with proactive dmap validation.
- Introduced dbValidateDmap() to check dmap page integrity (nblocks, nfree, start address, and tree structure).
- Integrated dmap validation into dbFree(), dbUpdatePMap(), dbAlloc(), dbExtend(), dbAllocCtl(), dbAllocBottomUp(), and dbExtendFS().
- Reverted return type changes for functions in jfs_dtree.c and jfs_xtree.c from the previous version.
https://lore.kernel.org/all/ff86d803-d687-48f6-9cc2-f3d35b27a666@mail.kernel.org/T/
v1:
https://lore.kernel.org/all/9d2eba88-93bf-4f3c-a3b2-b554e1fffe80@mail.kernel.org/T/
---
diff --git a/fs/jfs/jfs_dmap.c b/fs/jfs/jfs_dmap.c
index a841cf21d..063572456 100644
--- a/fs/jfs/jfs_dmap.c
+++ b/fs/jfs/jfs_dmap.c
@@ -98,6 +98,9 @@ static int blkstol2(s64 nb);
static int cntlz(u32 value);
static int cnttz(u32 word);
+static bool db_validate_dmap(struct super_block *sb, const struct dmap *dp,
+ s64 expected_start);
+
static int dbAllocDmapBU(struct bmap * bmp, struct dmap * dp, s64 blkno,
int nblocks);
static int dbInitDmap(struct dmap * dp, s64 blkno, int nblocks);
@@ -476,6 +479,12 @@ int dbFree(struct inode *ip, s64 blkno, s64 nblocks)
}
dp = (struct dmap *) mp->data;
+ if (!db_validate_dmap(ip->i_sb, dp, blkno & ~(s64)(BPERDMAP - 1))) {
+ release_metapage(mp);
+ IREAD_UNLOCK(ipbmap);
+ return -EIO;
+ }
+
/* determine the number of blocks to be freed from
* this dmap.
*/
@@ -568,6 +577,13 @@ dbUpdatePMap(struct inode *ipbmap,
if (mp == NULL)
return -EIO;
metapage_wait_for_io(mp);
+
+ if (!db_validate_dmap(ipbmap->i_sb,
+ (struct dmap *)mp->data,
+ blkno & ~(s64)(BPERDMAP - 1))) {
+ release_metapage(mp);
+ return -EIO;
+ }
}
dp = (struct dmap *) mp->data;
@@ -886,6 +902,11 @@ int dbAlloc(struct inode *ip, s64 hint, s64 nblocks, s64 * results)
dp = (struct dmap *) mp->data;
+ if (!db_validate_dmap(ip->i_sb, dp, blkno & ~(s64)(BPERDMAP - 1))) {
+ release_metapage(mp);
+ goto read_unlock;
+ }
+
/* first, try to satisfy the allocation request with the
* blocks beginning at the hint.
*/
@@ -1118,6 +1139,12 @@ static int dbExtend(struct inode *ip, s64 blkno, s64 nblocks, s64 addnblocks)
dp = (struct dmap *) mp->data;
+ if (!db_validate_dmap(ip->i_sb, dp, extblkno & ~(s64)(BPERDMAP - 1))) {
+ release_metapage(mp);
+ IREAD_UNLOCK(ipbmap);
+ return -EIO;
+ }
+
/* try to allocate the blocks immediately following the
* current allocation.
*/
@@ -1902,7 +1929,8 @@ dbAllocCtl(struct bmap * bmp, s64 nblocks, int l2nb, s64 blkno, s64 * results)
return -EIO;
dp = (struct dmap *) mp->data;
- if (dp->tree.budmin < 0) {
+ if (dp->tree.budmin < 0 ||
+ !db_validate_dmap(bmp->db_ipbmap->i_sb, dp, blkno & ~(s64)(BPERDMAP - 1))) {
release_metapage(mp);
return -EIO;
}
@@ -1936,6 +1964,12 @@ dbAllocCtl(struct bmap * bmp, s64 nblocks, int l2nb, s64 blkno, s64 * results)
}
dp = (struct dmap *) mp->data;
+ if (!db_validate_dmap(bmp->db_ipbmap->i_sb, dp, b & ~(s64)(BPERDMAP - 1))) {
+ release_metapage(mp);
+ rc = -EIO;
+ goto backout;
+ }
+
/* the dmap better be all free.
*/
if (dp->tree.stree[ROOT] != L2BPERDMAP) {
@@ -1993,6 +2027,11 @@ dbAllocCtl(struct bmap * bmp, s64 nblocks, int l2nb, s64 blkno, s64 * results)
}
dp = (struct dmap *) mp->data;
+ if (!db_validate_dmap(bmp->db_ipbmap->i_sb, dp, b & ~(s64)(BPERDMAP - 1))) {
+ release_metapage(mp);
+ continue;
+ }
+
/* free the blocks is this dmap.
*/
if (dbFreeDmap(bmp, dp, b, BPERDMAP)) {
@@ -2134,6 +2173,18 @@ static int dbAllocDmap(struct bmap * bmp, struct dmap * dp, s64 blkno,
return (rc);
}
+static bool db_validate_dmap(struct super_block *sb, const struct dmap *dp,
+ s64 expected_start)
+{
+ if (le64_to_cpu(dp->start) != expected_start) {
+ jfs_error(sb, "corrupt dmap page: start %lld expected %lld\n",
+ (long long)le64_to_cpu(dp->start),
+ (long long)expected_start);
+ return false;
+ }
+
+ return true;
+}
/*
* NAME: dbFreeDmap()
@@ -3308,6 +3359,12 @@ int dbAllocBottomUp(struct inode *ip, s64 blkno, s64 nblocks)
}
dp = (struct dmap *) mp->data;
+ if (!db_validate_dmap(ip->i_sb, dp, blkno & ~(s64)(BPERDMAP - 1))) {
+ release_metapage(mp);
+ IREAD_UNLOCK(ipbmap);
+ return -EIO;
+ }
+
/* determine the number of blocks to be allocated from
* this dmap.
*/
base-commit: dc59e4fea9d83f03bad6bddf3fa2e52491777482
--
This is an AI-generated patch subject to moderation.
Reply with '#syz upstream' to Sign-off the patch as a human author
and send it to the upstream kernel mailing lists.
Reply with '#syz reject' to reject it ('#syz unreject' to undo).
See https://goo.gle/syzbot-ai-patches for information about AI-generated patches.
You can comment on the patch as usual, syzbot will try to address
the comments and send a new version of the patch if necessary.
syzbot engineers can be reached at syzkaller@googlegroups.com.
next reply other threads:[~2026-07-27 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 18:48 syzbot [this message]
2026-07-29 15:45 ` [PATCH RFC v4] jfs: validate dmap start before block map operations Bartosz Chronowski
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=d1405703-afc9-40f9-bc57-ddedf66f35da@mail.kernel.org \
--to=syzbot@kernel.org \
--cc=immersa.bartosz.chronowski@gmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@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