From: Jarod Wilson <jwilson@redhat.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net,
"Kristian Høgsberg" <krh@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: fail open() quickly if the node doesn't exist anymore
Date: Mon, 28 Jan 2008 17:32:03 -0500 [thread overview]
Message-ID: <200801281732.03912.jwilson@redhat.com> (raw)
In-Reply-To: <tkrat.340b4530dff1f75a@s5r6.in-berlin.de>
On Sunday 27 January 2008 12:21:56 pm Stefan Richter wrote:
> Scenario: Process A keeps the character device file of node N open.
> N is being unplugged. File /dev/fwN won't be destroyed as long as A
> doesn't close it. Now, process B opens /dev/fwN as well. Previously
> it would succeed but be unable to do any IO on it of course. With this
> patch, process B's open() will fail immediately with -ENODEV.
>
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Makes perfect sense to me, no problems with it in cursory testing.
Signed-off-by: Jarod Wilson <jwilson@redhat.com>
--
Jarod Wilson
jwilson@redhat.com
next prev parent reply other threads:[~2008-01-28 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 0:05 [PATCH] firewire: fix "kobject_add failed for fw* with -EEXIST" Stefan Richter
2008-01-27 17:20 ` [PATCH update] " Stefan Richter
2008-01-27 17:21 ` [PATCH] firewire: fail open() quickly if the node doesn't exist anymore Stefan Richter
2008-01-28 22:32 ` Jarod Wilson [this message]
2008-01-28 23:50 ` Stefan Richter
2008-01-28 16:48 ` [PATCH update] firewire: fix "kobject_add failed for fw* with -EEXIST" Jarod Wilson
2008-01-28 18:54 ` Stefan Richter
2008-01-28 22:24 ` Jarod Wilson
2008-01-28 19:16 ` Stefan Richter
2008-01-28 23:31 ` Stefan Richter
2008-02-02 14:01 ` [PATCH update 2] " Stefan Richter
2008-01-28 22:30 ` [PATCH update] " Jarod Wilson
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=200801281732.03912.jwilson@redhat.com \
--to=jwilson@redhat.com \
--cc=krh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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.