linux-kernel - RE: [RFC PATCH 2/2] ACPI: Default disable auto-serialization.

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: <1AE640813FDE7649BE1B193DEA596E88024E1BA1@SHSMSX101.ccr.corp.intel.com>
Date:	Tue, 18 Mar 2014 01:29:55 +0000
From:	"Zheng, Lv" <lv.zheng@...el.com>
To:	"Rafael J. Wysocki" <rjw@...ysocki.net>
CC:	"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
	"Brown, Len" <len.brown@...el.com>, Lv Zheng <zetalog@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Subject: RE: [RFC PATCH 2/2] ACPI: Default disable auto-serialization.

Hi,

> From: linux-acpi-owner@...r.kernel.org [mailto:linux-acpi-owner@...r.kernel.org] On Behalf Of Rafael J. Wysocki
> Sent: Tuesday, March 18, 2014 9:13 AM
> 
> On Tuesday, March 18, 2014 12:31:54 AM Zheng, Lv wrote:
> > Hi, Rafael
> >
> > > From: Wysocki, Rafael J
> > > Sent: Monday, March 17, 2014 8:09 PM
> > >
> > > On 3/17/2014 5:14 AM, Lv Zheng wrote:
> > > > This feature enabled by the following commit is still under development.
> > > >
> > > >    Commit: cd52379678785b02d7a357988cfba214fdaf92f4
> > > >    Subject: ACPICA: Add global option to disable method auto-serialization.
> > > >    This change adds an option to disable the auto-serialization of
> > > >    methods that create named objects.
> > > >
> > > > This patch disables it by default temporarily according to the bug reports.
> > >
> > > Well, it doesn't restore the 3.14 behavior of acpi_auto_serialize, as
> > > far as I can say, so we can't apply it.
> > >
> > > I still can drop the commits related to auto-serialization from my
> > > acpica branch.  Which commits are they?
> >
> > From linux-pm/bleeding-edge branch, I found this series includes the following commits:
> >
> > Commit: a0fd108f2da56b769472fc0095616fb370988516
> > Author: Lv Zheng <lv.zheng@...el.com>
> > Subject: ACPI: Rename kernel parameter "acpi_serialize" to "acpi_no_auto_serialize"
> >
> > Commit: 5f1cb4a92e4c4aabd139ff9ca1e11c0e2db2ac59
> > Author: Lv Zheng <lv.zheng@...el.com>
> > Subject: ACPICA: Remove global option to serialize all control methods.
> >
> > Commit: cd52379678785b02d7a357988cfba214fdaf92f4
> > Author: Bob Moore <robert.moore@...el.com>
> > Subject: ACPICA: Add global option to disable method auto-serialization.
> >
> > Commit: f56b05bd111b01141ef74568dc4d262c70295d03
> > Author: Lv Zheng <lv.zheng@...el.com>
> > Subject: ACPICA: Add additional named objects for the auto-serialize method scan.
> >
> > Commit: 27f1899350a1d6baab117c03c87f0e37730047bd
> > Author: Bob Moore <robert.moore@...el.com>
> > Subject: ACPICA: Add auto-serialization support for ill-behaved control methods.
> >
> > Reverting these commits can restore original Linux behavior.
> > Please check.
> 
> OK, I dropped the five commits above from the acpica branch.
> 
> Please check if the current ACPICA material in the bleeding-edge branch of
> linux-pm.git looks OK (and let me know either way).

It took me some time to confirm.
I just checked ACPICA code using the ACPICA divergence script.
And checked the Linux side reversal in osl.c/kernel-parameter.txt.
All seem to be OK.

Best regards
-Lv

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