linux-kernel - Re: mmotm 2009-06-30-12-50 uploaded

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 30 Jun 2009 13:19:48 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Valdis.Kletnieks@...edu
CC:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: mmotm 2009-06-30-12-50 uploaded

Valdis.Kletnieks@...edu wrote:
> On Tue, 30 Jun 2009 12:51:30 PDT, akpm@...ux-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@...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.
> 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.

patch version problem?  I'm not seeing an error there.

Applying patch procfs-provide-stack-information-for-threads-v08.patch
patching file Documentation/filesystems/proc.txt
patching file fs/exec.c
Hunk #1 succeeded at 1340 (.[33moffset -4 lines.[00m).
patching file fs/proc/array.c
patching file fs/proc/task_mmu.c
patching file include/linux/sched.h
Hunk #1 succeeded at 1486 (.[33moffset 26 lines.[00m).
patching file kernel/fork.c
Hunk #1 succeeded at 1094 (.[33moffset -1 lines.[00m).


> patch --version
patch 2.5.9

-- 
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/
--
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/