From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Arnd Bergmann <arnd@kernel.org>, Mark Fasheh <mark@fasheh.com>,
Joel Becker <jlbec@evilplan.org>,
akpm <akpm@linux-foundation.org>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"David Sterba" <dsterba@suse.com>,
"Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Jan Höppner" <hoeppner@linux.ibm.com>,
"Christian Brauner" <brauner@kernel.org>,
ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ocfs2: reduce ioctl stack usage
Date: Tue, 18 Apr 2023 09:44:25 +0800 [thread overview]
Message-ID: <1cd0f938-72b8-2686-1db9-d8c229700e14@linux.alibaba.com> (raw)
In-Reply-To: <20230417205631.1956027-1-arnd@kernel.org>
On 4/18/23 4:56 AM, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> On 32-bit architectures with KASAN_STACK enabled, the total stack usage
> of the ocfs2_ioctl function grows beyond the warning limit:
>
> fs/ocfs2/ioctl.c: In function 'ocfs2_ioctl':
> fs/ocfs2/ioctl.c:934:1: error: the frame size of 1448 bytes is larger than 1400 bytes [-Werror=frame-larger-than=]
>
> Move each of the variables into a basic block, and mark ocfs2_info_handle()
> as noinline_for_stack, in order to have the variable share stack slots.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Looks good.
Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
> fs/ocfs2/ioctl.c | 37 ++++++++++++++++++++++++++-----------
> 1 file changed, 26 insertions(+), 11 deletions(-)
>
> diff --git a/fs/ocfs2/ioctl.c b/fs/ocfs2/ioctl.c
> index 811a6ea374bb..b1550ba73f96 100644
> --- a/fs/ocfs2/ioctl.c
> +++ b/fs/ocfs2/ioctl.c
> @@ -803,8 +803,8 @@ static int ocfs2_get_request_ptr(struct ocfs2_info *info, int idx,
> * a better backward&forward compatibility, since a small piece of
> * request will be less likely to be broken if disk layout get changed.
> */
> -static int ocfs2_info_handle(struct inode *inode, struct ocfs2_info *info,
> - int compat_flag)
> +static noinline_for_stack int
> +ocfs2_info_handle(struct inode *inode, struct ocfs2_info *info, int compat_flag)
> {
> int i, status = 0;
> u64 req_addr;
> @@ -840,27 +840,26 @@ static int ocfs2_info_handle(struct inode *inode, struct ocfs2_info *info,
> long ocfs2_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
> {
> struct inode *inode = file_inode(filp);
> - int new_clusters;
> - int status;
> - struct ocfs2_space_resv sr;
> - struct ocfs2_new_group_input input;
> - struct reflink_arguments args;
> - const char __user *old_path;
> - const char __user *new_path;
> - bool preserve;
> - struct ocfs2_info info;
> void __user *argp = (void __user *)arg;
> + int status;
>
> switch (cmd) {
> case OCFS2_IOC_RESVSP:
> case OCFS2_IOC_RESVSP64:
> case OCFS2_IOC_UNRESVSP:
> case OCFS2_IOC_UNRESVSP64:
> + {
> + struct ocfs2_space_resv sr;
> +
> if (copy_from_user(&sr, (int __user *) arg, sizeof(sr)))
> return -EFAULT;
>
> return ocfs2_change_file_space(filp, cmd, &sr);
> + }
> case OCFS2_IOC_GROUP_EXTEND:
> + {
> + int new_clusters;
> +
> if (!capable(CAP_SYS_RESOURCE))
> return -EPERM;
>
> @@ -873,8 +872,12 @@ long ocfs2_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
> status = ocfs2_group_extend(inode, new_clusters);
> mnt_drop_write_file(filp);
> return status;
> + }
> case OCFS2_IOC_GROUP_ADD:
> case OCFS2_IOC_GROUP_ADD64:
> + {
> + struct ocfs2_new_group_input input;
> +
> if (!capable(CAP_SYS_RESOURCE))
> return -EPERM;
>
> @@ -887,7 +890,14 @@ long ocfs2_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
> status = ocfs2_group_add(inode, &input);
> mnt_drop_write_file(filp);
> return status;
> + }
> case OCFS2_IOC_REFLINK:
> + {
> + struct reflink_arguments args;
> + const char __user *old_path;
> + const char __user *new_path;
> + bool preserve;
> +
> if (copy_from_user(&args, argp, sizeof(args)))
> return -EFAULT;
> old_path = (const char __user *)(unsigned long)args.old_path;
> @@ -895,11 +905,16 @@ long ocfs2_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
> preserve = (args.preserve != 0);
>
> return ocfs2_reflink_ioctl(inode, old_path, new_path, preserve);
> + }
> case OCFS2_IOC_INFO:
> + {
> + struct ocfs2_info info;
> +
> if (copy_from_user(&info, argp, sizeof(struct ocfs2_info)))
> return -EFAULT;
>
> return ocfs2_info_handle(inode, &info, 0);
> + }
> case FITRIM:
> {
> struct super_block *sb = inode->i_sb;
next prev parent reply other threads:[~2023-04-18 1:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 20:56 Arnd Bergmann
2023-04-18 1:44 ` Joseph Qi [this message]
2023-04-18 2:29 ` Mark Fasheh
[not found] ` <20230418-fortgehen-inkubationszeit-5d3db3f0c2b1@brauner>
2023-04-18 9:37 ` Joseph Qi
2023-04-18 12:56 ` Christian Brauner
2023-04-18 18:02 ` Theodore Ts'o
2023-04-19 2:00 ` Joseph Qi
2023-04-19 21:21 ` Andrew Morton
2023-04-20 9:34 ` Christian Brauner
2023-04-20 17:01 ` Mark Fasheh
2023-04-24 8:24 ` Christian Brauner
2023-04-20 20:48 ` Al Viro
2023-04-24 8:10 ` Christian Brauner
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=1cd0f938-72b8-2686-1db9-d8c229700e14@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=christoph.boehmwalder@linbit.com \
--cc=dsterba@suse.com \
--cc=hoeppner@linux.ibm.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=martin.petersen@oracle.com \
--cc=ocfs2-devel@oss.oracle.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
all inboxes | Powered by JetHome®