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:	Tue, 14 Sep 2010 09:39:05 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Maxim Levitsky <maximlevitsky@...il.com>
CC:	linux-kernel <linux-kernel@...r.kernel.org>,
	Jens Axboe <axboe@...nel.dk>,
	Kay Sievers <kay.sievers@...y.org>
Subject: Re: [REGRESSION] cdrom drive doesn't detect removal

Hello,

On 09/14/2010 03:27 AM, Maxim Levitsky wrote:
>> However 2.6.36 doesn't detect that removal.
>> According to udevadm monitor --property no uevents are send on removal.
> Correction, this is regression between 2.6.34 and 2.6.35. This shows how
> much I use cd these days...
> 
> I bisected it down to this:
> 
> 6b4517a7913a09d3259bb1d21c9cb300f12294bd is the first bad commit
> commit 6b4517a7913a09d3259bb1d21c9cb300f12294bd
> Author: Tejun Heo <tj@...nel.org>
> Date:   Wed Apr 7 18:53:59 2010 +0900
> 
>     block: implement bd_claiming and claiming block

Hmmm... weird.  This commit does change the open behavior but
shouldn't change the end result.  Can someone please enlighten me how
udevadm is interacting with the device at system call level?

Thanks.

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