From: "Arnd Bergmann" <arnd@arndb.de>
To: "Ian Kent" <raven@themaw.net>, "Arnd Bergmann" <arnd@kernel.org>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Christian Brauner" <brauner@kernel.org>
Cc: "Jan Kara" <jack@suse.cz>, "Miklos Szeredi" <mszeredi@redhat.com>,
"Seth Forshee (DigitalOcean)" <sforshee@kernel.org>,
"Dave Chinner" <dchinner@redhat.com>,
"Amir Goldstein" <amir73il@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] statmount: reduce runtime stack usage
Date: Wed, 13 Dec 2023 08:40:01 +0100 [thread overview]
Message-ID: <833f0dd5-ded8-4925-9c3c-639728000598@app.fastmail.com> (raw)
In-Reply-To: <eab9dee1-a542-b079-7c49-7f3cb2974e47@themaw.net>
On Wed, Dec 13, 2023, at 02:13, Ian Kent wrote:
> On 13/12/23 05:48, Arnd Bergmann wrote:
>> From: Arnd Bergmann <arnd@arndb.de>
>>
>> prepare_kstatmount() constructs a copy of 'struct kstatmount' on the stack
>> and copies it into the local variable on the stack of its caller. Because
>> of the size of this structure, this ends up overflowing the limit for
>> a single function's stack frame when prepare_kstatmount() gets inlined
>> and both copies are on the same frame without the compiler being able
>> to collapse them into one:
>>
>> fs/namespace.c:4995:1: error: stack frame size (1536) exceeds limit (1024) in '__se_sys_statmount' [-Werror,-Wframe-larger-than]
>> 4995 | SYSCALL_DEFINE4(statmount, const struct mnt_id_req __user *, req,
>>
>> Mark the inner function as noinline_for_stack so the second copy is
>> freed before calling do_statmount() enters filesystem specific code.
>> The extra copy of the structure is a bit inefficient, but this
>> system call should not be performance critical.
>
> Are you sure this is not performance sensitive, or is the performance
> critical comment not related to the system call being called many times?
>
>
> It's going to be a while (if ever) before callers change there ways.
>
> Consider what happens when a bunch of mounts are being mounted.
>
>
> First there are a lot of events and making the getting of mount info.
> more efficient means more of those events get processed (itself an issue
> that's going to need notification sub-system improvement) resulting in
> the system call being called even more.
Ok, I'll send a v2 that is more efficent. I expected it to look uglier,
but I don't think it's actually that bad:
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -4957,15 +4957,12 @@ static int prepare_kstatmount(struct kstatmount *ks, struct mnt_id_req *kreq,
if (!access_ok(buf, bufsize))
return -EFAULT;
- *ks = (struct kstatmount){
- .mask = kreq->param,
- .buf = buf,
- .bufsize = bufsize,
- .seq = {
- .size = seq_size,
- .buf = kvmalloc(seq_size, GFP_KERNEL_ACCOUNT),
- },
- };
+ memset(ks, 0, sizeof(*ks));
+ ks->mask = kreq->param,
+ ks->buf = buf,
+ ks->bufsize = bufsize,
+ ks->seq.size = seq_size,
+ ks->seq.buf = kvmalloc(seq_size, GFP_KERNEL_ACCOUNT),
if (!ks->seq.buf)
return -ENOMEM;
return 0;
prev parent reply other threads:[~2023-12-13 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 21:48 Arnd Bergmann
2023-12-13 1:13 ` Ian Kent
2023-12-13 7:40 ` Arnd Bergmann [this message]
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=833f0dd5-ded8-4925-9c3c-639728000598@app.fastmail.com \
--to=arnd@arndb.de \
--cc=amir73il@gmail.com \
--cc=arnd@kernel.org \
--cc=brauner@kernel.org \
--cc=dchinner@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=raven@themaw.net \
--cc=sforshee@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
all inboxes | Powered by JetHome®