From: Dev Jain <dev.jain@arm.com>
To: akpm@linux-foundation.org, willy@infradead.org
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, david@redhat.com,
anshuman.khandual@arm.com, ryan.roberts@arm.com,
Dev Jain <dev.jain@arm.com>
Subject: [PATCH] xarray: Add a BUG_ON() to ensure caller is not sibling
Date: Wed, 28 May 2025 17:01:24 +0530 [thread overview]
Message-ID: <20250528113124.87084-1-dev.jain@arm.com> (raw)
Suppose xas is pointing somewhere near the end of the multi-entry batch.
Then it may happen that the computed slot already falls beyond the batch,
thus breaking the loop due to !xa_is_sibling(), and computing the wrong
order. Thus ensure that the caller is aware of this by triggering a BUG
when the entry is a sibling entry.
This patch is motivated by code inspection and not a real bug report.
Signed-off-by: Dev Jain <dev.jain@arm.com>
---
The patch applies on 6.15 kernel.
lib/xarray.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/xarray.c b/lib/xarray.c
index 9644b18af18d..0f699766c24f 100644
--- a/lib/xarray.c
+++ b/lib/xarray.c
@@ -1917,6 +1917,8 @@ int xas_get_order(struct xa_state *xas)
if (!xas->xa_node)
return 0;
+ XA_NODE_BUG_ON(xas->xa_node, xa_is_sibling(xa_entry(xas->xa,
+ xas->xa_node, xas->xa_offset)));
for (;;) {
unsigned int slot = xas->xa_offset + (1 << order);
--
2.30.2
next reply other threads:[~2025-05-28 11:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 11:31 Dev Jain [this message]
2025-05-28 17:12 ` [PATCH] xarray: Add a BUG_ON() to ensure caller is not sibling Zi Yan
2025-05-29 3:17 ` Dev Jain
2025-05-29 22:47 ` Zi Yan
2025-05-29 23:04 ` Zi Yan
2025-05-30 3:44 ` Dev Jain
2025-06-02 15:03 ` Zi Yan
2025-06-03 5:23 ` Dev Jain
2025-06-03 7:58 ` David Hildenbrand
2025-06-03 12:17 ` Zi Yan
2025-06-03 12:59 ` Dev Jain
2025-06-03 13:57 ` Zi Yan
2025-06-03 14:07 ` Dev Jain
2025-06-02 5:44 ` Dev Jain
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=20250528113124.87084-1-dev.jain@arm.com \
--to=dev.jain@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=david@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).