Hi Kees, On Thu, Jun 4, 2020 at 1:32 AM Kees Cook <keesc...@chromium.org> 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-gli...@google.com/ > [2] > https://lore.kernel.org/lkml/CA+55aFw+Vbj0i=1tgqcr5vqkczwj0qxk6cernou6eedsuda...@mail.gmail.com/ > [3] > https://lore.kernel.org/lkml/ca+55afwgbgqhbp1fkxvrkepzyr5j8n1vkt1vzdz9knmpuxh...@mail.gmail.com/ > [4] > https://lore.kernel.org/lkml/CA+55aFz2500WfbKXAx8s67wrm9=yvju65tplgn_ybynv0ve...@mail.gmail.com/ > > Suggested-by: Linus Torvalds <torva...@linux-foundation.org> > Signed-off-by: Kees Cook <keesc...@chromium.org> > ---
+1, one less trick split between `compiler*` files. Reviewed-by: Miguel Ojeda <miguel.ojeda.sando...@gmail.com> Cheers, Miguel
