linux-kernel - Re: [PATCH UPDATE] deflate stack usage in lib/inflate.c

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: <200704130102.30588.ak@suse.de>
Date:	Fri, 13 Apr 2007 01:02:30 +0200
From:	Andi Kleen <ak@...e.de>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Tim Yamin <plasmaroo@...too.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH UPDATE] deflate stack usage in lib/inflate.c

On Friday 13 April 2007 00:56:56 Jeremy Fitzhardinge wrote:
> Andi Kleen wrote:
> >> (This was under Xen, but there's no reason it couldn't happen on bare
> >>   hardware.)
> >>     
> >
> > Hmm, does Xen perhaps not use interrupt stacks?
> 
> Looks like that's all done in do_IRQ, so it should be independent of
> whether its Xen or not.  And the stack overflow check is performed on
> the main stack, before switching to the interrupt stack.

Yes, but then we should have seen more frequently, shouldn't we? I always
run with the stack overflow check enabled and I don't think I ever saw 
warnings in inflate.

Something must be different in the Xen setup. Dunno if it's a bug,
but such differences could cause more problems later.

-Andi



-
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/