All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Anastasios Papagiannis <tasos.papagiannnis@gmail.com>
Cc: bpf@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	david@kernel.org, akpm@linux-foundation.org, andrii@kernel.org,
	ast@kernel.org, brauner@kernel.org, daniel@iogearbox.net,
	eddyz87@gmail.com, kpsingh@kernel.org, ljs@kernel.org,
	matt@bobrowski.net, memxor@gmail.com, song@kernel.org,
	sun.jian.kdev@gmail.com, utilityemal77@gmail.com,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH bpf-next v9 0/5] bpf: Add user memory access kfuncs for mm_struct
Date: Fri, 18 Sep 2026 15:40:07 +0000	[thread overview]
Message-ID: <178974600740.1015302.4891269233605977297.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260918131757.42802-1-tasos.papagiannnis@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 18 Sep 2026 16:17:52 +0300 you wrote:
> On MMU systems, during exec, argument and environment strings are copied
> into the new address space held by struct linux_binprm before that address
> space is installed on the task_struct. Existing BPF user memory helpers
> operate on the current address space or one associated with a task_struct.
> Because no task_struct refers to the new address space at this point,
> programs cannot access these strings from the bprm_check_security LSM
> hook.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v9,1/5] mm: Add copy_remote_mm_str()
    https://git.kernel.org/bpf/bpf-next/c/69d38c792c53
  - [bpf-next,v9,2/5] exec: Clear bprm->mm before dropping its reference
    https://git.kernel.org/bpf/bpf-next/c/adc7fb9955e2
  - [bpf-next,v9,3/5] bpf: Add user memory access kfuncs for mm_struct
    https://git.kernel.org/bpf/bpf-next/c/3f9d98dfed79
  - [bpf-next,v9,4/5] bpf: Mark linux_binprm->mm as trusted-or-null
    https://git.kernel.org/bpf/bpf-next/c/cca46f91737c
  - [bpf-next,v9,5/5] selftests/bpf: Test mm_struct user memory kfuncs with linux_binprm
    https://git.kernel.org/bpf/bpf-next/c/b5501fb38ff7

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-18 15:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 13:17 [PATCH bpf-next v9 0/5] bpf: Add user memory access kfuncs for mm_struct Anastasios Papagiannis
2026-09-18 13:17 ` [PATCH bpf-next v9 1/5] mm: Add copy_remote_mm_str() Anastasios Papagiannis
2026-09-18 14:36   ` bot+bpf-ci
2026-09-18 13:17 ` [PATCH bpf-next v9 2/5] exec: Clear bprm->mm before dropping its reference Anastasios Papagiannis
2026-09-18 13:17 ` [PATCH bpf-next v9 3/5] bpf: Add user memory access kfuncs for mm_struct Anastasios Papagiannis
2026-09-18 13:17 ` [PATCH bpf-next v9 4/5] bpf: Mark linux_binprm->mm as trusted-or-null Anastasios Papagiannis
2026-09-18 14:03   ` sashiko-bot
2026-09-18 14:39     ` Anastasios Papagiannis
2026-09-18 13:17 ` [PATCH bpf-next v9 5/5] selftests/bpf: Test mm_struct user memory kfuncs with linux_binprm Anastasios Papagiannis
2026-09-18 15:40 ` patchwork-bot+netdevbpf [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=178974600740.1015302.4891269233605977297.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brauner@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=david@kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=matt@bobrowski.net \
    --cc=memxor@gmail.com \
    --cc=song@kernel.org \
    --cc=sun.jian.kdev@gmail.com \
    --cc=tasos.papagiannnis@gmail.com \
    --cc=utilityemal77@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.