From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>,
Bart van Assche <bart.vanassche@sandisk.com>,
James Bottomley <james.bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Doug Gilbert <dgilbert@interlog.com>,
Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCHv2 2/4] scsi: Export blacklist flags to sysfs
Date: Thu, 10 Aug 2017 20:43:33 -0400 [thread overview]
Message-ID: <yq1valv0w96.fsf@oracle.com> (raw)
In-Reply-To: <1502275444-27676-3-git-send-email-hare@suse.de> (Hannes Reinecke's message of "Wed, 9 Aug 2017 12:44:02 +0200")
Hannes,
> Each scsi device is scanned according to the found blacklist flags,
> but this information is never presented to sysfs. This makes it quite
> hard to figure out if blacklisting worked as expected. With this
> patch we're exporting an additional attribute 'blacklist' containing
> the blacklist flags for this device.
There have been changes to the blacklist values over the years so I'm
not so keen on exporting them as a numbers.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-08-11 0:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 10:44 [PATCHv2 0/4] Fixup blacklist handling Hannes Reinecke
2017-08-09 10:44 ` [PATCHv2 1/4] scsi_debug: allow to specify inquiry vendor and model Hannes Reinecke
2017-08-11 0:44 ` Martin K. Petersen
2017-08-09 10:44 ` [PATCHv2 2/4] scsi: Export blacklist flags to sysfs Hannes Reinecke
2017-08-11 0:43 ` Martin K. Petersen [this message]
2017-08-11 6:46 ` Hannes Reinecke
2017-08-09 10:44 ` [PATCHv2 3/4] scsi: whitespace fixes in scsi_devinfo.c Hannes Reinecke
2017-08-09 10:44 ` [PATCHv2 4/4] scsi_devinfo: fixup string compare Hannes Reinecke
2017-08-09 17:43 ` Alan Stern
2017-08-10 6:34 ` Hannes Reinecke
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=yq1valv0w96.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bart.vanassche@sandisk.com \
--cc=dgilbert@interlog.com \
--cc=hare@suse.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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).