Ron Yorston <rmy@xxxxxxxxxxxx> wrote: > > Sure, but the same problem existing in other places isn't a reason not > to fix it here. If this were a real script then I might agree with you. But given that this came from a deliberately crafted script to breach the 8MB size limit, it would be pointless to fix it in just one spot because you could easily craft another script to exceed the size limit in any of the other places where we use alloca. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: [PATCH] parser: preserve characters on heap in backquote parsing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] parser: preserve characters on heap in backquote parsing
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 20 Nov 2018 10:12:13 +0800
- Cc: dash@xxxxxxxxxxxxxxx
- In-reply-to: <5bf2b001.vNHRJaq4AUGdpOBI%rmy@frippery.org>
- Organization: Core
- User-agent: NeoMutt/20170113 (1.7.2)
- References:
- Re: [PATCH] parser: preserve characters on heap in backquote parsing
- From: Ron Yorston
- Re: [PATCH] parser: preserve characters on heap in backquote parsing
- Prev by Date: eval: Use sh_warnx instead of warnx
- Next by Date: Re: parser: Do not push token back before parseheredoc
- Previous by thread: Re: [PATCH] parser: preserve characters on heap in backquote parsing
- Next by thread: [PATCH] var: ensure variables are fully initialised when unset
- Index(es):
 |