From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Martin K. Petersen" Subject: Re: [PATCH v1] scsi: Don't select SCSI_PROC_FS by default Date: Thu, 20 Jun 2019 17:47:01 -0400 Message-ID: References: <2de15293-b9be-4d41-bc67-a69417f27f7a@free.fr> <621306ee-7ab6-9cd2-e934-94b3d6d731fc@acm.org> <017cf3cf-ecd8-19c2-3bbd-7e7c28042c3c@free.fr> <48912bc0-8c79-408d-7ed2-c127b99b8bcc@interlog.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: (Marc Gonzalez's message of "Thu, 20 Jun 2019 11:01:39 +0200") Sender: linux-kernel-owner@vger.kernel.org To: Marc Gonzalez Cc: Douglas Gilbert , Finn Thain , Bart Van Assche , James Bottomley , Martin Petersen , SCSI , LKML , Christoph Hellwig List-Id: linux-scsi@vger.kernel.org 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