From: Kemeng Shi <shikemeng@huaweicloud.com>
To: akpm@linux-foundation.org, willy@infradead.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-nfs@vger.kernel.org
Subject: [PATCH v4 0/5] Fix and cleanups to xarray
Date: Wed, 18 Dec 2024 23:46:08 +0800 [thread overview]
Message-ID: <20241218154613.58754-1-shikemeng@huaweicloud.com> (raw)
v3->v4:
-Correct changelog in patch 1 by using nfs as low-level filesystem in
example how bug could be triggered in theory.
v2->v3:
-Add impact about fixed issue in changelog.
v1->v2:
-Drop patch "Xarray: skip unneeded xas_store() and xas_clear_mark() in
__xa_alloc()"
This series contains some random fixes and cleanups to xarray. Patch 1-2
are fixes and patch 3-6 are cleanups. More details can be found in
respective patches. Thanks!
Kemeng Shi (5):
Xarray: Do not return sibling entries from xas_find_marked()
Xarray: move forward index correctly in xas_pause()
Xarray: distinguish large entries correctly in xas_split_alloc()
Xarray: remove repeat check in xas_squash_marks()
Xarray: use xa_mark_t in xas_squash_marks() to keep code consistent
lib/test_xarray.c | 35 +++++++++++++++++++++++++++
lib/xarray.c | 26 +++++++++++---------
tools/testing/radix-tree/multiorder.c | 4 +++
3 files changed, 54 insertions(+), 11 deletions(-)
--
2.30.0
next reply other threads:[~2024-12-18 6:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 15:46 Kemeng Shi [this message]
2024-12-18 15:46 ` [PATCH v4 1/5] Xarray: Do not return sibling entries from xas_find_marked() Kemeng Shi
2024-12-18 15:46 ` [PATCH v4 2/5] Xarray: move forward index correctly in xas_pause() Kemeng Shi
2025-01-27 16:21 ` Geert Uytterhoeven
2025-02-06 6:13 ` Kemeng Shi
2025-02-06 7:34 ` Geert Uytterhoeven
2024-12-18 15:46 ` [PATCH v4 3/5] Xarray: distinguish large entries correctly in xas_split_alloc() Kemeng Shi
2024-12-18 15:46 ` [PATCH v4 4/5] Xarray: remove repeat check in xas_squash_marks() Kemeng Shi
2024-12-18 15:46 ` [PATCH v4 5/5] Xarray: use xa_mark_t in xas_squash_marks() to keep code consistent Kemeng Shi
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=20241218154613.58754-1-shikemeng@huaweicloud.com \
--to=shikemeng@huaweicloud.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--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