Re: [PATCH -next] gfs2: use kmem_cache_free() instead of kfree()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Wei Yongjun <weiyongjun1@xxxxxxxxxx>
Subject: Re: [PATCH -next] gfs2: use kmem_cache_free() instead of kfree()
From: Andreas Grünbacher <andreas.gruenbacher@xxxxxxxxx>
Date: Fri, 9 Apr 2021 10:34:34 +0200
Cc: Bob Peterson <rpeterso@xxxxxxxxxx>, Andreas Gruenbacher <agruenba@xxxxxxxxxx>, cluster-devel <cluster-devel@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, kernel-janitors@xxxxxxxxxxxxxxx, Hulk Robot <hulkci@xxxxxxxxxx>
In-reply-to: <20210409082957.2909213-1-weiyongjun1@huawei.com>
References: <20210409082957.2909213-1-weiyongjun1@huawei.com>

Hi,

Am Fr., 9. Apr. 2021 um 10:20 Uhr schrieb Wei Yongjun <weiyongjun1@xxxxxxxxxx>:
> memory allocated by kmem_cache_alloc() should be freed using
> kmem_cache_free(), not kfree().

thanks for the patch, that's true. This patch has turned out to have
other problems as well, so we've pulled it and Bob is currently
investigating.

Andreas

References:
- [PATCH -next] gfs2: use kmem_cache_free() instead of kfree()
  - From: Wei Yongjun

Prev by Date: [PATCH -next] gfs2: use kmem_cache_free() instead of kfree()
Next by Date: Re: [PATCH] clk: uniphier: Fix potential infinite loop
Previous by thread: [PATCH -next] gfs2: use kmem_cache_free() instead of kfree()
Next by thread: [PATCH][V2] clk: uniphier: Fix potential infinite loop
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Development] [Kernel Announce] [Kernel Newbies] [Linux Networking Development] [Share Photos] [IDE] [Security] [Git] [Netfilter] [Yosemite News] [MIPS Linux] [ARM Linux] [Device Mapper]

Powered by Linux