From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f70.google.com (mail-wm0-f70.google.com [74.125.82.70]) by kanga.kvack.org (Postfix) with ESMTP id 5D41F6B026E for ; Wed, 25 May 2016 17:49:40 -0400 (EDT) Received: by mail-wm0-f70.google.com with SMTP id n2so35129510wma.0 for ; Wed, 25 May 2016 14:49:40 -0700 (PDT) Received: from ZenIV.linux.org.uk (zeniv.linux.org.uk. [2002:c35c:fd02::1]) by mx.google.com with ESMTPS id p10si13892462wjp.70.2016.05.25.14.49.39 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 May 2016 14:49:39 -0700 (PDT) Date: Wed, 25 May 2016 22:49:35 +0100 From: Al Viro Subject: Re: [PATCH v9] fs: clear file privilege bits when mmap writing Message-ID: <20160525214935.GI14480@ZenIV.linux.org.uk> References: <20160114212201.GA28910@www.outflux.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Kees Cook Cc: Andrew Morton , Konstantin Khlebnikov , Andy Lutomirski , Jan Kara , yalin wang , Willy Tarreau , "linux-mm@kvack.org" , Linux Kernel Mailing List On Wed, May 25, 2016 at 02:36:57PM -0700, Kees Cook wrote: > Hm, this didn't end up getting picked up. (This jumped out at me again > because i_mutex just vanished...) > > Al, what's the right way to update the locking in this patch? ->i_mutex is dealt with just by using lock_inode(inode)/unlock_inode(inode); I hadn't looked at the rest of the locking in there. -- 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