From: Al Viro <viro@ZenIV.linux.org.uk>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: fs: proc: lockdep spew and questions
Date: Sun, 8 Dec 2013 22:10:08 +0000 [thread overview]
Message-ID: <20131208221008.GO10323@ZenIV.linux.org.uk> (raw)
In-Reply-To: <52A4DD51.6090709@oracle.com>
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...
next prev parent reply other threads:[~2013-12-08 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 20:57 fs: proc: lockdep spew and questions Sasha Levin
2013-12-08 22:10 ` Al Viro [this message]
2013-12-09 3:14 ` Sasha Levin
2013-12-09 11:46 ` Christian Kujau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131208221008.GO10323@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox