[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nZrHzhYztDMQnhuW3hhg3eXtwM+kZMd=3ARbWZTZWe9g@mail.gmail.com>
Date: Mon, 17 Mar 2025 11:23:31 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Benno Lossin <benno.lossin@...ton.me>
Cc: Tamir Duberstein <tamird@...il.com>, Danilo Krummrich <dakr@...nel.org>,
Andrew Ballance <andrewjballance@...il.com>, Alice Ryhl <aliceryhl@...gle.com>,
Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Andreas Hindborg <a.hindborg@...nel.org>, Trevor Gross <tmgross@...ch.edu>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] rust: alloc: replace `Vec::set_len` with `inc_len`
On Mon, Mar 17, 2025 at 10:58 AM Benno Lossin <benno.lossin@...ton.me> wrote:
>
> What if this overflows? Do we always have overflow debugging on when
> debug assertions are enabled? If yes, then this is fine.
No, they are independent settings.
> This change seems wrong unless the code was wrong to begin with.
Yeah, even if it is correct, it should definitely be described in the
commit log, because it does look like a functional change.
Cheers,
Miguel
Powered by blists - more mailing lists