Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755501AbaDKWID (ORCPT ); Fri, 11 Apr 2014 18:08:03 -0400 Received: from mail-qg0-f50.google.com ([209.85.192.50]:45246 "EHLO mail-qg0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755404AbaDKWH6 (ORCPT ); Fri, 11 Apr 2014 18:07:58 -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> From: Andy Lutomirski Date: Fri, 11 Apr 2014 15:07:38 -0700 Message-ID: Subject: Re: [PATCH 2/6] shm: add sealing API To: David Herrmann 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 On Fri, Apr 11, 2014 at 2:42 PM, David Herrmann wrote: > Hi > > On Fri, Apr 11, 2014 at 11:36 PM, Andy Lutomirski wrote: >> A quick grep of the kernel tree finds exactly zero code paths >> incrementing i_mmap_writable outside of mmap and fork. >> >> Or do you mean a different kind of write ref? What am I missing here? > > Sorry, I meant i_writecount. 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. --Andy -- 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/