[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72kZgZdU4Dut3rmcWT-cujyJaP_99ekis_XdfQ-7LmgZ5Q@mail.gmail.com>
Date: Fri, 12 Sep 2025 10:27:42 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Andrew Ballance <andrewjballance@...il.com>
Cc: Joel Fernandes <joelagnelf@...dia.com>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org, John Hubbard <jhubbard@...dia.com>,
Alexandre Courbot <acourbot@...dia.com>, Timur Tabi <ttabi@...dia.com>,
Alistair Popple <apopple@...dia.com>, Miguel Ojeda <ojeda@...nel.org>
Subject: Re: Printing with overflow checks can cause modpost errors
On Fri, Sep 12, 2025 at 6:08 AM Andrew Ballance
<andrewjballance@...il.com> wrote:
>
> The pointer passed is const so rustc should assume that the c side does
> not change offset, but looks like rustc does not do that.
That is not possible -- a const pointer does not guarantee the value
will not be changed.
Cheers,
Miguel
Powered by blists - more mailing lists