linux-kernel - Re: [PATCH] [104/223] KVM: Write protect memory after slot swap

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: <20101213094559.GD999@basil.fritz.box>
Date:	Mon, 13 Dec 2010 10:45:59 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Avi Kivity <avi@...hat.com>
Cc:	Andi Kleen <andi@...stfloor.org>, mst@...hat.com, gregkh@...e.de,
	ak@...ux.intel.com, linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: [PATCH] [104/223] KVM: Write protect memory after slot swap

> >Do you want to do the autotest explicitely for .35 too and no automatic
> >backports and do the same procedure as for newer kernels?
> >
> >I can do that, but you would need to do it for a long time.
> 
> Yes.  In fact it gets more important as time goes by, since as time
> goes by patches are more likely to cause regressions due to changes
> in the code base.

Ok. But this requires that you do this regularly for .35 too.
If you do that that's great. 

I will not automatically backport KVM patches anymore,
but wait/ping you instead.

-Andi
-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/