From: Anand Jain <anand.jain@oracle.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 4/5] btrfs: use GFP_KERNEL in init_ipath
Date: Thu, 1 Jun 2017 17:39:22 +0800 [thread overview]
Message-ID: <d29f764c-b08b-0687-a454-02bb02c7504a@oracle.com> (raw)
In-Reply-To: <529ad6aaf2a0814b3b42da65f7e3afa9d0576e7c.1496252765.git.dsterba@suse.com>
On 06/01/17 01:49, David Sterba wrote:
> Now that init_ipath is called either from a safe context or with
> memalloc_nofs protection, we can switch to GFP_KERNEL allocations in
> init_path and init_data_container.
Reviewed-by: Anand Jain <anand.jain@oracle.com>
Thanks, Anand
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
> fs/btrfs/backref.c | 10 +++++-----
> fs/btrfs/ioctl.c | 4 ++--
> 2 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c
> index 24865da63d8f..f723c11bb763 100644
> --- a/fs/btrfs/backref.c
> +++ b/fs/btrfs/backref.c
> @@ -16,7 +16,7 @@
> * Boston, MA 021110-1307, USA.
> */
>
> -#include <linux/vmalloc.h>
> +#include <linux/mm.h>
> #include <linux/rbtree.h>
> #include "ctree.h"
> #include "disk-io.h"
> @@ -2305,7 +2305,7 @@ struct btrfs_data_container *init_data_container(u32 total_bytes)
> size_t alloc_bytes;
>
> alloc_bytes = max_t(size_t, total_bytes, sizeof(*data));
> - data = vmalloc(alloc_bytes);
> + data = kvmalloc(alloc_bytes, GFP_KERNEL);
> if (!data)
> return ERR_PTR(-ENOMEM);
>
> @@ -2339,9 +2339,9 @@ struct inode_fs_paths *init_ipath(s32 total_bytes, struct btrfs_root *fs_root,
> if (IS_ERR(fspath))
> return (void *)fspath;
>
> - ifp = kmalloc(sizeof(*ifp), GFP_NOFS);
> + ifp = kmalloc(sizeof(*ifp), GFP_KERNEL);
> if (!ifp) {
> - vfree(fspath);
> + kvfree(fspath);
> return ERR_PTR(-ENOMEM);
> }
>
> @@ -2356,6 +2356,6 @@ void free_ipath(struct inode_fs_paths *ipath)
> {
> if (!ipath)
> return;
> - vfree(ipath->fspath);
> + kvfree(ipath->fspath);
> kfree(ipath);
> }
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index c9cdea8061bc..e4116f9248c2 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -37,7 +37,7 @@
> #include <linux/bit_spinlock.h>
> #include <linux/security.h>
> #include <linux/xattr.h>
> -#include <linux/vmalloc.h>
> +#include <linux/mm.h>
> #include <linux/slab.h>
> #include <linux/blkdev.h>
> #include <linux/uuid.h>
> @@ -4588,7 +4588,7 @@ static long btrfs_ioctl_logical_to_ino(struct btrfs_fs_info *fs_info,
>
> out:
> btrfs_free_path(path);
> - vfree(inodes);
> + kvfree(inodes);
> kfree(loi);
>
> return ret;
>
next prev parent reply other threads:[~2017-06-01 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 17:49 [PATCH 0/5] More vmalloc cleanups David Sterba
2017-05-31 17:49 ` [PATCH 1/5] btrfs: replace opencoded kvzalloc with the helper David Sterba
2017-06-01 8:04 ` Anand Jain
2017-06-01 14:25 ` David Sterba
2017-05-31 17:49 ` [PATCH 2/5] btrfs: send: use kvmalloc in iterate_dir_item David Sterba
2017-06-01 9:23 ` Anand Jain
2017-05-31 17:49 ` [PATCH 3/5] btrfs: scrub: add memalloc_nofs protection around init_ipath David Sterba
2017-06-01 9:27 ` Anand Jain
2017-05-31 17:49 ` [PATCH 4/5] btrfs: use GFP_KERNEL in init_ipath David Sterba
2017-06-01 9:39 ` Anand Jain [this message]
2017-05-31 17:49 ` [PATCH 5/5] btrfs: adjust includes after vmalloc removal 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=d29f764c-b08b-0687-a454-02bb02c7504a@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/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).