From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH 0/4] flask: XSA-84 follow-ups Date: Fri, 7 Feb 2014 11:29:32 +0000 Message-ID: <52F4C39C.4090005@eu.citrix.com> References: <52F4B840020000780011A1E2@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBjcn-0005yH-9Q for xen-devel@lists.xenproject.org; Fri, 07 Feb 2014 11:29:37 +0000 In-Reply-To: <52F4B840020000780011A1E2@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , xen-devel Cc: dgdegra@tycho.nsa.gov List-Id: xen-devel@lists.xenproject.org On 02/07/2014 09:41 AM, Jan Beulich wrote: > 1: fix memory leaks > 2: fix error propagation from flask_security_set_bool() > 3: check permissions first thing in flask_security_set_bool() > 4: add compat mode guest support > > Signed-off-by: Jan Beulich > > Release-wise, I would think that 1-3 should certainly go in. While I'd > like 4 to be in for 4.4 too, I realize that's a little more intrusive than > one would want at this point. I agree on 1-3: Release-acked-by: George Dunlap Re #4: This is something we can pull in for 4.4.1, right? If nobody has noticed it missing, it's not exactly a burning feature. If it's possible to wait for 4.4.1 I'd rather do so. -George