From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: mmotm 2009-06-30-12-50 uploaded
Date: Tue, 30 Jun 2009 13:39:13 -0700 [thread overview]
Message-ID: <4A4A77F1.4010405@oracle.com> (raw)
In-Reply-To: <20090630133550.bf34a0ba.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Tue, 30 Jun 2009 13:19:48 -0700
> Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
>> Valdis.Kletnieks@vt.edu wrote:
>
> (I wasn't cc'ed?)
mm-commits but not you... (from Valdis)
>>> On Tue, 30 Jun 2009 12:51:30 PDT, akpm@linux-foundation.org said:
>>>> The mm-of-the-moment snapshot 2009-06-30-12-50 has been uploaded to
>>> This dies with quilt 0.44, thusly:
>>>
>>> Applying patch procfs-provide-stack-information-for-threads-v08.patch
>>> can't find file to patch at input line 20
>>> Perhaps you used the wrong -p or --strip option?
>>> The text leading up to this was:
>>> --------------------------
>>> |From: Stefani Seibold <stefani@seibold.net>
>>> |
>>> |A patch to give a better overview of the userland application stack usage,
>>> |especially for embedded linux.
>>> |
>>> |Currently you are only able to dump the main process/thread stack usage
>>> |which is showed in /proc/pid/status by the "VmStk" Value. But you get no
>>> |information about the consumed stack memory of the the threads.
>>> |
>>> |There is an enhancement in the /proc/<pid>/{task/*,}/*maps and which marks
>>> |the vm mapping where the thread stack pointer reside with "[thread stack
>>> |xxxxxxxx]". xxxxxxxx is the maximum size of stack. This is a value
>>> |information, because libpthread doesn't set the start of the stack to the
>>> |top of the mapped area, depending of the pthread usage.
>>> |
>>> |A sample output of /proc/<pid>/task/<tid>/maps looks like:
>>> |
>>> |08048000-08049000 r-xp 00000000 03:00 8312 /opt/z
>>> |08049000-0804a000 rw-p 00001000 03:00 8312 /opt/z
>
> The next line is:
>
> a7d12000-a7d13000 ---p 00000000 00:00 0
>
> And I bet stupid patch(1) saw that "---" and decided that it was the
> start of a diff.
>
> Try adding `-u' to the patch(1) command?
>
> I use something like
>
> patch -u -f -p1 --fuzz=1 -s
Yes, my .quiltrc file contains -u for QUILT_PATCH_OPTS.
--
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/
next prev parent reply other threads:[~2009-06-30 20:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 19:51 mmotm 2009-06-30-12-50 uploaded akpm
2009-06-30 20:15 ` Valdis.Kletnieks
2009-06-30 20:19 ` Randy Dunlap
2009-06-30 20:35 ` Andrew Morton
2009-06-30 20:39 ` Randy Dunlap [this message]
2009-06-30 20:27 ` Valdis.Kletnieks
2009-06-30 20:38 ` Andrew Morton
2009-07-01 9:21 ` KOSAKI Motohiro
2009-07-02 13:51 ` Valdis.Kletnieks
2009-06-30 21:49 ` [PATCH mmotm] hwmon: fix lis3-spi for CONFIG_PM=n Randy Dunlap
2009-07-02 19:16 ` mmotm 2009-06-30-12-50 uploaded Valdis.Kletnieks
2009-07-02 19:47 ` Andrew Morton
2009-07-02 20:21 ` Valdis.Kletnieks
2009-07-03 10:25 ` Valdis.Kletnieks
2009-07-03 1:52 ` mmotm 2009-06-30-12-50 dies during early boot Valdis.Kletnieks
2009-07-03 2:20 ` Andrew Morton
2009-07-03 8:20 ` Oleg Nesterov
2009-07-03 9:23 ` [PATCH] selinux_bprm_committed_creds: use __wake_up_parent() Oleg Nesterov
2009-07-03 9:39 ` James Morris
2009-07-03 10:12 ` Valdis.Kletnieks
2009-07-03 10:46 ` Oleg Nesterov
2009-07-03 10:16 ` David Howells
2009-07-03 16:11 ` Andrew Morton
2009-07-04 8:14 ` Oleg Nesterov
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=4A4A77F1.4010405@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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