From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com [209.85.223.173]) by kanga.kvack.org (Postfix) with ESMTP id 750B76B00C6 for ; Sun, 13 Apr 2014 20:03:24 -0400 (EDT) Received: by mail-ie0-f173.google.com with SMTP id rl12so7547665iec.4 for ; Sun, 13 Apr 2014 17:03:24 -0700 (PDT) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [2607:f8b0:4001:c03::236]) by mx.google.com with ESMTPS id x3si10435933igl.28.2014.04.13.17.03.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Apr 2014 17:03:23 -0700 (PDT) Received: by mail-ie0-f182.google.com with SMTP id y20so7538242ier.13 for ; Sun, 13 Apr 2014 17:03:22 -0700 (PDT) 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 Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-linux-mm@kvack.org List-ID: To: Andy Lutomirski Cc: Tony Battersby , linux-fsdevel , linux-mm , linux-kernel , "dri-devel@lists.freedesktop.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, 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