| 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
| ||
|
Message-ID: <CANiq72mq5TCa4NqpxOMq3-e55N8Z4757Zx_=uzVge2QfqXOprA@mail.gmail.com> Date: Wed, 3 Dec 2025 15:23:02 +0100 From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com> To: Alexandre Courbot <acourbot@...dia.com> Cc: Hsiu Che Yu <yu.whisper.personal@...il.com>, linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org, 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> Subject: Re: [PATCH v2] rust: num: bounded: mark __new as unsafe On Wed, Dec 3, 2025 at 1:29 PM Alexandre Courbot <acourbot@...dia.com> wrote: > > Wasn't it Alice who said that `__new` should be unsafe? The issue was about making it unsafe -- I added the "Otherwise" branch to make it a bit more "open", i.e. sometimes I try to make those "good first issues" in a way that it is not completely automated, e.g. here so that the new contributor has to think what it means for a function to be unsafe or not, rather than just converting it. Given Hsiu's reply in v1, it seems it worked! :) Cheers, Miguel
Powered by blists - more mailing lists