From: Hannes Reinecke <hare@suse.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
James Bottomley <james.bottomley@hansenpartnership.com>,
Bart van Assche <bart.vanassche@sandisk.com>,
linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCHv6 0/5] scsi: Fixup blacklist handling
Date: Mon, 2 Oct 2017 16:26:32 +0200 [thread overview]
Message-ID: <1506954397-2237-1-git-send-email-hare@suse.de> (raw)
Hi all,
the SCSI blacklist handling seems to be rather tricky issue;
everytime a fix is included it tends to break other devices.
This patchset attempt to simplify the devlist handling yet again,
but this time implementing the framework for regression testing, too.
A patch adding a regression test to the blktest suite will follow.
As usual, comments and reviews are welcome.
Changes to v1:
- Implement exact match for vendor string as suggested by Bart
- Straigten out issues pointed out by Alan Stern
- Reshuffle patches
Changes to v2:
- Simplify code as indicated by Alan Stern
- Display blacklist flags verbatim
- Reformat blacklist flags definition for better readability
Changes to v3:
- Add reviews from Alan Stern
- Generate blacklist flag definitions
- Include reviews from Martin Petersen
Changes to v4:
- Add reviews from Bart
- Rework blacklist flag string generation
Changes to v5:
- Add bounds checking for sysfs attribute
- Add review from Doug Gilbert
Hannes Reinecke (5):
scsi_debug: allow to specify inquiry vendor and model
scsi: Export blacklist flags to sysfs
scsi_devinfo: Reformat blacklist flags
scsi_devinfo: Whitespace fixes
scsi_devinfo: fixup string compare
drivers/scsi/Makefile | 8 +++++
drivers/scsi/scsi_debug.c | 25 ++++++++++-----
drivers/scsi/scsi_devinfo.c | 67 ++++++++++++++++++++-------------------
drivers/scsi/scsi_scan.c | 1 +
drivers/scsi/scsi_sysfs.c | 37 ++++++++++++++++++++++
include/scsi/scsi_devinfo.h | 76 +++++++++++++++++++++++++++++----------------
6 files changed, 148 insertions(+), 66 deletions(-)
--
1.8.5.6
next reply other threads:[~2017-10-02 14:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 14:26 Hannes Reinecke [this message]
2017-10-02 14:26 ` [PATCHv6 1/5] scsi_debug: allow to specify inquiry vendor and model Hannes Reinecke
2017-10-13 10:08 ` Johannes Thumshirn
2017-10-02 14:26 ` [PATCHv6 2/5] scsi: Export blacklist flags to sysfs Hannes Reinecke
2017-10-02 16:35 ` Bart Van Assche
2017-10-13 10:08 ` Johannes Thumshirn
2017-10-25 1:48 ` [PATCHv6,2/5] " jeffy
2017-10-25 7:22 ` Hannes Reinecke
2017-10-25 7:40 ` jeffy
2017-10-02 14:26 ` [PATCHv6 3/5] scsi_devinfo: Reformat blacklist flags Hannes Reinecke
2017-10-13 10:08 ` Johannes Thumshirn
2017-10-02 14:26 ` [PATCHv6 4/5] scsi_devinfo: Whitespace fixes Hannes Reinecke
2017-10-13 10:09 ` Johannes Thumshirn
2017-10-02 14:26 ` [PATCHv6 5/5] scsi_devinfo: fixup string compare Hannes Reinecke
2017-10-13 10:09 ` Johannes Thumshirn
2017-10-13 10:06 ` [PATCHv6 0/5] scsi: Fixup blacklist handling Hannes Reinecke
2017-10-17 5:06 ` Martin K. Petersen
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=1506954397-2237-1-git-send-email-hare@suse.de \
--to=hare@suse.de \
--cc=bart.vanassche@sandisk.com \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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).