[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <24bfb681-faec-3567-3089-9cd5ee182710@linaro.org>
Date: Mon, 25 Apr 2022 11:22:48 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: John Garry <john.garry@...wei.com>,
Christoph Hellwig <hch@...radead.org>
Cc: "Ewan D. Milne" <emilne@...hat.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Alim Akhtar <alim.akhtar@...sung.com>,
Avri Altman <avri.altman@....com>,
Doug Gilbert <dgilbert@...erlog.com>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
james.smart@...adcom.com
Subject: Re: [PATCH 1/4] scsi: core: constify pointer to scsi_host_template
On 25/04/2022 10:58, John Garry wrote:
> On 20/04/2022 08:03, Christoph Hellwig wrote:
>>> The standard flow is:
>>>
>>> shost = scsi_host_alloc(sht, )
>>>
>>> // modify shost, like
>>> shost->cmd_per_lun = 5;
>>>
>>> scsi_add_host(shost)
>>>
>>> Is there some reason for which those two drivers can't follow that?
>> I think they should. Method tables should not be mutable data.
>> .
>
> Hi Krzysztof,
>
> Do you have any interest in going further with your work and trying to
> change all SCSI driver instances of scsi_host_template to be const? I am
> not sure if it has been attempted before...
I can work on this, but what about the SCSI core modifying the template?
For example scsi_proc_hostdir_rm(): 'present' and 'proc_dir' members.
Where should they be stored? Should they be moved to the Scsi_Host?
Best regards,
Krzysztof
Powered by blists - more mailing lists