From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH 1/2] tmem: add full support for x86 up to 16Tb Date: Wed, 25 Sep 2013 16:44:38 -0400 Message-ID: <20130925204438.GA9039@phenom.dumpdata.com> References: <1379903015-15955-1-git-send-email-bob.liu@oracle.com> <5240384202000078000F57F2@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VOvx2-0000LR-15 for xen-devel@lists.xenproject.org; Wed, 25 Sep 2013 20:44:48 +0000 Content-Disposition: inline In-Reply-To: <5240384202000078000F57F2@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 Cc: xen-devel , Bob Liu , Bob Liu , keir@xen.org, ian.campbell@citrix.com List-Id: xen-devel@lists.xenproject.org > All that said - I'm not sure we want to accept enhancements to > tmem without the security audit happening first, which has been > due for over a year now. I had looked at the tmem code with a peper and pencil to see if there are no issues. So far none - I still have the deduplication to finish. Also I had been looking at Coverity to help me in that and it has spotted two issues where we did not look at the return value. I plan to post patches for that once I am done with my vacation email-backlog.