All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Tejun Heo <tj@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>
Subject: Re: [REGRESSION] cdrom drive doesn't detect removal
Date: Wed, 15 Sep 2010 03:01:35 +0200	[thread overview]
Message-ID: <AANLkTikF37hN7dFqPbCp-gcim7SarveaTrjXipnGpJM7@mail.gmail.com> (raw)
In-Reply-To: <1284511071.3551.1.camel@maxim-laptop>

On Wed, Sep 15, 2010 at 02:37, Maxim Levitsky <maximlevitsky@gmail.com> wrote:
> On Wed, 2010-09-15 at 01:49 +0200, Kay Sievers wrote:
>> On Wed, Sep 15, 2010 at 01:38, Maxim Levitsky <maximlevitsky@gmail.com> wrote:
>> > On Tue, 2010-09-14 at 10:07 +0200, Kay Sievers wrote:
>>
>> >> Are we sure, that there is something that still polls the drive?
>> >> Udisks is only auto-started, when the desktop calls into some D-Bus
>> >> methods, unlike HAL where it was an init script.
>> >
>> > Note that on current vanilla head, I applied the attached manual revert
>> > patch, and problem disappears (and probably introduces the same bug that
>> > patch supposed to fix).
>>
>> Can you please check which process polls the device, and attach an
>> strace to it, to see what's going on?
> As far as I can tell there is no such process.
> (at least sudo fuser /dev/sr0 doesn't show up anything with or without
> cd in the drive)
>>
>> If there is no such process, does "touch /dev/sr0" create the missing event?
> Yes.

Hmm, strange, I really have no idea why the old kernel works
differently for you.

The behavior you describe for the current kernel seems correct and is
the expected one. If there is nothing in userspace that polls
periodically, than we can't expect any event for a media change.

It's only the polling that should be able to trigger these events for
the device. the device itself can't report any changes to the host,
unless you have a SATA drive which can send AN (async notification)
events. But we disabled the AN support recently, because it was
running in loops on some boxes.

Kay

  reply	other threads:[~2010-09-15  1:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-12  9:49 [REGRESSION] cdrom drive doesn't detect removal Maxim Levitsky
2010-09-14  1:27 ` Maxim Levitsky
2010-09-14  7:39   ` Tejun Heo
2010-09-14  8:07     ` Kay Sievers
2010-09-14 23:38       ` Maxim Levitsky
2010-09-14 23:49         ` Kay Sievers
2010-09-15  0:37           ` Maxim Levitsky
2010-09-15  1:01             ` Kay Sievers [this message]
2010-09-15 13:27               ` Henrique de Moraes Holschuh
2010-09-15 13:44                 ` Kay Sievers
2010-09-15 22:20                   ` Maxim Levitsky
2010-09-16  6:51                     ` Kay Sievers
2010-09-21 11:42                       ` Maxim Levitsky
2010-09-21 23:09                         ` Maxim Levitsky
2010-09-22  7:38                           ` Tejun Heo
2010-09-22 13:41                             ` Maxim Levitsky
2010-09-22 13:58                               ` Maxim Levitsky
2010-09-23  8:47                                 ` Tejun Heo
2010-09-23  9:21                                   ` Kay Sievers
2010-09-30  6:30                                     ` Florian Mickler
2010-09-30  7:48                                       ` Kay Sievers
2010-09-30 11:38                                         ` Florian Mickler
2010-09-30 14:17                                           ` Maxim Levitsky
2010-09-30 14:49                                             ` Florian Mickler
2010-09-30 19:27                                               ` Kay Sievers
2010-09-30 20:14                                                 ` Florian Mickler
2010-09-30 20:32                                                   ` Kay Sievers
2010-09-30 20:47                                                     ` Florian Mickler
2010-09-30 20:57                                                       ` Kay Sievers
2010-10-01  5:55                                               ` Tejun Heo
2010-10-01  7:54                                                 ` Florian Mickler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikF37hN7dFqPbCp-gcim7SarveaTrjXipnGpJM7@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.