| 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
| ||
|
Message-ID: <20100215070219.GB14412@jm.kir.nu> Date: Mon, 15 Feb 2010 09:02:19 +0200 From: Jouni Malinen <j@...fi> To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> Cc: Michael Neuling <mikey@...ling.org>, linux-kernel@...r.kernel.org Subject: Re: 2.6.33-rc8 breaks UML with Restrict initial stack space expansion to rlimit On Mon, Feb 15, 2010 at 11:38:52AM +0900, KOSAKI Motohiro wrote: > Wow. It seems very strange. Usually stack overflow makes SIGSEGV, not SIGKILL. > plus, In my environment (x86_64 non-uml), mount command doesn't use > the stack so much. The SIGKILL part is the odd one, I would assume.. It looks like about half of the commands are failing with SIGKILL even with ulimit -s 8192 and the ulimit -s value did not really change the failure rate that much if at all. SIGSEGV starts showing up only after having limited ulimit -s to quite samll number (see my previous email). > % /usr/bin/time --format="mem %M" ls > /usr/bin/time --format="mem %M" ls > GPATH INSTALL README configure fdisk lib misc-utils schedutils > mem 3232 mem 3296 on my UML setup > % sudo /usr/bin/time --format="mem %M" mount -a > sudo /usr/bin/time --format="mem %M" mount -a > mem 2992 mem 2928 -- Jouni Malinen PGP id EFC895FA -- 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