DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Yang Ming <ming.1.yang@nokia-sbell.com>
Cc: dev@dpdk.org, stable@dpdk.org,
	 Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v2] eal/linux: improve ASLR check
Date: Thu, 15 May 2025 13:45:09 +0200	[thread overview]
Message-ID: <CAJFAV8wXApL0njja3oOgz6JTnXBGyX6FfqL_pThB7Hu8VBJ00A@mail.gmail.com> (raw)
In-Reply-To: <20250313083733.203d132c@hermes.local>

On Thu, Mar 13, 2025 at 4:37 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> 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>

Applied, thanks.


-- 
David Marchand


      parent reply	other threads:[~2025-05-15 11:45 UTC|newest]

Thread overview: 12+ 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     ` [External] " Yang Ming
2025-03-27  8:14       ` David Marchand
2025-03-30  9:49         ` Yang Ming
2025-05-15 11:45     ` David Marchand [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=CAJFAV8wXApL0njja3oOgz6JTnXBGyX6FfqL_pThB7Hu8VBJ00A@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ming.1.yang@nokia-sbell.com \
    --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).