linux-kernel - Re: [PATCH 5 of 5] xen: Avoid allocations causing swap activity on the resume path

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: <4840B0C5.4020606@pobox.com>
Date:	Fri, 30 May 2008 21:58:29 -0400
From:	Jeff Garzik <jgarzik@...ox.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	Jens Axboe <jens.axboe@...cle.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 5 of 5] xen: Avoid allocations causing swap activity on
 the	resume path

Jeremy Fitzhardinge wrote:
> From: Ian Campbell <ian.campbell@...rix.com>
> 
> Avoid allocations causing swap activity on the resume path by allowing
> such allocations to access the emergency pools otherwise a
> save/restore/migration of a guest which is low on memory can
> deadlock.
> 
> [ linux-2.6.18-xen changesets e8b49cfbdac, fdb998e79aba ]
> 
> Signed-off-by: Ian Campbell <ian.campbell@...rix.com>
> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
> 
> ---
>  drivers/block/xen-blkfront.c       |    5 +++--
>  drivers/net/xen-netfront.c         |    4 ++--
>  drivers/xen/xenbus/xenbus_client.c |    2 +-
>  drivers/xen/xenbus/xenbus_xs.c     |   10 +++++-----
>  4 files changed, 11 insertions(+), 10 deletions(-)

IMO I am not qualified enough to ACK or NAK this VM-related patch...  If 
others are happy with it, go ahead and merge the xen-netfront.c with 
that batch.




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