mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: linux-kernel@vger.kernel.org
Cc: mm-commits@vger.kernel.org
Subject: Re: mmotm 2009-06-30-12-50 uploaded
Date: Tue, 30 Jun 2009 16:15:52 -0400	[thread overview]
Message-ID: <54770.1246392952@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 30 Jun 2009 12:51:30 PDT." <200906301951.n5UJpUSY013305@imap1.linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]

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
--------------------------
No file to patch.  Skipping patch.
patch: **** /tmp/poPjWncl : No such file or directory
Patch procfs-provide-stack-information-for-threads-v08.patch does not apply (enforce with -f)

Yowza.  Not sure what makes it think there's an issue at line 20, looks to
*me* like the actual patch starts on line 77.

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2009-06-30 20:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 19:51 akpm
2009-06-30 20:15 ` Valdis.Kletnieks [this message]
2009-06-30 20:19   ` Randy Dunlap
2009-06-30 20:35     ` Andrew Morton
2009-06-30 20:39       ` Randy Dunlap
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 16:11         ` Andrew Morton
2009-07-04  8:14           ` Oleg Nesterov
2009-07-03 10:16       ` David Howells

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=54770.1246392952@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --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

all inboxes | Powered by JetHome®