From: Alex Elder <elder@dreamhost.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Yehuda Sadeh <yehuda@hq.newdream.net>,
Sage Weil <sage@newdream.net>,
ceph-devel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] rbd: use gfp_flags parameter in rbd_header_from_disk()
Date: Wed, 18 Apr 2012 14:17:25 +0000 [thread overview]
Message-ID: <4F8ECCF5.5000501@dreamhost.com> (raw)
In-Reply-To: <20120322063309.GC7369@elgon.mountain>
On 03/22/2012 01:33 AM, Dan Carpenter wrote:
> We should use the gfp_flags that the caller specified instead of
> GFP_KERNEL here.
>
> There is only one caller and it uses GFP_KERNEL, so this change is just
> a cleanup and doesn't change how the code works.
>
> Signed-off-by: Dan Carpenter<dan.carpenter@oracle.com>
This looks good. Sorry it didn't get committed earlier.
Reviewed-by: Alex Elder <elder@dreamhost.com>
> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
> index a6278e7..fc9341f 100644
> --- a/drivers/block/rbd.c
> +++ b/drivers/block/rbd.c
> @@ -474,11 +474,11 @@ static int rbd_header_from_disk(struct rbd_image_header *header,
> return -ENOMEM;
> if (snap_count) {
> header->snap_names = kmalloc(header->snap_names_len,
> - GFP_KERNEL);
> + gfp_flags);
> if (!header->snap_names)
> goto err_snapc;
> header->snap_sizes = kmalloc(snap_count * sizeof(u64),
> - GFP_KERNEL);
> + gfp_flags);
> if (!header->snap_sizes)
> goto err_names;
> } else {
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2012-04-18 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 6:33 [patch] rbd: use gfp_flags parameter in rbd_header_from_disk() Dan Carpenter
2012-04-18 14:17 ` Alex Elder [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=4F8ECCF5.5000501@dreamhost.com \
--to=elder@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=sage@newdream.net \
--cc=yehuda@hq.newdream.net \
/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