From: Bart Van Assche <bvanassche@acm.org>
To: dgilbert@interlog.com, John Garry <john.garry@huawei.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Christoph Hellwig <hch@infradead.org>
Cc: "Ewan D. Milne" <emilne@redhat.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
james.smart@broadcom.com
Subject: Re: [PATCH 1/4] scsi: core: constify pointer to scsi_host_template
Date: Mon, 25 Apr 2022 21:13:33 -0700 [thread overview]
Message-ID: <f6516c7f-16c7-689c-b6cd-ebff95e931a4@acm.org> (raw)
In-Reply-To: <5485f529-e99a-0bdd-07bd-b5b559da91e6@interlog.com>
On 4/25/22 18:54, Douglas Gilbert wrote:
> On 2022-04-25 21:16, Bart Van Assche wrote:
>> How about removing scsi_proc_hostdir_add(), scsi_proc_hostdir_rm() and
>> all other code that creates files or directories under /proc/scsi?
>> There should be corresponding entries in sysfs for all /proc/scsi
>> entries. Some tools in sg3_utils use that directory so sg3_utils will
>> have to be updated.
>
> ... breaking this:
>
> ~$ cat /proc/scsi/scsi
>
> Attached devices:
>
> Host: scsi3 Channel: 00 Id: 00 Lun: 00
>
> Vendor: IBM-207x Model: HUSMM8020ASS20 Rev: J4B6
>
> Type: Direct-Access ANSI SCSI revision: 06
>
> Host: scsi3 Channel: 00 Id: 01 Lun: 00
>
> Vendor: IBM-207x Model: HUSMM8020ASS20 Rev: J4B6
>
> Type: Direct-Access ANSI SCSI revision: 06
>
> Host: scsi3 Channel: 00 Id: 02 Lun: 00
>
> Vendor: SEAGATE Model: ST200FM0073 Rev: 0007
>
> Type: Direct-Access ANSI SCSI revision: 06
> ...
>
> A deprecation notice would be helpful, then removal after a few kernel
> cycles.
Agreed with the deprecation notice + delayed removal, but is anyone
using cat /proc/scsi/scsi?
> Yes, lsscsi can give that output:
>
> $ lsscsi -c
>
> Attached devices:
>
> Host: scsi2 Channel: 00 Target: 00 Lun: 00
>
> Vendor: SEAGATE Model: ST200FM0073 Rev: 0007
>
> Type: Direct-Access ANSI SCSI revision: 06
>
> Host: scsi2 Channel: 00 Target: 01 Lun: 00
>
> Vendor: WDC Model: WSH722020AL5204 Rev: C421
>
> Type: Zoned Block ANSI SCSI revision: 07
>
> Host: scsi2 Channel: 00 Target: 02 Lun: 00
>
> Vendor: Areca Te Model: ARC-802801.37.69 Rev: 0137
>
> Type: Enclosure ANSI SCSI revision: 05
> ...
>
> [Hmmm, in a different order.]
>
> However no distribution that I'm aware of includes lsscsi in its
> installation.
> [Most recent example: Ubuntu 22.04]
Hmm ... are you sure? Last time I looked into this an lsscsi package was
available for every distro I tried (RHEL, SLES, Debian and openSUSE).
See also
https://packages.debian.org/search?searchon=contents&keywords=lsscsi&mode=path&suite=stable&arch=any.
Are there other utilities in sg3_utils that would break if the
/proc/scsi directory would be removed?
$ cd sg3_utils && git grep /proc/scsi | wc -l
51
Thanks,
Bart.
next prev parent reply other threads:[~2022-04-26 4:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 10:30 Krzysztof Kozlowski
2022-04-08 10:30 ` [PATCH 2/4] scsi: core: fix white-spaces Krzysztof Kozlowski
2022-05-04 8:47 ` Krzysztof Kozlowski
2022-04-08 10:30 ` [PATCH 3/4] scsi: ufs: ufshcd-pltfrm: constify pointed data Krzysztof Kozlowski
2022-04-08 10:30 ` [PATCH 4/4] scsi: ufs: ufshcd: " Krzysztof Kozlowski
2022-04-08 14:35 ` Bart Van Assche
2022-04-08 12:14 ` [PATCH 1/4] scsi: core: constify pointer to scsi_host_template John Garry
2022-04-08 12:32 ` Krzysztof Kozlowski
2022-04-08 12:57 ` John Garry
2022-04-08 19:31 ` Ewan D. Milne
2022-04-12 7:57 ` John Garry
2022-04-20 7:03 ` Christoph Hellwig
2022-04-25 8:58 ` John Garry
2022-04-25 9:22 ` Krzysztof Kozlowski
2022-04-25 13:04 ` John Garry
2022-04-26 1:16 ` Bart Van Assche
2022-04-26 1:54 ` Douglas Gilbert
2022-04-26 4:13 ` Bart Van Assche [this message]
2022-04-27 1:47 ` Douglas Gilbert
2022-05-06 16:42 ` Krzysztof Kozlowski
2022-05-09 11:28 ` John Garry
2022-05-09 13:20 ` Krzysztof Kozlowski
2022-05-09 14:50 ` John Garry
2022-05-11 8:31 ` Christoph Hellwig
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=f6516c7f-16c7-689c-b6cd-ebff95e931a4@acm.org \
--to=bvanassche@acm.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=dgilbert@interlog.com \
--cc=emilne@redhat.com \
--cc=hch@infradead.org \
--cc=james.smart@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®