mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "NeilBrown" <neilb@suse.de>
To: "Sage Weil" <sage@newdream.net>
Cc: linux-kernel@vger.kernel.org, "Sage Weil" <sage@newdream.net>,
	linux-raid@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] md: avoid use of broken kzalloc mempool
Date: Tue, 4 Aug 2009 08:03:52 +1000 (EST)	[thread overview]
Message-ID: <8604b01355a1ff1ec6397d223c28b1d5.squirrel@neil.brown.name> (raw)
In-Reply-To: <1249332888-13440-1-git-send-email-sage@newdream.net>

On Tue, August 4, 2009 6:54 am, Sage Weil wrote:
> The kzalloc mempool does not re-zero items that have been used and then
> returned to the pool.  Manually zero the allocated multipath_bh instead.
>
> CC: linux-raid@vger.kernel.org
> CC: Neil Brown <neilb@suse.de>

Acked-by: NeilBrown <neilb@suse.de>

Thanks.

In fact, you don't even need the memset.  After allocation
no assumptions are made about the content of the structure.
Every field is immediately initialised except retry_list, which
is never accessed until after the object is placed on a list.h list.

So this code never needed kzalloc_pool.

Thanks,
NeilBrown

> CC: <stable@kernel.org>
> Signed-off-by: Sage Weil <sage@newdream.net>
> ---
>  drivers/md/multipath.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/md/multipath.c b/drivers/md/multipath.c
> index 237fe3f..151ce69 100644
> --- a/drivers/md/multipath.c
> +++ b/drivers/md/multipath.c
> @@ -150,6 +150,7 @@ static int multipath_make_request (struct
> request_queue *q, struct bio * bio)
>  	}
>
>  	mp_bh = mempool_alloc(conf->pool, GFP_NOIO);
> +	memset(mp_bh, 0, sizeof(*mp_bh));
>
>  	mp_bh->master_bio = bio;
>  	mp_bh->mddev = mddev;
> @@ -490,7 +491,7 @@ static int multipath_run (mddev_t *mddev)
>  	}
>  	mddev->degraded = conf->raid_disks - conf->working_disks;
>
> -	conf->pool = mempool_create_kzalloc_pool(NR_RESERVED_BUFS,
> +	conf->pool = mempool_create_kmalloc_pool(NR_RESERVED_BUFS,
>  						 sizeof(struct multipath_bh));
>  	if (conf->pool == NULL) {
>  		printk(KERN_ERR
> --
> 1.5.6.5
>


  parent reply	other threads:[~2009-08-03 22:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 20:54 Sage Weil
2009-08-03 20:54 ` [PATCH] ibmvscsi: avoid unnecessary use of kzalloc_pool Sage Weil
2009-08-03 20:54   ` [PATCH] mm: remove broken 'kzalloc' mempool Sage Weil
2009-08-03 20:57     ` Sage Weil
2009-08-03 21:19   ` [PATCH] ibmvscsi: avoid unnecessary use of kzalloc_pool Brian King
2009-08-03 21:13 ` [PATCH] md: avoid use of broken kzalloc mempool Andi Kleen
2009-08-03 21:29   ` Sage Weil
2009-08-03 22:03 ` NeilBrown [this message]
2009-08-11 21:52   ` Andrew Morton
2009-08-11 22:03     ` Sage Weil
2009-08-12 23:17     ` Neil Brown

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=8604b01355a1ff1ec6397d223c28b1d5.squirrel@neil.brown.name \
    --to=neilb@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=sage@newdream.net \
    --cc=stable@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

all inboxes | Powered by JetHome®