From: Christian Brauner <brauner@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Andy Lutomirski <luto@amacapital.net>,
Miklos Szeredi <mszeredi@redhat.com>,
Giuseppe Scrivano <gscrivan@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org,
linux-api@vger.kernel.org, linux-erofs@lists.ozlabs.org,
Amir Goldstein <amir73il@gmail.com>,
Gao Xiang <hsiangkao@linux.alibaba.com>
Subject: Re: [RFC PATCH] fs: allow opening overlayfs/erofs layers through O_ALT
Date: Wed, 22 Jul 2026 16:25:39 +0200 [thread overview]
Message-ID: <20260722-erraten-hinblick-erlesen-2520fd1a3726@brauner> (raw)
In-Reply-To: <CAJfpeguxCOw4cURjPVOMj5-A7JnLrmy8zx4qE9uwxg7x_Wr+zg@mail.gmail.com>
On 2026-07-20 11:22 +0200, Miklos Szeredi wrote:
> On Sun, 19 Jul 2026 at 16:13, Andy Lutomirski <luto@amacapital.net> wrote:
>
> > This gives me the willies a bit. It's very cool, but it has some
> > potential security issues that I think we need to watch out for. As
> > sort-of prior art, NTFS supports alternate streams and Reiser4, ahem,
> > supported files-as-directories.
>
> I realized that we can keep the creepiness factor minimal by
> introducing this first in procfs only. That way zero changes are
> needed in the path lookup code:
>
> sprintf(buf, "/proc/self/fd-alt/%d/%s", base_fd, alt_path);
> alt_fd = open(buf, O_PATH);
I'm still vehemently opposed to stuffing more creepy apis into procfs.
So this gets clear opposition from me.
next prev parent reply other threads:[~2026-07-22 14:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 10:11 [RFC PATCH] fs: allow opening overlayfs/erofs layers through O_ALT Miklos Szeredi
2026-07-15 16:43 ` Giuseppe Scrivano
2026-07-19 14:12 ` Andy Lutomirski
2026-07-19 18:42 ` Miklos Szeredi
2026-07-20 9:22 ` Miklos Szeredi
2026-07-22 14:25 ` Christian Brauner [this message]
2026-07-22 14:51 ` Miklos Szeredi
2026-07-22 15:44 ` Christian Brauner
2026-07-22 16:29 ` Andy Lutomirski
2026-07-23 8:22 ` Miklos Szeredi
2026-07-23 9:00 ` Andy Lutomirski
2026-07-23 9:19 ` Miklos Szeredi
2026-07-23 13:53 ` Andy Lutomirski
2026-07-30 13:57 ` Christian Brauner
2026-07-23 8:00 ` Miklos Szeredi
2026-07-23 9:20 ` Amir Goldstein
2026-07-26 17:02 ` Giuseppe Scrivano
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=20260722-erraten-hinblick-erlesen-2520fd1a3726@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=gscrivan@redhat.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
/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