From: Bodo Eggert <7eggert@elstempel.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
andi@lisas.de, Andrew Morton <akpm@osdl.org>,
gregkh@suse.de, linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, hal@lists.freedesktop.org
Subject: Re: [linux-usb-devel] USB/hal: USB open() broken? (USB CD burner underruns, USB HDD hard resets)
Date: Wed, 21 Jun 2006 02:07:56 +0200 [thread overview]
Message-ID: <E1FsqGX-0001eu-AT@be1.lrz> (raw)
In-Reply-To: 6pLll-5iq-15@gated-at.bofh.it
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Ar Maw, 2006-06-20 am 11:05 +0200, ysgrifennodd Andreas Mohr:
>> But how would HAL safely determine whether a (IDE/USB) drive is busy?
>> As my test app demonstrates (without HAL running), the *very first* open()
>> happening during an ongoing burning operation will kill it instantly, in the
>> USB case.
>> Are there any options left for HAL at all? Still seems to strongly point
>> towards a kernel issue so far.
>
> In the IDE space O_EXCL has the needed semantics. At least it does on
> Fedora and I don't think thats a Fedora patch, not sure if this is the
> case for the USB side of things.
This does not work, since O_EXCL does not work:
http://lkml.org/lkml/2006/2/5/137
Instead, I'd (try to) use mandatory locking and prevent open() etc. from
causing the bad commands to be sent.
--
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
http://david.woodhou.se/why-not-spf.html
next parent reply other threads:[~2006-06-21 0:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6pnj7-32Q-7@gated-at.bofh.it>
[not found] ` <6pJWg-34g-5@gated-at.bofh.it>
[not found] ` <6pKfL-3sx-29@gated-at.bofh.it>
[not found] ` <6pKpl-3Sx-23@gated-at.bofh.it>
[not found] ` <6pLll-5iq-15@gated-at.bofh.it>
2006-06-21 0:07 ` Bodo Eggert [this message]
2006-06-21 10:53 ` [linux-usb-devel] USB/hal: USB open() broken? (USB CD burner underruns, USB HDD hard resets) Alan Cox
2006-06-21 16:16 ` Bodo Eggert
2006-06-21 16:34 ` Andreas Mohr
2006-06-21 19:02 ` Alan Stern
2006-06-21 19:16 ` Andreas Mohr
2006-06-21 19:56 ` Alan Stern
2006-06-21 20:38 ` Bodo Eggert
2006-06-21 20:37 ` Alan Cox
2006-06-19 8:21 Andreas Mohr
2006-06-20 8:37 ` Andrew Morton
2006-06-20 9:06 ` [linux-usb-devel] " Alan Cox
2006-06-20 9:05 ` Andreas Mohr
2006-06-20 10:18 ` Alan Cox
2006-06-20 14:22 ` Alan Stern
2006-06-21 9:33 ` Andreas Mohr
2006-06-21 16:15 ` Alan Stern
2006-06-21 16:44 ` Andreas Mohr
2006-06-21 19:06 ` Alan Stern
2006-06-21 20:52 ` Alan Cox
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=E1FsqGX-0001eu-AT@be1.lrz \
--to=7eggert@elstempel.de \
--cc=7eggert@gmx.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@lisas.de \
--cc=gregkh@suse.de \
--cc=hal@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.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