From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-f178.google.com (mail-qc0-f178.google.com [209.85.216.178]) by kanga.kvack.org (Postfix) with ESMTP id A889D6B0035 for ; Tue, 22 Apr 2014 06:04:41 -0400 (EDT) Received: by mail-qc0-f178.google.com with SMTP id i8so5107958qcq.37 for ; Tue, 22 Apr 2014 03:04:41 -0700 (PDT) Received: from mx1.redhat.com (mx1.redhat.com. [209.132.183.28]) by mx.google.com with ESMTP id v10si16594602qat.93.2014.04.22.03.04.40 for ; Tue, 22 Apr 2014 03:04:41 -0700 (PDT) Message-ID: <535631EB.4060906@redhat.com> Date: Tue, 22 Apr 2014 11:10:03 +0200 From: Florian Weimer MIME-Version: 1.0 Subject: Re: [PATCH 0/6] File Sealing & memfd_create() References: <1395256011-2423-1-git-send-email-dh.herrmann@gmail.com> <5343F2EC.3050508@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: David Herrmann Cc: linux-kernel , Kay Sievers , Daniel Mack , Lennart Poettering , "dri-devel@lists.freedesktop.org" , linux-fsdevel , linux-mm On 04/09/2014 11:31 PM, David Herrmann wrote: > On Tue, Apr 8, 2014 at 3:00 PM, Florian Weimer wrote: >> How do you keep these promises on network and FUSE file systems? > > I don't. This is shmem only. Ah. What do you recommend for recipient to recognize such descriptors? Would they just try to seal them and reject them if this fails? -- Florian Weimer / Red Hat Product Security Team -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org