linux-kernel - revert: loop: queue_lock NULL pointer derefence in blk_throtl

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-next>] [day] [month] [year] [list]

Date:	Fri, 11 Feb 2011 14:59:41 +0200
From:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To:	Jens Axboe <jaxboe@...ionio.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: revert: loop: queue_lock NULL pointer derefence in blk_throtl_exit V1

Hello Jens, Andrew

We have accidentally commit "loop: queue_lock NULL pointer 
derefence in blk_throtl_exit V1" applied: ee71a968672a9951aee6014c55511007596425bc

It's not a huge problem, but I think, it's better to have V3 applied 
https://lkml.org/lkml/2011/1/21/158

since V3 targets all the throttle users, not only loop (by moving 
`fall-back' from loop_free to blk_release_queue).

V3 is in Andrew's mmotm as for now 
loop-queue_lock-null-pointer-derefence-in-blk_throtl_exit-v3.patch

Could we please revert ee71a968672a9951aee6014c55511007596425bc when 
loop-queue_lock-null-pointer-derefence-in-blk_throtl_exit-v3 will land 
in the kernel?

Sorry.

Thanks in advance,

        Sergey

Content of type "application/pgp-signature" skipped