From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Peter Oberparleiter" <oberpar@linux.ibm.com>,
"Mikhail Zaslonko" <zaslonko@linux.ibm.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Steffen Klassert" <steffen.klassert@secunet.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Josh Poimboeuf" <jpoimboe@kernel.org>,
"Vasileios Almpanis" <vasileios.almpanis@virtuozzo.com>,
"Pavel Tikhomirov" <ptikhomirov@virtuozzo.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [PATCH v3 0/4] gcov: use -fprofile-update=atomic globally to fix concurrent access crashes on GCOV-enabled kernels
Date: Thu, 2 Apr 2026 14:48:55 +0200 [thread overview]
Message-ID: <3fde6bbc-09bd-4543-bbd0-8df1f7eda6a2@virtuozzo.com> (raw)
In-Reply-To: <20260401184625.2641899d@kernel.org>
On 4/2/26 03:46, Jakub Kicinski wrote:
> On Wed, 1 Apr 2026 17:20:16 +0300 Konstantin Khorenko wrote:
>> 1. Build fix for CONFIG_GCOV_PROFILE_ALL=y - skb_ext_total_length()
>> BUILD_BUG_ON failure:
>> https://lore.kernel.org/lkml/20260331165125.959833-1-khorenko@virtuozzo.com/T/#t
>>
>> 2. Runtime crash fix for zlib inflate_fast() - GCOV counter merging
>> with loop induction variables caused out-of-bounds writes on SMP:
>> https://lore.kernel.org/lkml/20260330143256.306326-1-khorenko@virtuozzo.com/T/#t
>
> Why are you merging these? The should go via different subsystems.
> How do you expect this series to be applied?
You are definitely right, Jakub.
i will create 3 different threads and note explicitly that the last commit should be applied only
after first 2 series are merged.
Will do right now!
--
Konstantin Khorenko
prev parent reply other threads:[~2026-04-02 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 14:20 [PATCH v3 0/4] gcov: use -fprofile-update=atomic globally to fix concurrent access crashes on GCOV-enabled kernels Konstantin Khorenko
2026-04-01 14:20 ` [PATCH v3 1/4] net: fix skb_ext_total_length() BUILD_BUG_ON with CONFIG_GCOV_PROFILE_ALL Konstantin Khorenko
2026-04-01 14:20 ` [PATCH v3 2/4] net: add __no_profile to skb_extensions_init() for GCOV compatibility Konstantin Khorenko
2026-04-01 14:20 ` [PATCH v3 3/4] iommu/generic_pt: disable GCOV for iommu_amdv1.o Konstantin Khorenko
2026-04-01 14:20 ` [PATCH v3 4/4] gcov: use atomic counter updates to fix concurrent access crashes Konstantin Khorenko
2026-04-01 16:55 ` Peter Oberparleiter
2026-04-02 1:46 ` [PATCH v3 0/4] gcov: use -fprofile-update=atomic globally to fix concurrent access crashes on GCOV-enabled kernels Jakub Kicinski
2026-04-02 12:48 ` Konstantin Khorenko [this message]
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=3fde6bbc-09bd-4543-bbd0-8df1f7eda6a2@virtuozzo.com \
--to=khorenko@virtuozzo.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oberpar@linux.ibm.com \
--cc=pabeni@redhat.com \
--cc=ptikhomirov@virtuozzo.com \
--cc=steffen.klassert@secunet.com \
--cc=vasileios.almpanis@virtuozzo.com \
--cc=zaslonko@linux.ibm.com \
/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