Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753128AbaDVMzn (ORCPT ); Tue, 22 Apr 2014 08:55:43 -0400 Received: from mail-ig0-f174.google.com ([209.85.213.174]:53310 "EHLO mail-ig0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750716AbaDVMzi (ORCPT ); Tue, 22 Apr 2014 08:55:38 -0400 MIME-Version: 1.0 In-Reply-To: <53566428.9080005@redhat.com> References: <1395256011-2423-1-git-send-email-dh.herrmann@gmail.com> <5343F2EC.3050508@redhat.com> <535631EB.4060906@redhat.com> <53566428.9080005@redhat.com> Date: Tue, 22 Apr 2014 14:55:37 +0200 Message-ID: Subject: Re: [PATCH 0/6] File Sealing & memfd_create() From: David Herrmann To: Florian Weimer Cc: linux-kernel , Kay Sievers , Daniel Mack , Lennart Poettering , "dri-devel@lists.freedesktop.org" , linux-fsdevel , linux-mm Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi On Tue, Apr 22, 2014 at 2:44 PM, Florian Weimer wrote: > I didn't find that very convincing. But in v2, seals are monotonic, so > checking them should be reliable enough. Ok. > What happens when you create a loop device on a write-sealed descriptor? Any write-back to the loop-device will fail with EPERM as soon as the fd gets write-sealed. See __do_lo_send_write() in drivers/block/loop.c. It's up to the loop-device to forward the error via bio_endio() to the caller for proper error-handling. Thanks David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/