From: Anand Jain <anand.jain@oracle.com>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>, linux-btrfs@vger.kernel.org
Cc: Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: Re: [PATCH 6/7] btrfs: Allocate btrfs_ioctl_defrag_range_args on stack
Date: Wed, 28 Jul 2021 14:27:12 +0800 [thread overview]
Message-ID: <a3c30a94-a2ef-1cda-a3f7-67ed839ba4c7@oracle.com> (raw)
In-Reply-To: <4b5d49128b43de57f5abfa9c922eb6cef3be9cba.1627418762.git.rgoldwyn@suse.com>
On 28/07/2021 05:17, Goldwyn Rodrigues wrote:
> From: Goldwyn Rodrigues <rgoldwyn@suse.com>
>
> Instead of using kmalloc() to allocate btrfs_ioctl_defrag_range_args,
> allocate btrfs_ioctl_defrag_range_args on stack.
>
> sizeof(btrfs_ioctl_defrag_range_args) = 48
>
> Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
Looks good. A nit is below.
Reviewed-by: Anand Jain <anand.jain@oracle.com>
> ---
> fs/btrfs/ioctl.c | 24 ++++++++----------------
> 1 file changed, 8 insertions(+), 16 deletions(-)
>
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index 291c16d8576b..bc38a1af45c7 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -3096,7 +3096,7 @@ static int btrfs_ioctl_defrag(struct file *file, void __user *argp)
> {
> struct inode *inode = file_inode(file);
> struct btrfs_root *root = BTRFS_I(inode)->root;
> - struct btrfs_ioctl_defrag_range_args *range;
> + struct btrfs_ioctl_defrag_range_args range = {0};
> int ret;
>
> ret = mnt_want_write_file(file);
> @@ -3128,33 +3128,25 @@ static int btrfs_ioctl_defrag(struct file *file, void __user *argp)
> goto out;
> }
>
> - range = kzalloc(sizeof(*range), GFP_KERNEL);
> - if (!range) {
> - ret = -ENOMEM;
> - goto out;
> - }
> -
> if (argp) {
> - if (copy_from_user(range, argp,
> - sizeof(*range))) {
> + if (copy_from_user(&range, argp,
> + sizeof(range))) {
Nit.
This fits in a line.
> ret = -EFAULT;
> - kfree(range);
> goto out;
> }
> /* compression requires us to start the IO */
> - if ((range->flags & BTRFS_DEFRAG_RANGE_COMPRESS)) {
> - range->flags |= BTRFS_DEFRAG_RANGE_START_IO;
> - range->extent_thresh = (u32)-1;
> + if ((range.flags & BTRFS_DEFRAG_RANGE_COMPRESS)) {
> + range.flags |= BTRFS_DEFRAG_RANGE_START_IO;
> + range.extent_thresh = (u32)-1;
> }
> } else {
> /* the rest are all set to zero by kzalloc */
> - range->len = (u64)-1;
> + range.len = (u64)-1;
> }
> ret = btrfs_defrag_file(file_inode(file), file,
> - range, BTRFS_OLDEST_GENERATION, 0);
> + &range, BTRFS_OLDEST_GENERATION, 0);
> if (ret > 0)
> ret = 0;
> - kfree(range);
> break;
> default:
> ret = -EINVAL;
>
next prev parent reply other threads:[~2021-07-28 6:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 12:51 [PATCH 0/7] Change allocation from kmalloc() to stack Goldwyn Rodrigues
2021-07-27 21:17 ` [PATCH 1/7] btrfs: Allocate walk_control on stack Goldwyn Rodrigues
2021-07-28 5:11 ` Anand Jain
2021-07-28 5:25 ` Anand Jain
2021-07-28 11:08 ` David Sterba
2021-07-27 21:17 ` [PATCH 2/7] btrfs: Allocate file_ra_state " Goldwyn Rodrigues
2021-07-28 5:29 ` Anand Jain
2021-07-27 21:17 ` [PATCH 3/7] btrfs: Allocate btrfs_ioctl_get_subvol_info_args " Goldwyn Rodrigues
2021-07-28 5:59 ` Anand Jain
2021-07-29 17:08 ` David Sterba
2021-07-29 17:22 ` David Sterba
2021-07-27 21:17 ` [PATCH 4/7] btrfs: Allocate btrfs_ioctl_balance_args " Goldwyn Rodrigues
2021-07-28 0:02 ` Darrick J. Wong
2021-07-28 2:04 ` Goldwyn Rodrigues
2021-07-28 1:19 ` kernel test robot
2021-07-27 21:17 ` [PATCH 5/7] btrfs: Allocate btrfs_ioctl_quota_rescan_args " Goldwyn Rodrigues
2021-07-28 6:01 ` Anand Jain
2021-07-27 21:17 ` [PATCH 6/7] btrfs: Allocate btrfs_ioctl_defrag_range_args " Goldwyn Rodrigues
2021-07-28 6:27 ` Anand Jain [this message]
2021-07-27 21:17 ` [PATCH 7/7] btrfs: Alloc backref_ctx " Goldwyn Rodrigues
2021-07-28 6:30 ` Anand Jain
-- strict thread matches above, loose matches on Subject: below --
2021-07-27 21:17 [PATCH 0/7] Allocate structures on stack instead of kmalloc() Goldwyn Rodrigues
2021-07-29 16:51 ` David Sterba
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=a3c30a94-a2ef-1cda-a3f7-67ed839ba4c7@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rgoldwyn@suse.com \
--cc=rgoldwyn@suse.de \
/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).