All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: David Rientjes <rientjes@google.com>,
	Lars Ellenberg <drbd-dev@lists.linbit.com>
Cc: linux-kernel@vger.kernel.org, drbd-user@lists.linbit.com
Subject: Re: [Drbd-dev] [patch 1/2] block, drbd: fix drbd_req_new() initialization
Date: Sat, 7 Mar 2015 17:33:55 -0700	[thread overview]
Message-ID: <54FB98F3.2050308@fb.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1503071623250.31688@chino.kir.corp.google.com>

On 03/07/2015 05:24 PM, David Rientjes wrote:
> mempool_alloc() does not support __GFP_ZERO since elements may come from
> memory that has already been released by mempool_free().
>
> Remove __GFP_ZERO from mempool_alloc() in drbd_req_new() and properly
> initialize it to 0.

You should add it to mempool instead, avoid having this issue show up 
for other folks as well. It'd be trivial to do. Normal ->alloc() should 
honor __GFP_ZERO, just do the same manually for removing an item from 
the internal pool.

-- 
Jens Axboe


WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@fb.com>
To: David Rientjes <rientjes@google.com>,
	Lars Ellenberg <drbd-dev@lists.linbit.com>
Cc: <linux-kernel@vger.kernel.org>, <drbd-user@lists.linbit.com>
Subject: Re: [patch 1/2] block, drbd: fix drbd_req_new() initialization
Date: Sat, 7 Mar 2015 17:33:55 -0700	[thread overview]
Message-ID: <54FB98F3.2050308@fb.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1503071623250.31688@chino.kir.corp.google.com>

On 03/07/2015 05:24 PM, David Rientjes wrote:
> mempool_alloc() does not support __GFP_ZERO since elements may come from
> memory that has already been released by mempool_free().
>
> Remove __GFP_ZERO from mempool_alloc() in drbd_req_new() and properly
> initialize it to 0.

You should add it to mempool instead, avoid having this issue show up 
for other folks as well. It'd be trivial to do. Normal ->alloc() should 
honor __GFP_ZERO, just do the same manually for removing an item from 
the internal pool.

-- 
Jens Axboe


  parent reply	other threads:[~2015-03-12 23:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08  0:24 [Drbd-dev] [patch 1/2] block, drbd: fix drbd_req_new() initialization David Rientjes
2015-03-08  0:24 ` David Rientjes
2015-03-08  0:24 ` [Drbd-dev] [patch 2/2] block, drbd: use mempool_create_slab_pool() David Rientjes
2015-03-08  0:24   ` David Rientjes
2015-03-08  0:33 ` Jens Axboe [this message]
2015-03-08  0:33   ` [patch 1/2] block, drbd: fix drbd_req_new() initialization Jens Axboe
2015-03-08  0:53   ` [Drbd-dev] " David Rientjes
2015-03-08  0:53     ` David Rientjes
2015-03-08  1:03     ` [Drbd-dev] " Jens Axboe
2015-03-08  1:03       ` Jens Axboe
2015-03-08  1:27       ` [Drbd-dev] " David Rientjes
2015-03-08  1:27         ` David Rientjes
2015-03-08  1:45         ` [Drbd-dev] " Jens Axboe
2015-03-08  1:45           ` Jens Axboe
2015-03-13 23:24         ` [Drbd-dev] " David Rientjes
2015-03-13 23:24           ` David Rientjes
2015-03-10 10:38 ` [Drbd-dev] [DRBD-user] " Lars Ellenberg
2015-03-10 10:38   ` Lars Ellenberg
2015-03-10 19:28   ` [Drbd-dev] " David Rientjes
2015-03-10 19:28     ` David Rientjes

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=54FB98F3.2050308@fb.com \
    --to=axboe@fb.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=drbd-user@lists.linbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rientjes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.