linux-kernel - Re: [GIT PULL] workqueue fixes for v4.5-rc3

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: <CA+55aFyVneVzC33Lr_ca0GNYEw5gDy1PgEY+Mj35dTcrj-Ue2g@mail.gmail.com>
Date:	Thu, 11 Feb 2016 10:26:35 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Tejun Heo <tj@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] workqueue fixes for v4.5-rc3

On Thu, Feb 11, 2016 at 12:18 AM, Thomas Gleixner <tglx@...utronix.de> wrote:
>
> That certainly makes sense. So we should use a common debug option to force
> the 'schedule remote' machinery for all interesting subsystems instead of
> creating an extra option for each.

Yeah, let's make it easy to use and enable.

If it was split, the options would likely interact anyway (ie any
option that enables "add_timer()" to run on arbitrary cpu's wouldl
automatically also affect "queue_delayed_work()"), so it's not like it
would really be truly independent issues anyway.

And if it does show an oops or other problem due to some broken
expectations, I'd hope the oops should be enough to show what the
problem is. It did for the vmstat case.

                    Linus