[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <284c3ecc-b3a8-eeec-92d5-5eda1f20f691@suse.de>
Date: Mon, 8 Jul 2019 08:01:08 +0200
From: Hannes Reinecke <hare@...e.de>
To: dgilbert@...erlog.com,
"Elliott, Robert (Servers)" <elliott@....com>,
Bart Van Assche <bvanassche@....org>,
Marc Gonzalez <marc.w.gonzalez@...e.fr>,
James Bottomley <jejb@...ux.ibm.com>,
Martin Petersen <martin.petersen@...cle.com>
Cc: SCSI <linux-scsi@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v1] scsi: Don't select SCSI_PROC_FS by default
On 7/5/19 7:53 PM, Douglas Gilbert wrote:
> On 2019-07-05 3:22 a.m., Hannes Reinecke wrote:
[ .. ]
>> As mentioned, rescan-scsi-bus.sh is keeping references to /proc/scsi as
>> a fall back only, as it's meant to work kernel independent. Per default
>> it'll be using /sys, and will happily work without /proc/scsi.
>>
>> So it's really only /proc/scsi/sg which carries some meaningful
>> information; maybe we should move/copy it to somewhere else.
>>
>> I personally like getting rid of /proc/scsi.
>
> /proc/scsi/device_info doesn't seem to be in sysfs.
>
> Could the contents of /proc/scsi/sg/* be placed in
> /sys/class/scsi_generic/* ? Currently that directory only has symlinks
> to the sg devices.
>
The sg parameters are already available in /sys/module/sg/parameters;
so from that perspective I feel we're good.
Problem is /proc/scsi/device_info, for which we currently don't have any
other location to store it at.
Hmm.
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@...e.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
Powered by blists - more mailing lists