From: Christoph Hellwig <hch@infradead.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Hou Tao <houtao@huaweicloud.com>,
Alexey Gladkov <legion@kernel.org>,
bpf@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Subject: Re: [PATCH v1] fs: Add kfuncs to handle idmapped mounts
Date: Thu, 6 Jul 2023 07:37:35 -0700 [thread overview]
Message-ID: <ZKbRrziFf4tf09vo@infradead.org> (raw)
In-Reply-To: <20230704-anrollen-beenden-9187c7b1b570@brauner>
On Tue, Jul 04, 2023 at 03:01:21PM +0200, Christian Brauner wrote:
> That's too much stability for my taste for these helpers. The helpers
> here exposed have been modified multiple times and once we wean off
> idmapped mounts from user namespaces completely they will change again.
> So I'm fine if they're traceable but not as kfuncs with any - even
> minimal - stability guarantees.
I fully agree. I also don't think any eBPF program has any business
looking at idmapping.
next prev parent reply other threads:[~2023-07-06 14:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 11:08 [PATCH v1] fs: Add kfuncs to handle idmapped mounts Alexey Gladkov
2023-07-04 11:42 ` Hou Tao
2023-07-04 13:01 ` Christian Brauner
2023-07-04 15:05 ` Alexey Gladkov
2023-07-06 1:10 ` Alexei Starovoitov
2023-07-06 7:22 ` Christian Brauner
2023-07-07 1:04 ` Alexei Starovoitov
2023-07-06 14:37 ` Christoph Hellwig [this message]
2023-07-04 15:11 ` Alexey Gladkov
2023-07-04 15:28 ` Christian Brauner
2023-07-05 13:43 ` Alexey Gladkov
2023-07-05 14:18 ` Christian Brauner
2023-07-05 15:28 ` Alexey Gladkov
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=ZKbRrziFf4tf09vo@infradead.org \
--to=hch@infradead.org \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=houtao@huaweicloud.com \
--cc=legion@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).