linux-kernel - Re: [PATCH V2] ACPI/Processor: Rework processor throttling with work_on

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] [day] [month] [year] [list]

Message-ID: <1578601.f4RF6O7QVQ@vostro.rjw.lan>
Date:	Thu, 27 Feb 2014 00:49:24 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Lan Tianyu <tianyu.lan@...el.com>
Cc:	tj@...nel.org, jolsa@...hat.com, oleg@...hat.com, lenb@...nel.org,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2] ACPI/Processor: Rework processor throttling with work_on_cpu()

On Wednesday, February 26, 2014 09:46:29 PM Lan Tianyu wrote:
> On 02/26/2014 09:30 PM, Rafael J. Wysocki wrote:
> > On Wednesday, February 26, 2014 09:03:05 PM Lan Tianyu wrote:
> >> acpi_processor_set_throttling() uses set_cpus_allowed_ptr() to make
> >> sure struct acpi_processor->acpi_processor_set_throttling() callback
> >> run on associated cpu. But the function maybe called in a worker which
> >> has been bound to a cpu. The patch is to replace set_cpus_allowed_ptr()
> >> with work_on_cpu().
> >>
> >> Signed-off-by: Lan Tianyu <tianyu.lan@...el.com>
> >
> > OK
> >
> > I suppose we need this in -stable?
> 
> Yes.
> 
> >
> > Which series of -stable should it go to?  All of them or just recent?
> 
> I think it should be all of them.

OK, queued up as a fix for 3.14, thanks!

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/