From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>,
Konstantin Khorenko <khorenko@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v2 0/2] mm, binfmt_elf: two fixes also posted to mainline
Date: Wed, 04 Nov 2026 20:16:04 +0100 [thread overview]
Message-ID: <179381976414.2760255.4125118775697990860.b4-ty@b4> (raw)
In-Reply-To: <20261104-b4-prep-khorenko-vstor-149847-1-upstream-fixes-v2-0-2974ec52f0fe@virtuozzo.com>
On Wed, 04 Nov 2026 19:05:39 +0100, Konstantin Khorenko wrote:
> mm, binfmt_elf: two fixes also posted to mainline
>
> Two independent fixes for bugs that mainline has as well. Both are
> posted to mainline; the backport notes name what differs in this tree.
>
> The MADV_DOEXEC series apply on top of this one, in this order:
>
> [...]
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.18.vz10, thanks!
[1/2] mm/huge_memory: recheck a special PMD under the lock in copy_huge_pmd()
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/ed1299611b83
[2/2] binfmt_elf: return the real error when program headers cannot be loaded
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/b45c540e7358
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-11-04 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 18:05 Konstantin Khorenko
2026-11-04 18:05 ` [Devel] [PATCH hci-8.1 v2 1/2] mm/huge_memory: recheck a special PMD under the lock in copy_huge_pmd() Konstantin Khorenko
2026-11-04 18:08 ` no-reply
2026-11-04 18:05 ` [Devel] [PATCH hci-8.1 v2 2/2] binfmt_elf: return the real error when program headers cannot be loaded Konstantin Khorenko
2026-11-04 18:08 ` no-reply
2026-11-04 19:16 ` 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=179381976414.2760255.4125118775697990860.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
--cc=ptikhomirov@virtuozzo.com \
--cc=vasileios.almpanis@virtuozzo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.