linux-kernel - Re: [PATCH] block: initialize the bounce pool if high memory may be added later

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: <4EA074CD.9000903@kernel.dk>
Date:	Thu, 20 Oct 2011 21:21:49 +0200
From:	Jens Axboe <axboe@...nel.dk>
To:	David Vrabel <david.vrabel@...rix.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] block: initialize the bounce pool if high memory may
 be added later

On 2011-10-20 17:27, David Vrabel wrote:
> On 11/10/11 12:53, David Vrabel wrote:
>> init_emergency_pool() does not create the page pool for bouncing block
>> requests if the current count of high pages is zero.  If high memory
>> may be added later (either via memory hotplug or a balloon driver in a
>> virtualized system) then a oops occurs if a request with a high page
>> need bouncing because the pool does not exist.
>>
>> So, always create the pool if memory hotplug is enabled and change the
>> test so it's valid even if all high pages are currently in the balloon
>> (the balloon drivers adjust totalhigh_pages but not max_pfn).
> 
> Jens, you don't seem to have picked up this patch yet.  Should it have
> gone via Andrew Morton instead?

Added now for 3.2.

-- 
Jens Axboe

--
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/