linux-kernel - Re: [PATCH v3] rust: num: bounded: mark _

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: <DEPIHBWRUHYA.39BLL36OTCO2D@nvidia.com>
Date: Thu, 04 Dec 2025 23:45:05 +0900
From: "Alexandre Courbot" <acourbot@...dia.com>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@...il.com>, "Alexandre Courbot"
 <acourbot@...dia.com>
Cc: "Hsiu Che Yu" <yu.whisper.personal@...il.com>, "Miguel Ojeda"
 <ojeda@...nel.org>, "Yury Norov" <yury.norov@...il.com>, "Boqun Feng"
 <boqun.feng@...il.com>, "Gary Guo" <gary@...yguo.net>,
 Björn Roy Baron <bjorn3_gh@...tonmail.com>, "Benno Lossin"
 <lossin@...nel.org>, "Andreas Hindborg" <a.hindborg@...nel.org>, "Alice
 Ryhl" <aliceryhl@...gle.com>, "Trevor Gross" <tmgross@...ch.edu>, "Danilo
 Krummrich" <dakr@...nel.org>, <rust-for-linux@...r.kernel.org>,
 <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] rust: num: bounded: mark __new as unsafe

On Thu Dec 4, 2025 at 11:28 PM JST, Miguel Ojeda wrote:
> On Thu, Dec 4, 2025 at 3:13 PM Alexandre Courbot <acourbot@...dia.com> wrote:
>>
>> Miguel, do you prefer to take this directly, or should I gather all the
>> `num/*` patches and send you a PR in one go sometime later?
>
> Just to avoid forgetting later, which ones do you mean? i.e. I have
> these in my radar:
>
>     [PATCH v3] rust: num: bounded: mark __new as unsafe
>     [PATCH] rust: num: fix typos in Bounded documentation
>     [PATCH] rust: num: bounded: rename `try_into_bitint` to `try_into_bounded`
>     One in [PATCH v2 0/7] rust: build_assert: document and fix use
> with function arguments
>
> None seems urgent, i.e. they can be added to `rust-fixes` after -rc1 I
> think, right?

Oh yes, actually I was thinking about rust-next rather than rust-fixes,
but that works as well. My point was more about taking the mental burden
of tracking this off your shoulders. :)