From: Christian Brauner <brauner@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Christian Brauner <brauner@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Tycho Andersen <tandersen@netflix.com>,
Tycho Andersen <tycho@tycho.pizza>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] pidfd: cleanup the usage of __pidfd_prepare's flags
Date: Thu, 25 Jan 2024 17:34:50 +0100 [thread overview]
Message-ID: <20240125-kilometer-erwischen-9077030e4326@brauner> (raw)
In-Reply-To: <20240125161734.GA778@redhat.com>
On Thu, 25 Jan 2024 17:17:34 +0100, Oleg Nesterov wrote:
> - make pidfd_create() static.
>
> - Don't pass O_RDWR | O_CLOEXEC to __pidfd_prepare() in copy_process(),
> __pidfd_prepare() adds these flags unconditionally.
>
> - Kill the flags check in __pidfd_prepare(). sys_pidfd_open() checks the
> flags itself, all other users of pidfd_prepare() pass flags = 0.
>
> [...]
Thanks!
---
Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/1] pidfd: cleanup the usage of __pidfd_prepare's flags
https://git.kernel.org/vfs/vfs/c/2502da713861
next prev parent reply other threads:[~2024-01-25 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 16:17 Oleg Nesterov
2024-01-25 16:34 ` Christian Brauner [this message]
2024-01-25 16:53 ` Oleg Nesterov
2024-01-25 16:56 ` Christian Brauner
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=20240125-kilometer-erwischen-9077030e4326@brauner \
--to=brauner@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=tandersen@netflix.com \
--cc=tycho@tycho.pizza \
/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
all inboxes | Powered by JetHome®