From: Herbert Xu <herbert@gondor.apana.org.au>
To: Peter Zijlstra <peterz@infradead.org>
Cc: andriy.shevchenko@linux.intel.com, przemyslaw.kitszel@intel.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, vbabka@suse.cz,
torvalds@linux-foundation.org, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, linux-toolchains@vger.kernel.org
Subject: Re: [RFC] slab: introduce auto_kfree macro
Date: Fri, 4 Apr 2025 11:05:44 +0800 [thread overview]
Message-ID: <Z-9MiJ0nuBxYCaV2@gondor.apana.org.au> (raw)
In-Reply-To: <20250402121935.GJ25239@noisy.programming.kicks-ass.net>
Peter Zijlstra <peterz@infradead.org> wrote:
>
> The compiler *should* complain. But neither GCC nor clang actually
> appear to warn in this case.
Linus turned that warning off in 2020:
commit 78a5255ffb6a1af189a83e493d916ba1c54d8c75
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat May 9 13:57:10 2020 -0700
Stop the ad-hoc games with -Wno-maybe-initialized
You need to enable it by hand to see the warning:
make KBUILD_CFLAGS_KERNEL=-Wmaybe-uninitialized CFLAGS_MODULE=-Wmaybe-uninitialized
W=2 enables it too but it also enables lots of other crap so it's
useless.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2025-04-04 3:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 13:44 Przemek Kitszel
2025-04-02 10:32 ` Andy Shevchenko
2025-04-02 10:40 ` Andy Shevchenko
2025-04-02 12:19 ` Peter Zijlstra
2025-04-02 12:22 ` Peter Zijlstra
2025-04-02 12:57 ` Andy Shevchenko
2025-04-04 3:05 ` Herbert Xu [this message]
2025-04-02 12:21 ` Peter Zijlstra
2025-04-02 12:55 ` Andy Shevchenko
2025-04-02 10:44 ` Vlastimil Babka
2025-04-03 16:59 ` Kees Cook
2025-04-03 17:35 ` Matthew Wilcox
2025-04-03 17:46 ` Andy Shevchenko
2025-04-03 18:15 ` Linus Torvalds
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=Z-9MiJ0nuBxYCaV2@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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