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

Andi Kleen wrote:
> 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.
>   

I guess the window is just while decompressing the root filesystem. 
Interrupts under Xen might be using a little more stack (~40-50 bytes?),
but its not a qualitative difference.  It might have more to do with
different timing.

    J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH] deflate stack usage in lib/inflate.c
  - From: Jeremy Fitzhardinge <[email protected]>
- Re: [PATCH UPDATE] deflate stack usage in lib/inflate.c
  - From: Andi Kleen <[email protected]>
- Re: [PATCH UPDATE] deflate stack usage in lib/inflate.c
  - From: Jeremy Fitzhardinge <[email protected]>
- Re: [PATCH UPDATE] deflate stack usage in lib/inflate.c
  - From: Andi Kleen <[email protected]>

Prev by Date: [PATCH] pnpbios_thread_init: don't use CLONE_SIGHAND
Next by Date: [PATCH 0/3] [UPDATED]: Multiqueue network device support
Previous by thread: Re: [PATCH UPDATE] deflate stack usage in lib/inflate.c
Next by thread: Re: [PATCH UPDATE] deflate stack usage in lib/inflate.c
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]