From: James Bottomley <James.Bottomley@suse.de>
To: linux-scsi <linux-scsi@vger.kernel.org>,
linux-ide <linux-ide@vger.kernel.org>
Subject: [PATCH 0/3] libata bug fixes and updates as a precursor for converting libsas to the new eh
Date: Sun, 23 Jan 2011 08:26:46 -0600 [thread overview]
Message-ID: <1295792806.3007.12.camel@mulgrave.site> (raw)
While I was playing around with converting libsas to the new error
handler, I ran into the two locking bugs and the fact that sas uses non
standard submission paths. These patches fix all of that. In theory,
the error handler locking bug is serious, since the eh_cmd_q list is
being processed on the wrong lock, but in practise, since libata has one
host per port, I don't think it will ever have any visible consequence
(until, of course, libsas comes along with multiple ports per host plus
non-libata ports).
James
---
James Bottomley (3):
libata: plumb sas port scan into standard libata paths
libata: fix locking for sas paths
libata: fix eh locking
drivers/ata/libata-core.c | 46 +++++++++++++++++++++-----------------------
drivers/ata/libata-eh.c | 9 ++++++-
drivers/ata/libata-scsi.c | 4 +-
drivers/ata/libata.h | 1 +
4 files changed, 32 insertions(+), 28 deletions(-)
next reply other threads:[~2011-01-23 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 14:26 James Bottomley [this message]
2011-01-23 14:28 ` [PATCH 1/3] libata: plumb sas port scan into standard libata paths James Bottomley
2011-01-23 14:30 ` [PATCH 2/3] libata: fix locking for sas paths James Bottomley
2011-01-23 14:31 ` [PATCH 3/3] libata: fix eh locking James Bottomley
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=1295792806.3007.12.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).