From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>,
Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>,
Konstantin Khorenko <khorenko@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 0/7] mm, exec: fix the MADV_DOEXEC code we carry from Oracle
Date: Wed, 04 Nov 2026 20:21:36 +0100 [thread overview]
Message-ID: <179382009675.2760255.5950188615715657150.b4-ty@b4> (raw)
In-Reply-To: <20261014-b4-prep-khorenko-vstor-149847-3-doexec-oracle-fixes-v1-0-e34cbe0d1440@virtuozzo.com>
On Wed, 14 Oct 2026 19:12:19 +0200, Konstantin Khorenko wrote:
> mm, exec: fix the MADV_DOEXEC code we carry from Oracle
>
> Fixes in the existing Oracle MADV_DOEXEC code, found while working on
> VSTOR-149847, and a refusal of preserved memory across setuid exec.
> Applies on top of "mm: keep DMA-pinned MADV_DOEXEC memory working across
> exec".
>
> [...]
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/7] oracle/mm: take a file reference when preserving a file-backed VMA
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/f4e104c2c212
[2/7] oracle/mm: refuse MADV_DOEXEC on special mappings
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/63f64110d674
[3/7] oracle/mm: keep a MADV_DOEXEC range from becoming executable
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/9c46b9df2c32
[4/7] oracle/exec, elf: look for the opt-in note in every PT_NOTE segment
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/eb564719f827
[5/7] exec: refuse to preserve memory across a privilege-changing exec
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/3bcf0711f01b
[6/7] selftests/mm: check that a setuid exec refuses preserved memory
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/8fbaf630e8a5
[7/7] selftests/mm: check MADV_DOEXEC on /dev/zero and exec permission
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/604ec9e520c8
--
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:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 17:12 Konstantin Khorenko
2026-10-14 17:12 ` [Devel] [PATCH hci-8.1 1/7] oracle/mm: take a file reference when preserving a file-backed VMA Konstantin Khorenko
2026-10-14 17:12 ` [Devel] [PATCH hci-8.1 2/7] oracle/mm: refuse MADV_DOEXEC on special mappings Konstantin Khorenko
2026-10-14 17:12 ` [Devel] [PATCH hci-8.1 3/7] oracle/mm: keep a MADV_DOEXEC range from becoming executable Konstantin Khorenko
2026-10-14 17:12 ` [Devel] [PATCH hci-8.1 4/7] oracle/exec, elf: look for the opt-in note in every PT_NOTE segment Konstantin Khorenko
2026-10-14 17:12 ` [Devel] [PATCH hci-8.1 5/7] exec: refuse to preserve memory across a privilege-changing exec Konstantin Khorenko
2026-10-14 17:12 ` [Devel] [PATCH hci-8.1 6/7] selftests/mm: check that a setuid exec refuses preserved memory Konstantin Khorenko
2026-10-14 17:12 ` [Devel] [PATCH hci-8.1 7/7] selftests/mm: check MADV_DOEXEC on /dev/zero and exec permission Konstantin Khorenko
2026-11-04 19:21 ` 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=179382009675.2760255.5950188615715657150.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=andrey.drobyshev@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.