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
| ||
|
Date: Fri, 24 Feb 2012 18:35:40 +0530 From: Siddhesh Poyarekar <siddhesh.poyarekar@...il.com> To: Andrew Morton <akpm@...ux-foundation.org> Cc: KOSAKI Motohiro <kosaki.motohiro@...il.com>, linux-mm@...ck.org, linux-kernel@...r.kernel.org, Alexander Viro <viro@...iv.linux.org.uk>, linux-fsdevel@...r.kernel.org, Jamie Lokier <jamie@...reable.org>, Mike Frysinger <vapier@...too.org> Subject: Re: [PATCH] Mark thread stack correctly in proc/<pid>/maps On Fri, Feb 24, 2012 at 1:52 AM, Andrew Morton <akpm@...ux-foundation.org> wrote: > Looks OK to me, thanks. I doubt if those interface changes will cause > significant disruption. > I just found one breakage due to this patch: `cat /proc/self/maps` does not always get the stack marked right. I think this is because it gets the $esp a little to early, even before the vma is sent to its randomized space. That is why /proc/self/smaps works just ok as it always wins the race due to the sheer volume of data it prints. Similarly numa_maps always fails since its write volume is lower than maps. I'll try to fix this. -- Siddhesh Poyarekar http://siddhesh.in -- 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/
Powered by blists - more mailing lists