From: Josh Law <hlcj1234567@gmail.com>
To: Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Josh Law <objecting@objecting.org>
Subject: [PATCH v3 0/2] lib/idr: Fixes for infinite loop and memory leak
Date: Thu, 12 Mar 2026 18:19:46 +0000 [thread overview]
Message-ID: <20260312181948.20020-1-objecting@objecting.org> (raw)
This series includes two fixes for the IDR and IDA APIs, along with
their corresponding test cases as requested by reviewers.
1. Fix an infinite loop condition in idr_get_next() that occurs when
iterating over an ID > INT_MAX.
2. Fix a memory leak in ida_alloc_range() where an intermediate
allocated bitmap is not freed if a subsequent XArray insertion fails.
Both fixes update tools/testing/radix-tree/idr-test.c to ensure the
error paths are covered by the test suite.
Changes since v2:
- Added `idr-test.c` updates to both commits to formally test the fix conditions.
Josh Law (2):
lib/idr: fix infinite loop in idr_get_next()
lib/idr: fix memory leak in ida_alloc_range() error path
lib/idr.c | 4 +++-
tools/testing/radix-tree/idr-test.c | 19 ++++++++++++++++++-
2 files changed, 21 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2026-03-12 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 18:19 Josh Law [this message]
2026-03-12 18:19 ` [PATCH v3 1/2] lib/idr: fix infinite loop in idr_get_next() Josh Law
2026-03-12 20:55 ` Andrew Morton
2026-03-12 20:57 ` Josh Law
2026-03-12 21:15 ` Josh Law
2026-03-12 18:19 ` [PATCH v3 2/2] lib/idr: fix memory leak in ida_alloc_range() error path Josh Law
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=20260312181948.20020-1-objecting@objecting.org \
--to=hlcj1234567@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=objecting@objecting.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.