From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>
Cc: Douglas Gilbert <dgilbert@interlog.com>,
Finn Thain <fthain@telegraphics.com.au>,
Bart Van Assche <bvanassche@acm.org>,
James Bottomley <jejb@linux.ibm.com>,
Martin Petersen <martin.petersen@oracle.com>,
SCSI <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v1] scsi: Don't select SCSI_PROC_FS by default
Date: Thu, 20 Jun 2019 17:47:01 -0400 [thread overview]
Message-ID: <yq1muicq696.fsf@oracle.com> (raw)
In-Reply-To: <e04e14b7-e1ee-c0c1-9e6d-2628d2c873a9@free.fr> (Marc Gonzalez's message of "Thu, 20 Jun 2019 11:01:39 +0200")
Marc,
> (I work on smaller systems where we do use /proc occasionally, but we
> don't enable CHR_DEV_SG or SCSI_PROC_FS.)
Many sg apps depend on SCSI_PROC_FS. That doesn't imply that only sg
apps depend on it.
As an example, with SCSI_PROC_FS enabled we don't need your SanDisk
Cruzer Blade patch at all since you can tweak the blacklist flags from
user space.
Also, the "legacy" moniker was wishful thinking. Applied to the Kconfig
option at a time where sysfs was new and shiny and considered the
solution to all the kernel's problems. But that wholesale transition of
all interfaces from /proc simply never took place. What happened was
that *new* functionality largely went to sysfs.
Note that I don't have a problem adding missing knobs to sysfs where it
makes sense. But it will obviously take a while for userland apps to
adopt it.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-06-20 21:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 13:59 [PATCH v1] scsi: Don't select SCSI_PROC_FS by default Marc Gonzalez
2019-06-17 21:11 ` Bart Van Assche
2019-06-18 0:35 ` Douglas Gilbert
2019-06-18 1:08 ` Finn Thain
2019-06-18 7:29 ` Marc Gonzalez
2019-06-18 15:31 ` Douglas Gilbert
2019-06-19 9:42 ` Marc Gonzalez
2019-06-19 14:34 ` Douglas Gilbert
2019-06-20 9:01 ` Marc Gonzalez
2019-06-20 21:47 ` Martin K. Petersen [this message]
2019-06-20 23:43 ` Finn Thain
2019-06-21 10:41 ` Marc Gonzalez
2019-06-21 23:50 ` Finn Thain
2019-06-18 3:28 ` Bart Van Assche
2019-06-18 17:43 ` Elliott, Robert (Servers)
2019-07-05 7:22 ` Hannes Reinecke
2019-07-05 17:53 ` Douglas Gilbert
2019-07-08 6:01 ` Hannes Reinecke
2019-07-08 13:02 ` Douglas Gilbert
2019-07-05 7:18 ` 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=yq1muicq696.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bvanassche@acm.org \
--cc=dgilbert@interlog.com \
--cc=fthain@telegraphics.com.au \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
/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