From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
ebiederm@xmission.com, linux-fsdevel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: /proc/pid/fd/ shows strange mode when executed via sudo.
Date: Fri, 18 May 2012 19:45:26 +0100 [thread overview]
Message-ID: <20120518184526.GS22082@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFzuW0qmozQsZ4CYzXJeUQS_X+_=AevB9qFYRY=NEw96vQ@mail.gmail.com>
On Fri, May 18, 2012 at 11:23:27AM -0700, Linus Torvalds wrote:
> On Fri, May 18, 2012 at 11:18 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > Doing it at getattr() time does sound good.
> >
> > Let me try to cook something up.
>
> Ugh. It's a much bigger patch, because we share the inode operations
> with other cases too.
>
> So I think that would fall under the "further cleanup" heading, and
> I'm not going to do it now. Not with 3.4 imminent.
>
> But if you were to do such a cleanup later...
It's actually not big. Completely untested minimal variant (without
touching ->d_revalidate()):
diff --git a/fs/proc/base.c b/fs/proc/base.c
index 1c8b280..b2a8b8f 100644
--- a/fs/proc/base.c
+++ b/fs/proc/base.c
@@ -1491,6 +1491,44 @@ static const struct inode_operations proc_pid_link_inode_operations = {
.setattr = proc_setattr,
};
+static int proc_fd_getattr(struct vfsmount *mnt, struct dentry *dentry, struct kstat *stat)
+{
+ struct inode *inode = dentry->d_inode;
+ struct files_struct *files;
+ struct task_struct *task;
+ struct file *file;
+ fmode_t mode = 0;
+
+ generic_fillattr(inode, stat);
+
+ rcu_read_lock();
+ task = pid_task(proc_pid(inode), PIDTYPE_PID);
+ files = task ? get_files_struct(task) : NULL;
+ file = files ? fcheck_files(files, PROC_I(inode)->fd) : NULL;
+ if (file)
+ mode = file->f_mode;
+ rcu_read_unlock();
+
+ if (files)
+ put_files_struct(files);
+ if (!file)
+ return -ENOENT;
+
+ if (mode & FMODE_READ)
+ stat->mode |= S_IRUSR | S_IXUSR;
+ if (mode & FMODE_WRITE)
+ stat->mode |= S_IWUSR | S_IXUSR;
+ stat->size = 64;
+ return 0;
+}
+
+static const struct inode_operations proc_pid_fd_inode_operations = {
+ .readlink = proc_pid_readlink,
+ .follow_link = proc_pid_follow_link,
+ .setattr = proc_setattr,
+ .getattr = proc_fd_getattr,
+};
+
/* building an inode */
@@ -1851,25 +1889,16 @@ static struct dentry *proc_fd_instantiate(struct inode *dir,
files = get_files_struct(task);
if (!files)
goto out_iput;
- inode->i_mode = S_IFLNK;
- /*
- * We are not taking a ref to the file structure, so we must
- * hold ->file_lock.
- */
- spin_lock(&files->file_lock);
+ rcu_read_lock();
file = fcheck_files(files, fd);
- if (!file)
- goto out_unlock;
- if (file->f_mode & FMODE_READ)
- inode->i_mode |= S_IRUSR | S_IXUSR;
- if (file->f_mode & FMODE_WRITE)
- inode->i_mode |= S_IWUSR | S_IXUSR;
- spin_unlock(&files->file_lock);
+ rcu_read_unlock();
put_files_struct(files);
+ if (!file)
+ goto out_iput;
- inode->i_op = &proc_pid_link_inode_operations;
- inode->i_size = 64;
+ inode->i_mode = S_IFLNK;
+ inode->i_op = &proc_pid_fd_inode_operations;
ei->op.proc_get_link = proc_fd_link;
d_set_d_op(dentry, &tid_fd_dentry_operations);
d_add(dentry, inode);
@@ -1879,9 +1908,6 @@ static struct dentry *proc_fd_instantiate(struct inode *dir,
out:
return error;
-out_unlock:
- spin_unlock(&files->file_lock);
- put_files_struct(files);
out_iput:
iput(inode);
goto out;
next prev parent reply other threads:[~2012-05-18 18:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 13:40 /proc/pid/fd/ shows strange mode when executed via sudo Tetsuo Handa
2012-05-03 15:42 ` Serge Hallyn
2012-05-03 16:25 ` Tetsuo Handa
2012-05-18 2:39 ` Tetsuo Handa
2012-05-18 9:27 ` Tetsuo Handa
2012-05-18 16:08 ` Linus Torvalds
2012-05-18 16:25 ` Linus Torvalds
2012-05-18 19:55 ` Eric W. Biederman
2012-05-18 18:08 ` Al Viro
2012-05-18 18:18 ` Linus Torvalds
2012-05-18 18:23 ` Linus Torvalds
2012-05-18 18:45 ` Al Viro [this message]
2012-05-18 18:55 ` Linus Torvalds
2012-05-18 19:10 ` Al Viro
2012-05-18 20:49 ` Linus Torvalds
2012-05-18 21:23 ` Al Viro
2012-05-18 21:26 ` Linus Torvalds
2012-05-18 21:32 ` Linus Torvalds
2012-05-18 22:29 ` Al Viro
2012-05-19 7:08 ` Tetsuo Handa
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=20120518184526.GS22082@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.