From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: devel@openvz.org, Konstantin Khorenko <khorenko@virtuozzo.com>
Subject: Re: [Devel] [PATCH hci-8.1 0/2] ms/kbuild: GCOV follow-ups to the prefer-atomic fix
Date: Mon, 19 Oct 2026 21:54:42 +0200 [thread overview]
Message-ID: <179243968207.3623378.11791104629565073289.b4-ty@b4> (raw)
In-Reply-To: <20261019-b4-prep-khorenko-vstor-148131-gcov-followups-v1-0-2932ec685608@virtuozzo.com>
On Mon, 19 Oct 2026 20:26:49 +0200, Konstantin Khorenko wrote:
> ms/kbuild: GCOV follow-ups to the prefer-atomic fix
>
> Two follow-ups to commit 6e1a837a05d4 ("ms/gcov: use atomic counter
> updates to fix concurrent access crashes"). Peter Oberparleiter suggested
> them while reviewing the upstream patch.
>
> Both are taken from the akpm/mm tree, branch mm-nonmm-stable, and are not
> in Linus's tree yet:
>
> [...]
Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.22.9.vz10, thanks!
[1/2] ms/kbuild: use $(CFLAGS_GCOV) in the prefer-atomic try-run test
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/bcaa25137dc6
[2/2] ms/kbuild: move GCOV flags to scripts/Makefile.gcov
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/8f2170c160be
--
Konstantin Khorenko <khorenko@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-10-19 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 18:26 Konstantin Khorenko
2026-10-19 18:26 ` [Devel] [PATCH hci-8.1 1/2] ms/kbuild: use $(CFLAGS_GCOV) in the prefer-atomic try-run test Konstantin Khorenko
2026-10-19 18:29 ` no-reply
2026-10-19 18:26 ` [Devel] [PATCH hci-8.1 2/2] ms/kbuild: move GCOV flags to scripts/Makefile.gcov Konstantin Khorenko
2026-10-19 18:30 ` no-reply
2026-10-19 19:54 ` 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=179243968207.3623378.11791104629565073289.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
/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