Re: [PATCH 10/10] compiler: Remove uninitialized_var() macro

From
Miguel Ojeda <hidden>
Date
2020-06-04 00:50:44
Also in
linux-block, linux-clk, linux-ide, linux-mm, linux-spi, linux-wireless, lkml
Reply to
Kees Cook, 2020-06-03
Hi Kees,

On Thu, Jun 4, 2020 at 1:32 AM Kees Cook [off-list ref] wrote:
Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings
(e.g. "unused variable"). If the compiler thinks it is uninitialized,
either simply initialize the variable or make compiler changes.

As recommended[2] by[3] Linus[4], remove the macro.

[1] https://lore.kernel.org/lkml/20200603174714.192027-1-glider@google.com/ (local)
[2] https://lore.kernel.org/lkml/CA+55aFw+Vbj0i=1TGqCR5vQkCzWJ0QxK6CernOU6eedsudAixw@mail.gmail.com/ (local)
[3] https://lore.kernel.org/lkml/CA+55aFwgbgqhbp1fkxvRKEpzyR5J8n1vKT1VZdz9knmPuXhOeg@mail.gmail.com/ (local)
[4] https://lore.kernel.org/lkml/CA+55aFz2500WfbKXAx8s67wrm9=yVJu65TpLgN_ybYNv0VEOKA@mail.gmail.com/ (local)

Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Kees Cook <redacted>
---
+1, one less trick split between `compiler*` files.

Reviewed-by: Miguel Ojeda <redacted>

Cheers,
Miguel
Thread (51 messages) 51 messages, 12 authors, last reply 2020-06-15
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help