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]
Message-ID: <ac3eb2510809301302l7d966896tfb0e3d230598974@mail.gmail.com>
Date:	Tue, 30 Sep 2008 22:02:53 +0200
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Frans Pop" <elendil@...net.nl>
Cc:	"Tony Vroon" <tony@...on.org>, linux-kernel@...r.kernel.org,
	"Tejun Heo" <tj@...nel.org>, "Jens Axboe" <jens.axboe@...cle.com>
Subject: Re: CD tray closes spontaneously after opening it

On Tue, Sep 30, 2008 at 9:50 PM, Frans Pop <elendil@...net.nl> wrote:
> On Tuesday 30 September 2008, Kay Sievers wrote:
>> Does:
>>   /sbin/udevadm monitor --env
>> print something while you see the tray closing?
>
> I was somewhat lucky to reproduce it with that running and there was no
> output during the open or close. I guess that rules out udev?

I think so, yes.

> I still don't know how to reliably reproduce this. It seems that after it
> has occurred once, it will not occur again unless the system is rebooted.
> But I'm not 100% sure of that.
>
> Most times I've seen it was after playing a DVD when ejecting the disc to
> put it back in its box, but not when the DVD was inserted earlier.
> But I've also seen it shortly after the system is booted when just opening
> the tray with no media inserted.
>
> Just to be clear: until recently the drive has always behaved perfectly in
> the same situations.
>
>> Does this also happen when you set:
>>   /proc/sys/dev/cdrom/autoclose
>> to 0?
>
> I'll set that on boot using /etc/sysctl.conf and will report if I can
> still reproduce with that setting. I've checked that the "normal" value
> is 1.

That will prevent the closing, when something tries to open the device
in blocking mode. If that solves the issue, you should start looking
which process tries to access your drive.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ