linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Alexander Potapenko" <glider@google.com>,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	"Andrew Morton" <akpm@linux-foundation.org>
Cc: "Nathan Chancellor" <nathan@kernel.org>,
	"Lukas Bulwahn" <lbulwahn@redhat.com>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	"Nicolas Schier" <nicolas.schier@linux.dev>,
	"Andrey Konovalov" <andreyknvl@gmail.com>,
	linux-kbuild@vger.kernel.org, kasan-dev@googlegroups.com,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Lukas Bulwahn" <lukas.bulwahn@redhat.com>,
	"Dmitry Vyukov" <dvyukov@google.com>
Subject: Re: [PATCH] Makefile.kcov: apply needed compiler option unconditionally in CFLAGS_KCOV
Date: Wed, 21 May 2025 16:10:47 +0200	[thread overview]
Message-ID: <61db74cd-2d6c-4880-8e80-12baa338a727@app.fastmail.com> (raw)
In-Reply-To: <CAG_fn=XTLcqa8jBTQONNDEWFMJaMTKYO+rxjoWMHESWaYVYbgA@mail.gmail.com>

On Wed, May 21, 2025, at 12:02, Alexander Potapenko wrote:
> On Tue, May 20, 2025 at 4:57 PM 'Dmitry Vyukov' via kasan-dev
> <kasan-dev@googlegroups.com> wrote:
>>
>> On Thu, 8 May 2025 at 18:44, Nathan Chancellor <nathan@kernel.org> wrote:
>> >
>> > On Wed, May 07, 2025 at 03:30:43PM +0200, Lukas Bulwahn wrote:
>> > > From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
>> > >
>> > > Commit 852faf805539 ("gcc-plugins: remove SANCOV gcc plugin") removes the
>> > > config CC_HAS_SANCOV_TRACE_PC, as all supported compilers include the
>> > > compiler option '-fsanitize-coverage=trace-pc' by now.
>> > >
>> > > The commit however misses the important use of this config option in
>> > > Makefile.kcov to add '-fsanitize-coverage=trace-pc' to CFLAGS_KCOV.
>> > > Include the compiler option '-fsanitize-coverage=trace-pc' unconditionally
>> > > to CFLAGS_KCOV, as all compilers provide that option now.
>> > >
>> > > Fixes: 852faf805539 ("gcc-plugins: remove SANCOV gcc plugin")
>> > > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
>> >
>> > Good catch.
>> >
>> > Reviewed-by: Nathan Chancellor <nathan@kernel.org>
>>
>> Reviewed-by: Dmitry Vyukov <dvyukov@google.com>
>>
>> Thanks for fixing this!
>
> @akpm, could you please take this patch at your convenience?

I have applied it on the asm-generic tree now, as this contains
the original broken commit. Sorry for missing it earlier.

      Arnd


  reply	other threads:[~2025-05-21 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250507133043.61905-1-lukas.bulwahn@redhat.com>
     [not found] ` <20250508164425.GD834338@ax162>
     [not found]   ` <CACT4Y+a=FLk--rrN0TQiKcQ+NjND_vnSRnwrrg1XzAYaUmKxhw@mail.gmail.com>
2025-05-21 10:02     ` Alexander Potapenko
2025-05-21 14:10       ` Arnd Bergmann [this message]
2025-05-22  8:18         ` Alexander Potapenko

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=61db74cd-2d6c-4880-8e80-12baa338a727@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lbulwahn@redhat.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lukas.bulwahn@redhat.com \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolas.schier@linux.dev \
    /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