From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760325Ab3LIDOJ (ORCPT ); Sun, 8 Dec 2013 22:14:09 -0500 Received: from userp1040.oracle.com ([156.151.31.81]:23215 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760260Ab3LIDOG (ORCPT ); Sun, 8 Dec 2013 22:14:06 -0500 Message-ID: <52A5357A.8030506@oracle.com> Date: Sun, 08 Dec 2013 22:14:02 -0500 From: Sasha Levin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Al Viro CC: LKML Subject: Re: fs: proc: lockdep spew and questions References: <52A4DD51.6090709@oracle.com> <20131208221008.GO10323@ZenIV.linux.org.uk> In-Reply-To: <20131208221008.GO10323@ZenIV.linux.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Source-IP: acsinet21.oracle.com [141.146.126.237] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/08/2013 05:10 PM, Al Viro wrote: > On Sun, Dec 08, 2013 at 03:57:53PM -0500, Sasha Levin wrote: >> Hi all, >> >> I've been looking at permissions in procfs, and noticed that >> directories are usually added with execute permission. >> >> As far as I know, there's nothing executable by default inside >> procfs, and on top of that, many of the files there don't deal well >> with being executed so it's easy to cause lockdep spews (one below). >> >> Is there a reason execute bit is set for directories? > > Take any introductory textbook on Unix and read the chapter on permissions. > Or say chmod a-x ~, if you prefer education by self-LART... > Uh, forgot about that. So how would you suggest to deal with the execution issue in procfs? Thanks, Sasha