From: "Charles 'Mack' Rhinelander" <mrhinelander@gmail.com>
To: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: BUG: mmotm-2009-0625-1549 quilt fails at procfs-provide-stack-information-for-threads-v08.patch
Date: Sat, 27 Jun 2009 09:26:50 -0700 [thread overview]
Message-ID: <1faf47660906270926s38ee652dtf9150febb60b358e@mail.gmail.com> (raw)
When attempting quilt push -a with mmotm-2009-0625-1549, failure at
procfs-provide-stack-information-for-threads-v08.patch as below. quilt
enters infinite loop: "No file to patch. Skipping patch. \can't find
file to patch at input line 20" See below.
---CUT HERE---
Applying patch proc-connector-add-event-for-process-becoming-session-leader-checkpatch-fixes.patch
patching file drivers/connector/cn_proc.c
Applying patch procfs-provide-stack-information-for-threads-v08.patch
can't find file to patch at input line 20
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
--------------------------
No file to patch. Skipping patch.
can't find file to patch at input line 20
No file to patch. Skipping patch.
can't find file to patch at input line 20
<etc.>
reply other threads:[~2009-06-27 16:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1faf47660906270926s38ee652dtf9150febb60b358e@mail.gmail.com \
--to=mrhinelander@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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
Powered by JetHome