linux-kernel - Re: stack overflow on Sparc64

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080620.144424.168785883.davem@davemloft.net>
Date:	Fri, 20 Jun 2008 14:44:24 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mpatocka@...hat.com
Cc:	sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org,
	agk@...hat.com
Subject: Re: stack overflow on Sparc64

From: Mikulas Patocka <mpatocka@...hat.com>
Date: Fri, 20 Jun 2008 17:25:26 -0400 (EDT)

> On Fri, 20 Jun 2008, David Miller wrote:
> 
> > From: Mikulas Patocka <mpatocka@...hat.com>
> > Date: Fri, 20 Jun 2008 17:14:41 -0400 (EDT)
> >
> > It means i386 and every other platform potentially has the same exact
> > problem.
> >
> > What point wrt. sparc64 are you trying to make here? :-)
> 
> The difference is that i386 takes minimum 4 bytes per stack frame and 
> sparc64 192 bytes per stack frame. So this problem will kill sparc64 
> sooner.
> 
> But yes, it is general problem and should be solved in arch-independent 
> code.

I agree on both counts.  Although I'm curious what the average stack
frame sizes look like on x86_64 and i386, and also how this area
appears on powerpc.

One mitigating factor on sparc64 is that typically when there are lots
of devices with interrupts there are also lots of cpus, and we evenly
distribute the IRQ targetting amongst the available cpus on sparc64.

This is probably why, in practice, these problems tend to not surface
often.

In any event, with the work you've accomplished and my implementation
of IRQ stacks for sparc64 we should be able to get things in much
better shape.
--
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/