From: <gregkh@linuxfoundation.org>
To: agruenba@redhat.com,anprice@redhat.com,gfs2@lists.linux.dev,gregkh@linuxfoundation.org,ruohanlan@aliyun.com,sashal@kernel.org,syzbot+4708579bb230a0582a57@syzkaller.appspotmail.com
Cc: <stable-commits@vger.kernel.org>
Subject: Patch "gfs2: Validate i_depth for exhash directories" has been added to the 5.10-stable tree
Date: Thu, 23 Apr 2026 14:35:06 +0200 [thread overview]
Message-ID: <2026042306-depletion-overstock-6779@gregkh> (raw)
In-Reply-To: <20260423032002.2803528-1-ruohanlan@aliyun.com>
This is a note to let you know that I've just added the patch titled
gfs2: Validate i_depth for exhash directories
to the 5.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
gfs2-validate-i_depth-for-exhash-directories.patch
and it can be found in the queue-5.10 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
From stable+bounces-240403-greg=kroah.com@vger.kernel.org Thu Apr 23 05:20:44 2026
From: Ruohan Lan <ruohanlan@aliyun.com>
Date: Thu, 23 Apr 2026 11:20:02 +0800
Subject: gfs2: Validate i_depth for exhash directories
To: gregkh@linuxfoundation.org, sashal@kernel.org, stable@vger.kernel.org
Cc: gfs2@lists.linux.dev, Andrew Price <anprice@redhat.com>, syzbot+4708579bb230a0582a57@syzkaller.appspotmail.com, Andreas Gruenbacher <agruenba@redhat.com>, Ruohan Lan <ruohanlan@aliyun.com>
Message-ID: <20260423032002.2803528-1-ruohanlan@aliyun.com>
From: Andrew Price <anprice@redhat.com>
[ Upstream commit 557c024ca7250bb65ae60f16c02074106c2f197b ]
A fuzzer test introduced corruption that ends up with a depth of 0 in
dir_e_read(), causing an undefined shift by 32 at:
index = hash >> (32 - dip->i_depth);
As calculated in an open-coded way in dir_make_exhash(), the minimum
depth for an exhash directory is ilog2(sdp->sd_hash_ptrs) and 0 is
invalid as sdp->sd_hash_ptrs is fixed as sdp->bsize / 16 at mount time.
So we can avoid the undefined behaviour by checking for depth values
lower than the minimum in gfs2_dinode_in(). Values greater than the
maximum are already being checked for there.
Also switch the calculation in dir_make_exhash() to use ilog2() to
clarify how the depth is calculated.
Tested with the syzkaller repro.c and xfstests '-g quick'.
Reported-by: syzbot+4708579bb230a0582a57@syzkaller.appspotmail.com
Signed-off-by: Andrew Price <anprice@redhat.com>
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
[ To maintain consistency in error handling in gfs2_dinode_in(),
use "goto corrupt" in v5.10. ]
Signed-off-by: Ruohan Lan <ruohanlan@aliyun.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
fs/gfs2/dir.c | 6 ++----
fs/gfs2/glops.c | 4 ++++
2 files changed, 6 insertions(+), 4 deletions(-)
--- a/fs/gfs2/dir.c
+++ b/fs/gfs2/dir.c
@@ -60,6 +60,7 @@
#include <linux/crc32.h>
#include <linux/vmalloc.h>
#include <linux/bio.h>
+#include <linux/log2.h>
#include "gfs2.h"
#include "incore.h"
@@ -910,7 +911,6 @@ static int dir_make_exhash(struct inode
struct qstr args;
struct buffer_head *bh, *dibh;
struct gfs2_leaf *leaf;
- int y;
u32 x;
__be64 *lp;
u64 bn;
@@ -977,9 +977,7 @@ static int dir_make_exhash(struct inode
i_size_write(inode, sdp->sd_sb.sb_bsize / 2);
gfs2_add_inode_blocks(&dip->i_inode, 1);
dip->i_diskflags |= GFS2_DIF_EXHASH;
-
- for (x = sdp->sd_hash_ptrs, y = -1; x; x >>= 1, y++) ;
- dip->i_depth = y;
+ dip->i_depth = ilog2(sdp->sd_hash_ptrs);
gfs2_dinode_out(dip, dibh->b_data);
--- a/fs/gfs2/glops.c
+++ b/fs/gfs2/glops.c
@@ -11,6 +11,7 @@
#include <linux/bio.h>
#include <linux/posix_acl.h>
#include <linux/security.h>
+#include <linux/log2.h>
#include "gfs2.h"
#include "incore.h"
@@ -452,6 +453,9 @@ static int gfs2_dinode_in(struct gfs2_in
depth = be16_to_cpu(str->di_depth);
if (unlikely(depth > GFS2_DIR_MAX_DEPTH))
goto corrupt;
+ if ((ip->i_diskflags & GFS2_DIF_EXHASH) &&
+ depth < ilog2(sdp->sd_hash_ptrs))
+ goto corrupt;
ip->i_depth = (u8)depth;
ip->i_entries = be32_to_cpu(str->di_entries);
Patches currently in stable-queue which might be from ruohanlan@aliyun.com are
queue-5.10/gfs2-validate-i_depth-for-exhash-directories.patch
prev parent reply other threads:[~2026-04-23 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 3:20 [PATCH 5.10.y] gfs2: Validate i_depth for exhash directories Ruohan Lan
2026-04-23 12:35 ` gregkh [this message]
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=2026042306-depletion-overstock-6779@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=agruenba@redhat.com \
--cc=anprice@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=ruohanlan@aliyun.com \
--cc=sashal@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=syzbot+4708579bb230a0582a57@syzkaller.appspotmail.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