From: David Zeuthen <david@fubar.dk>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: HAL list <hal@freedesktop.org>,
kde-devel@mail.kde.org, linux-kernel@vger.kernel.org
Subject: Re: USB Media card - works at boot-up, removal works, re-insert doesn't
Date: Thu, 23 Sep 2004 21:31:40 +0200 [thread overview]
Message-ID: <1095967901.4573.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20040921214842.GJ1105@lkcl.net>
Hi,
On Tue, 2004-09-21 at 22:48 +0100, Luke Kenneth Casson Leighton wrote:
> > To me, it seems like a severe kernel bug if a userspace process,
> > *especially* if it's unprivileged, can keep the kernel from emitting
> > hotplug remove events when a device is physically detached. It would be
> > interesting to create a minimal program to reproduce this.
>
> that's quite straightforward: i guess that an appx 30 character perl program
> or a 3 line python program 'd do the job.
>
> or just using opendir() in c, here y'go...
>
I can indeed reproduce this.
> [of course, changing it to "umount -lf" _also_ solves the
> problem by making konqueror break: result, after the first remove,
> you have to manually close konqueror, insert the media, remove
> the media card (again), reinsert it (again), re-run konqueror]
>
Even using 'umount -lf' doesn't work for me; I'm using the Fedora
Rawhide 2.6.8-1.584 kernel which is pretty close to 2.6.9-rc2-bk5. So
there we have it: unprivileged user can delay hotplug events for as long
as he likes. Yikes!
Thanks,
David
prev parent reply other threads:[~2004-09-23 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040921180217.GE1105@lkcl.net>
[not found] ` <1095792743.5501.29.camel@localhost.localdomain>
[not found] ` <20040921202911.GH1105@lkcl.net>
[not found] ` <1095800905.4970.8.camel@localhost.localdomain>
2004-09-21 21:48 ` USB Media card - works at boot-up, removal works, re-insert doesn't Luke Kenneth Casson Leighton
2004-09-22 0:37 ` Luke Kenneth Casson Leighton
2004-09-23 19:31 ` David Zeuthen [this message]
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=1095967901.4573.5.camel@localhost.localdomain \
--to=david@fubar.dk \
--cc=hal@freedesktop.org \
--cc=kde-devel@mail.kde.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcl@lkcl.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox