linux-kernel - Re: [PATCH 04/50] ACPICA: Fix to allow region arguments to reference other scopes

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: <20120301152754.GA3167@burratino>
Date:	Thu, 1 Mar 2012 09:27:55 -0600
From:	Jonathan Nieder <jrnieder@...il.com>
To:	Len Brown <lenb@...nel.org>
Cc:	linux-acpi@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org,
	Jim Green <student.northwestern@...il.com>,
	Lin Ming <ming.m.lin@...el.com>,
	Bob Moore <robert.moore@...el.com>,
	Len Brown <len.brown@...el.com>,
	Arne Nordmark <nordmark@...h.kth.se>
Subject: Re: [PATCH 04/50] ACPICA: Fix to allow region arguments to reference
 other scopes

Hi,

Len Brown wrote[1]:

> From: Lin Ming <ming.m.lin@...el.com>
[...]
> http://www.acpica.org/bugzilla/show_bug.cgi?id=937
> http://marc.info/?l=linux-acpi&m=131636632718222&w=2
>
> ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND (20110112/psargs-359)
> ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20110112/nsinit-349)
>
>     Scope (_SB)
>     {
>         Name (RAMB, 0xDF5A1018)
>         OperationRegion (\RAMW, SystemMemory, RAMB, 0x00010000)
>     }
>
> For above ASL code, we need to save scope node(\_SB) to lookup
> the argument node(\_SB.RAMB).
>
> Reported-by: Jim Green <student.northwestern@...il.com>
> Signed-off-by: Lin Ming <ming.m.lin@...el.com>
> Signed-off-by: Bob Moore <robert.moore@...el.com>
> Signed-off-by: Len Brown <len.brown@...el.com>

Arne Nordmark reports[2] that this patch, when applied to 3.2.5, fixes
a resume failure.  Thanks!

Would it be safe and useful to backport this fix to stable/longterm
kernels?  If so, which ones?

Jonathan

[1] commit 8931d9ea7884
[2] http://bugs.debian.org/661581
--
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/