From: Zorro Lang <zlang@kernel.org>
To: Lukas Herbolt <lukas@herbolt.com>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 1/1] lib/random.c fix undefined behavior on signed integer overflow.
Date: Wed, 14 Oct 2026 23:34:44 +0800 [thread overview]
Message-ID: <as-gn2UbAkwzn__7@zlang-mailbox> (raw)
In-Reply-To: <77a91ff8f43794433376c3af4362bbdd@herbolt.com>
On Mon, Oct 12, 2026 at 04:38:26PM +0200, Lukas Herbolt wrote:
> On 2026-10-12 15:44, Zorro Lang wrote:
> > On Tue, Oct 06, 2026 at 03:51:52PM +0200, Lukas Herbolt wrote:
> > > The random.c now expects that signed integer to overflow and
> > > triggers the ^MASK branch. But signed int overflow is undefined
> > > behavior and GCC can optimize this branch out with certain
> > > CFLAGS/LDFLAGS.
> > >
> > > Signed-off-by: Lukas Herbolt <lukas@herbolt.com>
> > > ---
> > > lib/random.c | 13 +++++++------
> > > 1 file changed, 7 insertions(+), 6 deletions(-)
> > >
> > > diff --git a/lib/random.c b/lib/random.c
> > > index d5c81be817c8..f767ed1d1337 100644
> > > --- a/lib/random.c
> > > +++ b/lib/random.c
> > > @@ -186,14 +186,15 @@ _random (int32_t is [2])
> > > int32_t
> > > _irandm (int32_t is [2])
> > > {
> > > - int32_t it, leh, nit;
> > > -
> > > + int32_t it, leh, nit, apply_mask;
> > > it = is [0];
> > > leh = is [1];
> > > - if (it <= 0)
> > > - it = (it + it) ^ MASK;
> > > - else
> > > - it = it + it;
> > > +
> > > +/* evaluate on original value — no UB here */
> > > + apply_mask = (it <= 0);
> > > +/* double via unsigned shift — well-defined */
> > > + it = (unsigned)it << 1;
> >
> > I'll explicitly change it to unsigned int when applying the patch.
> >
> > Reviewed-by: Zorro Lang <zlang@kernel.org>
> >
> > > + if (apply_mask) it ^= MASK;
> >
> > Ahaha, this .c program is quite legacy. I'm not sure it's worth pulling
> > in
> > <stdint.h> and <stdbool.h> just to use *bool apply_mask* and
> > *(uint32_t)*.
> >
> Yeah, I did't want to pull anything else into it.
Makes sense :)
> I will send v2 cleaning up the dead code.
OK, If you plan to send a v2, I'll hold off on merging this one and wait for
your next version.
>
> --
> -lhe
>
prev parent reply other threads:[~2026-10-14 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 13:51 [PATCH 0/1] Fix random.c UB on int overflow Lukas Herbolt
2026-10-06 13:51 ` [PATCH 1/1] lib/random.c fix undefined behavior on signed integer overflow Lukas Herbolt
2026-10-07 17:00 ` Darrick J. Wong
2026-10-08 8:23 ` Lukas Herbolt
2026-10-08 15:17 ` Darrick J. Wong
2026-10-12 13:33 ` Zorro Lang
2026-10-12 13:44 ` Zorro Lang
2026-10-12 14:38 ` Lukas Herbolt
2026-10-14 15:34 ` Zorro Lang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=as-gn2UbAkwzn__7@zlang-mailbox \
--to=zlang@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lukas@herbolt.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox