linux-kernel - Re: [PATCH] io_uring/rsrc: take unsigned index in io_rsrc_node

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-prev] [day] [month] [year] [list]

Message-Id: <176912275829.523910.8844345576274421651.b4-ty@kernel.dk>
Date: Thu, 22 Jan 2026 15:59:18 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Caleb Sander Mateos <csander@...estorage.com>
Cc: io-uring@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] io_uring/rsrc: take unsigned index in
 io_rsrc_node_lookup()


On Thu, 22 Jan 2026 14:45:04 -0700, Caleb Sander Mateos wrote:
> io_rsrc_node_lookup() takes a signed int index as input and compares it
> to an unsigned length. Since the signed int is implicitly cast to an
> unsigned int for the comparison and the length is bounded by
> IORING_MAX_FIXED_FILES/IORING_MAX_REG_BUFFERS, negative indices are
> already rejected on architectures where int is at least 32 bits. Make
> this a bit clearer and avoid compiler warnings for comparisons of
> signed and unsigned values by taking an unsigned int index instead.
> 
> [...]

Applied, thanks!

[1/1] io_uring/rsrc: take unsigned index in io_rsrc_node_lookup()
      commit: 82dadc8a494758093e775336390cb31033c6f9a3

Best regards,
-- 
Jens Axboe