linux-kernel - Re: [PATCH] LIB: remove unmatched write_lock() in gen_pool

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 15 Jun 2009 17:30:32 -0500
From:	Steve Wise <swise@...ngridcomputing.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Jiri Kosina <trivial@...nel.org>, zygo.blaxell@...dros.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] LIB: remove unmatched write_lock() in gen_pool_destroy

Andrew Morton wrote:
> On Mon, 15 Jun 2009 23:35:31 +0200 (CEST)
> Jiri Kosina <trivial@...nel.org> wrote:
>
>   
>>> -	write_lock(&pool->lock);
>>>  	list_for_each_safe(_chunk, _next_chunk, &pool->chunks) {
>>>  		chunk = list_entry(_chunk, struct gen_pool_chunk, next_chunk);
>>>  		list_del(&chunk->next_chunk);
>>> -- 
>>> 1.5.6.5
>>>
>>>       
>> Hi Zygo,
>>
>> this doesn't really qualify for trivial tree, as it introduces a 
>> significant code change. Adding some CCs.
>>     
>
> yep, I merged it, thanks.
>
> I wonder why drivers/infiniband/hw/cxgb3 users never noticed this.
>   

I seem to remember trying to get this removed a few years ago and the 
owner didn't want it removed...


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/