mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] firewire: cope with temporary connection loss
Date: Sat, 17 Jan 2009 22:45:54 +0100 (CET)	[thread overview]
Message-ID: <tkrat.ca8b7763ca31e24d@s5r6.in-berlin.de> (raw)

In the following series, the 1st patch enables the firewire stack to
tolerate brief disappearance of nodes similarly as the ieee1394 stack
has been taught in Linux 2.6.28.

This finally allows me to push the patch
    Date: Wed, 19 Mar 2008 22:02:40 +0100 (CET)
    From: Stefan Richter <stefanr@s5r6.in-berlin.de>
    Subject: firewire: insist on successive self ID complete events
into the mainline, which is a fix that potentially prevents kernel
panics.  This fix had the unfortunate side effect that the firewire-core
topology code destroyed and re-created node representations more often
than before.  Until now, this caused high-level drivers (firewire-sbp2
and userspace drivers) to be unbound and rebound, so that for example
mounted filesystems were lost.

Besides the condition which triggered the "insist on successive self ID
complete events" precautions, there are also other occasions at which
nodes vanish briefly and reappear.  See the changelog of patch 1/4.
firewire-core is now able to keep drivers bound until the nodes come
back, if they come back quickly.

The latter 3 patches are cleanups.

[PATCH 1/4] firewire: keep highlevel drivers attached during brief connection loss
[PATCH 2/4] firewire: core: clean up includes
[PATCH 3/4] firewire: core: move some functions
[PATCH 4/4] firewire: core: remove condition which is always false

 drivers/firewire/fw-device.c |  231 +++++++++++++++++++++++------------
 drivers/firewire/fw-device.h |   14 +-
 2 files changed, 166 insertions(+), 79 deletions(-)
-- 
Stefan Richter
-=====-==--= ---= =---=
http://arcgraph.de/sr/


             reply	other threads:[~2009-01-17 21:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17 21:45 Stefan Richter [this message]
2009-01-17 21:46 ` [PATCH 1/4] firewire: keep highlevel drivers attached during brief " Stefan Richter
2009-01-17 21:46 ` [PATCH 2/4] firewire: core: clean up includes Stefan Richter
2009-01-17 21:47 ` [PATCH 3/4] firewire: core: move some functions Stefan Richter
2009-01-17 21:47 ` [PATCH 4/4] firewire: core: remove condition which is always false Stefan Richter
2009-01-24 19:35 ` [PATCH 5/4] firewire: core: optimize card shutdown Stefan Richter

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=tkrat.ca8b7763ca31e24d@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-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

all inboxes | Powered by JetHome®