From: David Howells <dhowells@redhat.com>
To: Matt Helsley <matthltc@us.ibm.com>
Cc: dhowells@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Al Viro <viro@ftp.linux.org.uk>,
William H Taber <wtaber@us.ibm.com>,
William Cesar de Oliveira <owilliam@br.ibm.com>,
Richard Kissel <rkissel@us.ibm.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] Fix procfs task exe symlink
Date: Wed, 23 Jan 2008 20:46:31 +0000 [thread overview]
Message-ID: <22275.1201121191@redhat.com> (raw)
In-Reply-To: <1201112977.5443.29.camel@localhost.localdomain>
Matt Helsley <matthltc@us.ibm.com> wrote:
> To solve the problem this patch changes the way that the kernel resolves a
> task's exe symlink. Instead of walking the VMAs to find the first
> executable file-backed VMA we store a reference to the exec'd file in the
> mm_struct -- /foo/bar/jvm/bin/java in the example above.
Sounds interesting.
> nommu-only code paths are untested -- lacking access to nommu system
I could test it, but it'll have to wait until I get back from LCA in a couple
of weeks time.
David
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: Matt Helsley <matthltc@us.ibm.com>
Cc: dhowells@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Al Viro <viro@ftp.linux.org.uk>,
William H Taber <wtaber@us.ibm.com>,
William Cesar de Oliveira <owilliam@br.ibm.com>,
Richard Kissel <rkissel@us.ibm.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] Fix procfs task exe symlink
Date: Wed, 23 Jan 2008 20:46:31 +0000 [thread overview]
Message-ID: <22275.1201121191@redhat.com> (raw)
In-Reply-To: <1201112977.5443.29.camel@localhost.localdomain>
Matt Helsley <matthltc@us.ibm.com> wrote:
> To solve the problem this patch changes the way that the kernel resolves a
> task's exe symlink. Instead of walking the VMAs to find the first
> executable file-backed VMA we store a reference to the exec'd file in the
> mm_struct -- /foo/bar/jvm/bin/java in the example above.
Sounds interesting.
> nommu-only code paths are untested -- lacking access to nommu system
I could test it, but it'll have to wait until I get back from LCA in a couple
of weeks time.
David
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-01-23 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 18:29 [PATCH] Fix procfs task exe symlink Matt Helsley
2008-01-23 18:29 ` Matt Helsley
2008-01-23 19:01 ` Jan Engelhardt
2008-01-23 19:01 ` Jan Engelhardt
2008-01-25 0:09 ` Erez Zadok
2008-01-25 0:09 ` Erez Zadok
2008-01-23 19:41 ` Christoph Hellwig
2008-01-23 19:41 ` Christoph Hellwig
2008-01-23 20:46 ` David Howells [this message]
2008-01-23 20:46 ` David Howells
2008-01-27 6:03 ` Andrew Morton
2008-01-27 6:03 ` Andrew Morton
2008-01-29 0:18 ` Matt Helsley
2008-01-29 0:18 ` Matt Helsley
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=22275.1201121191@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthltc@us.ibm.com \
--cc=owilliam@br.ibm.com \
--cc=rkissel@us.ibm.com \
--cc=viro@ftp.linux.org.uk \
--cc=wtaber@us.ibm.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 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.