From: Christian Brauner <brauner@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Allison Karlitskaya <allison.karlitskaya@redhat.com>,
linux-fsdevel@vger.kernel.org, lis@redhat.com
Subject: Re: [PATCH] fuse: add max_stack_depth to fuse_init_in
Date: Thu, 15 May 2025 12:10:43 +0200 [thread overview]
Message-ID: <20250515-dunkel-rochen-ad18a3423840@brauner> (raw)
In-Reply-To: <CAJfpegtS3HLCOywFYuJ7HLPVKaSu7i6pQv-GhKQ=PK3JAiz+JQ@mail.gmail.com>
On Thu, May 15, 2025 at 10:42:30AM +0200, Miklos Szeredi wrote:
> On Wed, 14 May 2025 at 14:14, Allison Karlitskaya
> <allison.karlitskaya@redhat.com> wrote:
> > Use one of the unused fields in fuse_init_in to add a max_stack_depth
> > uint32_t (matching the max_stack_depth uint32_t in fuse_init_out).
>
> This is not a fuse-only thing.
>
> What about making it a read-only sysctl attribute? E.g.
> /proc/sys/fs/max-stack-depth.
Before making this a kernel wide sysctl attribute we should have actual
users that need more than two right now. IIUC, then making this an
attribute in FUSE will happen at some point anyway. For example, if
userspace wants to have a FUSE specific stacking limit that's different
from the global limit.
next prev parent reply other threads:[~2025-05-15 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 21:02 Request for clarification about FILESYSTEM_MAX_STACK_DEPTH Allison Karlitskaya
2025-05-13 10:21 ` Miklos Szeredi
2025-05-14 12:14 ` [PATCH] fuse: add max_stack_depth to fuse_init_in Allison Karlitskaya
2025-05-14 13:32 ` Bernd Schubert
2025-05-15 8:42 ` Miklos Szeredi
2025-05-15 10:10 ` Christian Brauner [this message]
2025-05-16 9:07 ` Miklos Szeredi
2025-05-26 8:50 ` Allison Karlitskaya
2025-05-26 10:11 ` Amir Goldstein
2025-05-27 14:30 ` Miklos Szeredi
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=20250515-dunkel-rochen-ad18a3423840@brauner \
--to=brauner@kernel.org \
--cc=allison.karlitskaya@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lis@redhat.com \
--cc=miklos@szeredi.hu \
/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).