linux-kernel - BUG: mmotm-2009-0625-1549 quilt fails at procfs-provide-stack-information-for-threads-v08.patch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Sat, 27 Jun 2009 09:26:50 -0700
From:	"Charles 'Mack' Rhinelander" <mrhinelander@...il.com>
To:	mm-commits@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: BUG: mmotm-2009-0625-1549 quilt fails at procfs-provide-stack-information-for-threads-v08.patch

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@...bold.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.>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/