From: Edward Adam Davis <eadavis@qq.com>
To: syzbot+077d9ebda84f426a6a1e@syzkaller.appspotmail.com
Cc: jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org, shaggy@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [PATCH] jfs: Issue a warning when leafidx is too large
Date: Tue, 17 Jun 2025 11:19:57 +0800 [thread overview]
Message-ID: <tencent_279220DDBEDD93995BCF998D8B25B18D8B07@qq.com> (raw)
In-Reply-To: <6850d37f.a70a0220.395abc.01f9.GAE@google.com>
When it is clear that leafidx is too large, a warn is triggered to
distinguish it from other sizes.
Reported-by: syzbot+077d9ebda84f426a6a1e@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=077d9ebda84f426a6a1e
Signed-off-by: Edward Adam Davis <eadavis@qq.com>
---
fs/jfs/jfs_dmap.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/fs/jfs/jfs_dmap.c b/fs/jfs/jfs_dmap.c
index 35e063c9f3a4..7e3c5f6826d8 100644
--- a/fs/jfs/jfs_dmap.c
+++ b/fs/jfs/jfs_dmap.c
@@ -2856,9 +2856,13 @@ static int dbJoin(dmtree_t *tp, int leafno, int newval, bool is_ctl)
static void dbAdjTree(dmtree_t *tp, int leafno, int newval, bool is_ctl)
{
int lp, pp, k;
- int max, size;
+ int max, size, max_idx;
size = is_ctl ? CTLTREESIZE : TREESIZE;
+ max_idx = is_ctl ? LPERCTL : LPERDMAP;
+
+ if (WARN_ON_ONCE(le32_to_cpu(tp->dmt_leafidx) >= max_idx))
+ return;
/* pick up the index of the leaf for this leafno.
*/
--
2.43.0
next prev parent reply other threads:[~2025-06-17 3:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 2:31 [syzbot] [jfs?] WARNING: fs/jfs/jfs_dmap.c:LINE at dbAdjTree, CPU: jfsCommit/NUM syzbot
2025-06-17 3:01 ` Edward Adam Davis
2025-06-17 7:48 ` syzbot
2025-06-17 8:07 ` Aleksandr Nogikh
2025-06-17 3:19 ` Edward Adam Davis [this message]
2025-07-11 20:31 ` [PATCH] jfs: Issue a warning when leafidx is too large Dave Kleikamp
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=tencent_279220DDBEDD93995BCF998D8B25B18D8B07@qq.com \
--to=eadavis@qq.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=syzbot+077d9ebda84f426a6a1e@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®