linux-kernel - Re: acpi_os_allocate(GFP_KERNEL) (was Re: acpi_evaluate

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081218164801.GC16115@elf.ucw.cz>
Date:	Thu, 18 Dec 2008 17:48:01 +0100
From:	Pavel Machek <pavel@...e.cz>
To:	Len Brown <lenb@...nel.org>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-acpi@...r.kernel.org,
	Johannes Berg <johannes@...solutions.net>
Subject: Re: acpi_os_allocate(GFP_KERNEL) (was Re: acpi_evaluate_integer
	broken by design)

On Thu 2008-12-18 01:07:08, Len Brown wrote:
> 
> 
> -- Len Brown, Intel Open Source Technology Center
> 
> > In fact, we should be using GFP_ATOMIC already while devices are being
> > suspended, so we can switch from GFP_KERNEL to GFP_ATOMIC even before
> > interrupts are enabled.
> 
> true.  it makes me wonder if tinkering with ACPI
> is a bad idea -- for it will address only one user of kmalloc.

Other users should already know that they are called while suspending
device, and behave accordingly (use right flags to kmalloc, etc.)

If not, that's a bug...
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/