From: Christian Brauner <brauner@kernel.org>
To: Jie Jiang <jiejiang@chromium.org>
Cc: bpf@vger.kernel.org, vapier@chromium.org, andrii@kernel.org
Subject: Re: [PATCH bpf-next v2] bpf: Support uid and gid when mounting bpffs
Date: Wed, 6 Dec 2023 11:55:17 +0100 [thread overview]
Message-ID: <20231206-annahme-beide-976ce66476e4@brauner> (raw)
In-Reply-To: <20231206073624.149124-1-jiejiang@chromium.org>
On Wed, Dec 06, 2023 at 07:36:24AM +0000, Jie Jiang wrote:
> Parse uid and gid in bpf_parse_param() so that they can be passed in as
> the `data` parameter when mount() bpffs. This will be useful when we
> want to control which user/group has the control to the mounted bpffs,
> otherwise a separate chown() call will be needed.
>
> Signed-off-by: Jie Jiang <jiejiang@chromium.org>
> ---
Yes, looks good now,
Acked-by: Christian Brauner <brauner@kernel.org>
next prev parent reply other threads:[~2023-12-06 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 7:36 [PATCH bpf-next v2] bpf: Support uid and gid when mounting bpffs Jie Jiang
2023-12-06 10:55 ` Christian Brauner [this message]
2023-12-06 17:21 ` Andrii Nakryiko
2023-12-06 18:20 ` Alexei Starovoitov
2023-12-07 4:32 ` Jie Jiang
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=20231206-annahme-beide-976ce66476e4@brauner \
--to=brauner@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jiejiang@chromium.org \
--cc=vapier@chromium.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