From: Alexey Dobriyan <adobriyan@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jerome Marchand <jmarchan@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Miklos Szeredi <mszeredi@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] procfs: fix tid fdinfo
Date: Sat, 24 Apr 2010 22:27:35 +0300 [thread overview]
Message-ID: <20100424192735.GA5157@x200> (raw)
In-Reply-To: <20100423111620.100840fe.akpm@linux-foundation.org>
On Fri, Apr 23, 2010 at 11:16:20AM -0700, Andrew Morton wrote:
> On Fri, 23 Apr 2010 17:40:07 +0200
> > - DIR("fdinfo", S_IRUSR|S_IXUSR, proc_fdinfo_inode_operations, proc_fd_operations),
> > + DIR("fdinfo", S_IRUSR|S_IXUSR, proc_fdinfo_inode_operations, proc_fdinfo_operations),
> hm, the code's been like that for over a year. What are the
> user-visible effects of the bug, and of this change?
/proc/*/task/*/fdinfo contains symlinks to opened files like /proc/*/fd/
which is cool bug :-)
next prev parent reply other threads:[~2010-04-23 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 15:40 [PATCH] procfs: fix tid fdinfo Jerome Marchand
2010-04-23 18:16 ` Andrew Morton
2010-04-24 19:27 ` Alexey Dobriyan [this message]
2010-04-23 20:07 ` Miklos Szeredi
2010-04-26 7:49 ` Jerome Marchand
2010-04-26 10:26 ` Miklos Szeredi
2010-04-24 16:28 ` Alexey Dobriyan
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=20100424192735.GA5157@x200 \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jmarchan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=viro@zeniv.linux.org.uk \
/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.