linux-kernel - Re: [PATCH RESEND 01/13] scsi: ncr53c8xx: Use default @max_active for hostdata->work

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZGwPt4VNs1RhWpvn@slm.duckdns.org>
Date:   Mon, 22 May 2023 14:58:31 -1000
From:   Tejun Heo <tj@...nel.org>
To:     "Martin K. Petersen" <martin.petersen@...cle.com>
Cc:     jiangshanlai@...il.com, linux-kernel@...r.kernel.org,
        kernel-team@...a.com, Finn Thain <fthain@...ux-m68k.org>,
        Michael Schmitz <schmitzmic@...il.com>,
        "James E.J. Bottomley" <jejb@...ux.ibm.com>,
        linux-scsi@...r.kernel.org
Subject: Re: [PATCH RESEND 01/13] scsi: ncr53c8xx: Use default @max_active
 for hostdata->work_q

On Mon, May 22, 2023 at 06:06:56PM -0400, Martin K. Petersen wrote:
> 
> Hi Tejun!
> 
> > Subject: scsi: ncr53c8xx: Use default @max_active for hostdata->work_q
> >
> > hostdata->work_q only hosts a single work item, hostdata->main_task, and
> > thus doesn't need explicit concurrency limit. Let's use the default
> > @max_active. This doesn't cost anything and clearly expresses that
> > @max_active doesn't matter.
> 
> > It's not a must but it'd be great if I can route this through the workqueue
> > tree so that it can go together with other related and followup cleanups.
> 
> As Finn pointed out, please make sure it's tagged NCR5380: instead of
> ncr53c8xx:. Otherwise OK.
> 
> Acked-by: Martin K. Petersen <martin.petersen@...cle.com>

Will update and apply to wq/for-6.5-cleanup-ordered.

Thank you.

-- 
tejun