From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH for-4.6] x86/gdt: Drop write-only, xalloc()'d array from set_gdt() Date: Wed, 5 Aug 2015 10:58:20 +0100 Message-ID: <1438768700.9747.40.camel@citrix.com> References: <1438621543-21062-1-git-send-email-andrew.cooper3@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap , Andrew Cooper Cc: Wei Liu , Jan Beulich , Xen-devel List-Id: xen-devel@lists.xenproject.org On Tue, 2015-08-04 at 15:17 +0100, George Dunlap wrote: > On Mon, Aug 3, 2015 at 6:05 PM, Andrew Cooper > wrote: > > It is not used, and can cause a spurious failure of the set_gdt() > > hypercall in > > low memory situations. > > > > Signed-off-by: Andrew Cooper > > Reviewed-by: George Dunlap It's unclear from MAINTAINERS if this is formally enough for the patch to be applied but under the circumstances (pretty obvious patch, Reviewed-by more than one person, including the X86 MEMORY MANAGEMENT maintainer even if mm.c isn't strictly under that for some reason) I've added my own Revieed-by and applied, hopefully that is ok. Perhaps there should be a patch to MAINTAINERS to add arch/x86/mm.c to the relevant subsection? (Or maybe the file is just horribly named?) Ian.