From: "Mike Frysinger" <vapier.adi@gmail.com>
To: Matt Helsley <matthltc@us.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@tv-sign.ru>,
David Howells <dhowells@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Christoph Hellwig <chellwig@de.ibm.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Hugh Dickins <hugh@veritas.com>, Bryan Wu <Bryan.Wu@analog.com>
Subject: Re: [PATCH] procfs task exe symlink
Date: Sat, 16 Feb 2008 07:12:01 -0500 [thread overview]
Message-ID: <8bd0f97a0802160412ve49103cya446b89d8560458b@mail.gmail.com> (raw)
In-Reply-To: <1202348669.9062.271.camel@localhost.localdomain>
On Feb 6, 2008 8:44 PM, Matt Helsley <matthltc@us.ibm.com> wrote:
> The kernel implements readlink of /proc/pid/exe by getting the file from the
> first executable VMA. Then the path to the file is reconstructed and reported as
> the result.
>
> Because of the VMA walk the code is slightly different on nommu systems. This
> patch avoids separate /proc/pid/exe code on nommu systems. 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.
>
> That reference would prevent the filesystem holding the executable file from
> being unmounted even after unmapping the VMAs. So we track the number of
> VM_EXECUTABLE VMAs and drop the new reference when the last one is unmapped.
> This avoids pinning the mounted filesystem.
>
> Andrew, these are the updates I promised. Please consider this patch for
> inclusion in -mm.
mm/nommu.c wasnt compiled tested, it's trivially broken:
> --- linux-2.6.24.orig/mm/nommu.c
> +++ linux-2.6.24/mm/nommu.c
> @@ -960,12 +960,15 @@ unsigned long do_mmap_pgoff(struct file
> if (!vma)
> goto error_getting_vma;
>
> INIT_LIST_HEAD(&vma->anon_vma_node);
> atomic_set(&vma->vm_usage, 1);
> - if (file)
> + if (file) {
> get_file(file);
> + if (vm_flags & VM_EXECUTABLE)
> + added_exe_file_vma(mm);
> + }
> vma->vm_file = file;
> vma->vm_flags = vm_flags;
> vma->vm_start = addr;
> vma->vm_end = addr + len;
> vma->vm_pgoff = pgoff;
this function has no variable named "mm"
mm/nommu.c: In function 'do_mmap_pgoff':
mm/nommu.c:968: error: 'mm' undeclared (first use in this function)
mm/nommu.c:968: error: (Each undeclared identifier is reported only once
mm/nommu.c:968: error: for each function it appears in.)
make[1]: *** [mm/nommu.o] Error 1
-mike
--
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-02-16 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 1:44 [PATCH] procfs task exe symlink Matt Helsley
2008-02-16 12:12 ` Mike Frysinger [this message]
2008-02-19 21:54 ` Matt Helsley
2008-02-20 4:02 ` Mike Frysinger
2008-04-26 16:19 ` Andrew Morton
2008-04-26 16:24 ` Al Viro
2008-04-30 11:02 ` 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=8bd0f97a0802160412ve49103cya446b89d8560458b@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=Bryan.Wu@analog.com \
--cc=akpm@linux-foundation.org \
--cc=chellwig@de.ibm.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthltc@us.ibm.com \
--cc=oleg@tv-sign.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).