linux-kernel - [RFC PATCH 0/1] IDR fix for potential id mismatch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251127092732.684959-1-jan.sokolowski@intel.com>
Date: Thu, 27 Nov 2025 10:27:31 +0100
From: Jan Sokolowski <jan.sokolowski@...el.com>
To: linux-kernel@...r.kernel.org
Cc: Jan Sokolowski <jan.sokolowski@...el.com>,
	Christian König <christian.koenig@....com>,
	Matthew Wilcox <willy@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-fsdevel@...r.kernel.org,
	linux-mm@...ck.org
Subject: [RFC PATCH 0/1] IDR fix for potential id mismatch

When debugging an issue found in drm subsystem (link to the
discussion in Link tag), a bug was found in idr library
where requesting id in range would return id outside
requested range. Didn't see in documentation that this is how
idr should behave.

This is an RFC as this library is deprecated but still in use by other
subsystems. Is this fix proper?

Link: https://lists.freedesktop.org/archives/dri-devel/2025-November/538294.html
Cc: "Christian König" <christian.koenig@....com>
Cc: Matthew Wilcox <willy@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-fsdevel@...r.kernel.org
Cc: linux-mm@...ck.org
Cc: linux-kernel@...r.kernel.org

---
Jan Sokolowski (1):
  idr: do not create idr if new id would be outside given range

 lib/idr.c | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

-- 
2.43.0