linux-kernel - Re: [RFC PATCH 03/13] usb: remove the usage of the list iterator after the loop

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANiq72k_PUBPVL1Fx4HLm_WO66RuSsi0oSsKRhssCYRNGbY84Q@mail.gmail.com>
Date:   Sun, 27 Feb 2022 19:12:11 +0100
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     Martin Uecker <uecker@...raz.at>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 03/13] usb: remove the usage of the list iterator
 after the loop

On Sat, Feb 26, 2022 at 3:43 AM Martin Uecker <uecker@...raz.at> wrote:
>
> Roughly the same group of people / companies that
> write the compilers also control what goes into the
> standard. They then like to point to the standard

Indeed, at least to a substantial degree.

> For signed overflow, I am not entirely sure what the
> right choice is.  Wrapping for signed overflow also seems
> dangerous. I use UBsan to find such issues in my code, and
> this would not really work if signed overflow was defined
> to wrap.

UBsan and similar tooling may still be used to find whatever behavior
one wants, whether defined or not. UBSan already has non-UB checks.

Cheers,
Miguel