linux-kernel - Re: [PATCHSET wq/for-6.9,6.10] workqueue: Implement disable/enable

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: <CAOMdWSJ4WVXV+-c_dXOWmSxXadb4a-qgpBe+fLPNsZtW0-uayQ@mail.gmail.com>
Date: Mon, 26 Feb 2024 09:30:14 -0800
From: Allen <allen.lkml@...il.com>
To: Kees Cook <keescook@...omium.org>
Cc: Tejun Heo <tj@...nel.org>, Lai Jiangshan <jiangshanlai@...il.com>, torvalds@...ux-foundation.org, 
	linux-kernel@...r.kernel.org, kernel-team@...a.com
Subject: Re: [PATCHSET wq/for-6.9,6.10] workqueue: Implement disable/enable_work()

> > > > For 0001-00010:
> > > >
> > > > Reviewed-by: Lai Jiangshan <jiangshanlai@...il.com>
> > >
> > > Applied 0001-0010 to wq/for-6.9.
> > >
> > > Thanks.
> >
> > I have rebased the conversion work based on
> >
> >  git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git disable_work-v1
> >
> > 0001-dma-Convert-from-tasklet-to-BH-workqueue.patch
> > 0002-IB-Convert-from-tasklet-to-BH-workqueue.patch
> > 0003-USB-Convert-from-tasklet-to-BH-workqueue.patch
> > 0004-mailbox-Convert-from-tasklet-to-BH-workqueue.patch
> > 0005-ipmi-Convert-from-tasklet-to-BH-workqueue.patch
> > 0006-s390-Convert-from-tasklet-to-BH-workqueue.patch
> > 0007-drivers-media-Convert-from-tasklet-to-BH-workqueue.patch
> > 0008-mmc-Convert-from-tasklet-to-BH-workqueue.patch
> >
> > Patches: https://github.com/allenpais/for-6.9-bh-conversions
> > KSPP Issue: refactor all tasklet users into other APIs · Issue #94 ·
> > https://github.com/KSPP/linux/issues/94
> >

Kees,

> > I am working on drivers/crypto/* and drivers/net/*. This might a
> > day or two more. Please provide guidance on the types of testing I
> > should perform.
>
> Great! What's the plan for these? Will they go to subsystem maintainers
> after the next merge window, or is Tejun carrying them?
>

  I think it's best to send it out the subsystem mailing list. Ideally, get some
testing/benchmarks run and then look at getting them into either Tejun's
branch or via subsystem maintainers. I am open to other ideas.

Thanks.

> -Kees
>
> --
> Kees Cook



-- 
       - Allen