Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752553AbaDNADY (ORCPT ); Sun, 13 Apr 2014 20:03:24 -0400 Received: from mail-ie0-f176.google.com ([209.85.223.176]:44646 "EHLO mail-ie0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751094AbaDNADX (ORCPT ); Sun, 13 Apr 2014 20:03:23 -0400 MIME-Version: 1.0 In-Reply-To: References: <53470E26.2030306@cybernetics.com> <5347451C.4060106@amacapital.net> <5347F188.10408@cybernetics.com> <53486067.6090506@mit.edu> Date: Mon, 14 Apr 2014 02:03:22 +0200 Message-ID: Subject: Re: [PATCH 2/6] shm: add sealing API From: David Herrmann To: Andy Lutomirski Cc: Tony Battersby , linux-fsdevel , linux-mm , linux-kernel , "dri-devel@lists.freedesktop.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi On Sat, Apr 12, 2014 at 12:07 AM, Andy Lutomirski wrote: > I bet this is missing from lots of places. For example, I can't find > any write_access stuff in the rdma code. > > I suspect that the VM_DENYWRITE code is just generally racy. So what does S_IMMUTABLE do to prevent such races? I somehow suspect it's broken in that regard, too. I really dislike pinning pages like this, but if people want to keep it I guess I have to scan all shmem-inode pages before changing seals. 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/