linux-kernel - Re: [Bug 18252] spinlock lockup in __make_request <- submit_bio <- ondemand

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

Message-ID: <4C8F59EA.6020606@s5r6.in-berlin.de>
Date:	Tue, 14 Sep 2010 13:18:02 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Jens Axboe <axboe@...nel.dk>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Florian Mickler <florian@...kler.org>,
	linux-kernel@...r.kernel.org, bugzilla-daemon@...zilla.kernel.org,
	linux-scsi@...r.kernel.org
Subject: Re: [Bug 18252] spinlock lockup in __make_request <- submit_bio <-
  ondemand_readahead

Jens Axboe wrote:
> On 2010-09-14 08:56, Stefan Richter wrote:
>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=18252
>> Florian Mickler wrote:
>>> There was an scsi-related use-after-free OOPS fixed recently and pulled 3 days
>>> ago.  
...
>>> Maybe you are seeing that?
>>>
>>> (reacting to the general-protection-fault preceded by scsi_init in the
>>> attachment jpg)
>> Now that you point it out --- perhaps.  Though I haven't looked into the
>> mechanics of the now fixed scsi_ini_io use after free.
> 
> It seems the very likely explanation, since I can't see any other way that
> you would deadlock on the queue lock from that call trace if you haven't
> had someone else crash with the lock held already.

Good, I close the bugzilla item right away with the reasonable assuption that
it is fixed by commit 3a5c19c23db65a554f2e4f5df5f307c668277056.
-- 
Stefan Richter
-=====-==-=- =--= -===-
http://arcgraph.de/sr/
--
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/