linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Streetman <ddstreet@ieee.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Minchan Kim <minchan@kernel.org>,
	Christoph Lameter <cl@linux.com>,
	Pekka Enberg <penberg@kernel.org>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Michal Hocko <mhocko@suse.cz>,
	David Rientjes <rientjes@google.com>,
	Linux-MM <linux-mm@kvack.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [RFC][PATCH 4/5] mm/zpool: allow NULL `zpool' pointer in zpool_destroy_pool()
Date: Wed, 10 Jun 2015 16:59:53 -0400	[thread overview]
Message-ID: <CALZtONAyQn1qGusF4TXcS1FHmiHNmJT+Wrh2G6j7OYA=R+Q0dQ@mail.gmail.com> (raw)
In-Reply-To: <1433851493-23685-5-git-send-email-sergey.senozhatsky@gmail.com>

On Tue, Jun 9, 2015 at 8:04 AM, Sergey Senozhatsky
<sergey.senozhatsky@gmail.com> wrote:
> zpool_destroy_pool() does not tolerate a NULL zpool pointer
> argument and performs a NULL-pointer dereference. Although
> there is only one zpool_destroy_pool() user (as of 4.1),
> still update it to be coherent with the corresponding
> destroy() functions of the remainig pool-allocators (slab,
> mempool, etc.), which now allow NULL pool-pointers.
>
> For consistency, tweak zpool_destroy_pool() and NULL-check the
> pointer there.
>
> Proposed by Andrew Morton.
>
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> Reported-by: Andrew Morton <akpm@linux-foundation.org>
> LKML-reference: https://lkml.org/lkml/2015/6/8/583

Acked-by: Dan Streetman <ddstreet@ieee.org>

> ---
>  mm/zpool.c | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/mm/zpool.c b/mm/zpool.c
> index bacdab6..2f59b90 100644
> --- a/mm/zpool.c
> +++ b/mm/zpool.c
> @@ -202,6 +202,9 @@ struct zpool *zpool_create_pool(char *type, char *name, gfp_t gfp,
>   */
>  void zpool_destroy_pool(struct zpool *zpool)
>  {
> +       if (unlikely(!zpool))
> +               return;
> +
>         pr_info("destroying pool type %s\n", zpool->type);
>
>         spin_lock(&pools_lock);
> --
> 2.4.3.368.g7974889
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2015-06-10 21:00 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 12:04 [RFC][PATCH 0/5] do not dereference NULL pools in pools' destroy() functions Sergey Senozhatsky
2015-06-09 12:04 ` [RFC][PATCH 1/5] mm/slab_common: allow NULL cache pointer in kmem_cache_destroy() Sergey Senozhatsky
2015-06-17 23:14   ` David Rientjes
2015-06-17 23:52     ` Sergey Senozhatsky
2015-06-19 15:50       ` Julia Lawall
2015-08-06 14:21         ` Sergey Senozhatsky
2015-08-06 14:27           ` Julia Lawall
2015-08-06 14:29             ` Sergey Senozhatsky
2015-06-20 16:25       ` Julia Lawall
2015-07-16  8:26         ` Sergey Senozhatsky
2015-06-09 12:04 ` [RFC][PATCH 2/5] mm/mempool: allow NULL `pool' pointer in mempool_destroy() Sergey Senozhatsky
2015-06-17 23:21   ` David Rientjes
2015-06-17 23:54     ` Sergey Senozhatsky
2015-06-09 12:04 ` [RFC][PATCH 3/5] mm/dmapool: allow NULL `pool' pointer in dma_pool_destroy() Sergey Senozhatsky
2015-06-17 23:22   ` David Rientjes
2015-06-09 12:04 ` [RFC][PATCH 4/5] mm/zpool: allow NULL `zpool' pointer in zpool_destroy_pool() Sergey Senozhatsky
2015-06-10 20:59   ` Dan Streetman [this message]
2015-06-10 23:58     ` Sergey Senozhatsky
2015-06-11  0:48       ` Joe Perches
2015-06-11  0:59         ` Sergey Senozhatsky
2015-06-11  1:01           ` Dan Streetman
2015-06-09 12:04 ` [RFC][PATCH 5/5] mm/zsmalloc: allow NULL `pool' pointer in zs_destroy_pool() Sergey Senozhatsky
2015-06-09 21:25 ` [RFC][PATCH 0/5] do not dereference NULL pools in pools' destroy() functions Andrew Morton
2015-06-10  0:06   ` Joe Perches
2015-06-10  4:39     ` [PATCH] checkpatch: Add some <foo>_destroy functions to NEEDLESS_IF tests Joe Perches
2015-06-10  5:52       ` [PATCH V2] " Joe Perches
2015-06-10 10:18         ` Sergey Senozhatsky
2015-06-11  9:41         ` Julia Lawall
2015-06-11  9:51           ` Sergey Senozhatsky
2015-06-11  9:55             ` Julia Lawall
2015-07-14 23:03         ` Andrew Morton
2015-07-15  0:27           ` Sergey Senozhatsky
2015-06-10  5:46     ` [RFC][PATCH 0/5] do not dereference NULL pools in pools' destroy() functions Julia Lawall
2015-06-10  6:41       ` Sergey Senozhatsky
2015-06-10  6:44         ` Julia Lawall
2015-06-10  6:52           ` Sergey Senozhatsky
2015-06-10  1:11   ` Christoph Lameter
2015-06-10  1:51     ` Andrew Morton
2015-06-10  2:00       ` Christoph Lameter
2015-06-10  2:17         ` Andrew Morton
2015-06-10  4:47           ` Joe Perches
2015-06-11 17:26           ` Christoph Lameter
2015-06-11 17:40             ` Andrew Morton
2015-06-10  2:04     ` Sergey Senozhatsky

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='CALZtONAyQn1qGusF4TXcS1FHmiHNmJT+Wrh2G6j7OYA=R+Q0dQ@mail.gmail.com' \
    --to=ddstreet@ieee.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=minchan@kernel.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=sergey.senozhatsky@gmail.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 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).