All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Song Liu <songliubraving@fb.com>
Cc: x86@kernel.org, bpf@vger.kernel.org, netdev@vger.kernel.org,
	tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, ast@kernel.org,
	daniel@iogearbox.net, andrii@kernel.org, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 2/7] set_memory: introduce set_memory_[ro|x]_noalias
Date: Tue, 16 Nov 2021 09:00:51 +0100	[thread overview]
Message-ID: <20211116080051.GU174703@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20211116071347.520327-3-songliubraving@fb.com>

On Mon, Nov 15, 2021 at 11:13:42PM -0800, Song Liu wrote:
> These allow setting ro/x for module_alloc() mapping, while leave the
> linear mapping rw/nx.

This needs a very strong rationale for *why*. How does this not
trivially circumvent W^X ?

       reply	other threads:[~2021-11-16  8:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211116071347.520327-1-songliubraving@fb.com>
     [not found] ` <20211116071347.520327-3-songliubraving@fb.com>
2021-11-16  8:00   ` Peter Zijlstra [this message]
2021-11-17 21:36     ` [PATCH bpf-next 2/7] set_memory: introduce set_memory_[ro|x]_noalias Song Liu
2021-11-17 22:01       ` Peter Zijlstra
2021-11-17 23:57         ` Song Liu
2021-11-18  0:11           ` Song Liu
2021-11-18  7:54           ` Peter Zijlstra
2021-11-18 17:16             ` Song Liu
2021-11-18 18:28               ` Peter Zijlstra
2021-11-18 18:39                 ` Song Liu
2021-11-18 18:58                   ` Peter Zijlstra
2021-11-19  4:14                     ` Song Liu
2021-11-19  9:35                       ` Peter Zijlstra
2021-11-19 16:06                         ` Johannes Weiner

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=20211116080051.GU174703@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bp@alien8.de \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=kernel-team@fb.com \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 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.