linux-kernel - Re: [REGRESSION] cdrom drive doesn't detect removal

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:	Thu, 16 Sep 2010 08:51:28 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Maxim Levitsky <maximlevitsky@...il.com>
Cc:	Henrique de Moraes Holschuh <hmh@....eng.br>,
	Tejun Heo <tj@...nel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Jens Axboe <axboe@...nel.dk>
Subject: Re: [REGRESSION] cdrom drive doesn't detect removal

On Thu, Sep 16, 2010 at 00:20, Maxim Levitsky <maximlevitsky@...il.com> wrote:
> So it makes the sense.
> It turns out that hal is still running on ubuntu systems, and yes, it
> still polls the drives, and yes I disabled that feature....
> So restoring that polling feature indeed fixes that problem for now.
> Yet, why without that commit detection did work?

Really, I have no idea how this can happen. You could only find out
with blocktrace, if something else is trying to open the device. The
state change in the drive should not be able to get known to the host
unless something is causing i/o with open().

Kay
--
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/