linux-kernel - Re: [PATCH 1/2] Disk hot removal causing oopses and fixes

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4ADF7AED.2030506@s5r6.in-berlin.de>
Date:	Wed, 21 Oct 2009 23:19:41 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Jarkko Lavinen <jarkko.lavinen@...ia.com>
CC:	Jens Axboe <axboe@...nel.dk>, linux-kernel@...r.kernel.org,
	linux-mmc@...r.kernel.org
Subject: Re: [PATCH 1/2] Disk hot removal causing oopses and fixes

Stefan Richter wrote:
> I dare say without knowing the MMC and block system:  It is not a
> locking issue, it is a reference counting issue.
[...]
> The whole secret is not to forget to count _all_ references.

PS, in case that it might be needed:  Sometimes a low level wants to
wait for the moment until its upper level users went away.  Reference
counting is then coupled with constructs like wait_for_completion then.
-- 
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/