From: Yang Ming <ming.1.yang@nokia-sbell.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [External] Re: [PATCH v2] eal/linux: improve ASLR check
Date: Thu, 27 Mar 2025 16:02:12 +0800 [thread overview]
Message-ID: <9fa6a076-e187-461f-9899-a53e891efb21@nokia-sbell.com> (raw)
In-Reply-To: <20250313083733.203d132c@hermes.local>
On 2025/3/13 23:37, Stephen Hemminger wrote:
> Caution: This is an external email. Please be very careful when clicking links or opening attachments. See http://nok.it/nsb for additional information.
>
> On Thu, 13 Mar 2025 14:19:03 +0800
> Yang Ming <ming.1.yang@nokia-sbell.com> wrote:
>
>> This change ensures that the current process is checked for
>> being run with 'setarch' before verifying the value of
>> '/proc/sys/kernel/randomize_va_space'. The '-R' or
>> '--addr-no-randomize' parameter of the 'setarch' command is used
>> to disable the randomization of the virtual address space.
>>
>> Fixes: af75078fece3 ("first public release")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Yang Ming <ming.1.yang@nokia-sbell.com>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
>
Hi Experts,
is there any chance to review and accept this patch?
Brs,
Yang Ming
next prev parent reply other threads:[~2025-03-27 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 9:44 [PATCH] eal/linux: enhance ASLR verification Yang Ming
2025-03-10 21:43 ` Stephen Hemminger
2025-03-12 3:13 ` Yang Ming
2025-03-12 16:29 ` Stephen Hemminger
2025-03-13 5:52 ` [External] " Yang Ming
2025-03-12 16:22 ` Stephen Hemminger
2025-03-13 6:19 ` [PATCH v2] eal/linux: improve ASLR check Yang Ming
2025-03-13 15:37 ` Stephen Hemminger
2025-03-27 8:02 ` Yang Ming [this message]
2025-03-27 8:14 ` [External] " David Marchand
2025-03-30 9:49 ` Yang Ming
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=9fa6a076-e187-461f-9899-a53e891efb21@nokia-sbell.com \
--to=ming.1.yang@nokia-sbell.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).