From: Stefani Seibold <stefani@seibold.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] procfs: provide stack information for threads
Date: Sat, 03 Oct 2009 09:40:26 +0200 [thread overview]
Message-ID: <1254555626.24924.2.camel@wall-e> (raw)
In-Reply-To: <m263axq8ie.fsf@whitebox.home>
Sorry, i missed this. Good job ;-)
Stefani
Am Samstag, den 03.10.2009, 08:47 +0200 schrieb Andreas Schwab:
> Here's the patch again properly signed.
>
> Andreas.
>
> >From 9da252fd7d9a5cf84a477a35a6b52f927c85b280 Mon Sep 17 00:00:00 2001
> From: Andreas Schwab <schwab@linux-m68k.org>
> Date: Sat, 3 Oct 2009 08:19:43 +0200
> Subject: [PATCH] compat_do_execve: set current->stack_start as in do_execve
>
> Signed-off-by: Andreas Schwab <schwab@linux-m68k.org>
> ---
> fs/compat.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/fs/compat.c b/fs/compat.c
> index d576b55..6c19040 100644
> --- a/fs/compat.c
> +++ b/fs/compat.c
> @@ -1532,6 +1532,8 @@ int compat_do_execve(char * filename,
> if (retval < 0)
> goto out;
>
> + current->stack_start = current->mm->start_stack;
> +
> /* execve succeeded */
> current->fs->in_exec = 0;
> current->in_execve = 0;
> --
> 1.6.4.4
>
>
--
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:[~2009-10-03 7:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 14:58 Detailed Stack Information Patch [1/3] Stefani Seibold
2009-04-01 19:31 ` Ingo Molnar
2009-04-02 21:26 ` Stefani Seibold
2009-06-03 20:34 ` Detailed Stack Information Patch Next Generation Stefani Seibold
2009-06-03 21:06 ` Andrew Morton
2009-06-04 11:23 ` [patch] procfs: provide stack information for threads Stefani Seibold
2009-06-04 11:37 ` Andrew Morton
2009-06-04 11:56 ` Stefani Seibold
2009-06-04 17:57 ` Andrew Morton
2009-06-04 20:21 ` Stefani Seibold
2009-06-04 21:23 ` Andrew Morton
2009-06-05 19:12 ` Stefani Seibold
2009-06-05 19:19 ` Andrew Morton
2009-10-02 21:17 ` Andreas Schwab
2009-10-02 21:44 ` Andreas Schwab
2009-10-03 6:47 ` Andreas Schwab
2009-10-03 7:40 ` Stefani Seibold [this message]
2009-10-03 11:33 ` Stefani Seibold
2009-06-06 10:01 ` [patch] procfs: provide stack information for threads V0.6 Stefani Seibold
2009-06-09 10:35 ` [patch] proc.txt: Update kernel filesystem/proc.txt documentation Stefani Seibold
2009-06-09 19:36 ` Andrew Morton
2009-06-09 20:53 ` Stefani Seibold
2009-06-09 21:13 ` Andrew Morton
2009-06-10 6:46 ` [patch 1/2] " Stefani Seibold
2009-06-10 6:46 ` [patch 2/2] procfs: provide stack information for threads V0.7 Stefani Seibold
2009-06-10 7:20 ` [patch 2/2] procfs: provide stack information for threads V0.8 Stefani Seibold
2009-06-15 22:01 ` Andrew Morton
2009-06-16 7:14 ` Stefani Seibold
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=1254555626.24924.2.camel@wall-e \
--to=stefani@seibold.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=schwab@linux-m68k.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 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).