| To: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [CRYPTO] Fix stack overrun in crypt() |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Wed, 21 Jul 2004 14:58:15 -0700 |
| Cc: | jmorris@xxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20040715114840.GA1325@gondor.apana.org.au> |
| References: | <20040715114840.GA1325@gondor.apana.org.au> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Thu, 15 Jul 2004 21:48:40 +1000 Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote: > The stack allocation in crypt() is bogus as whether tmp_src/tmp_dst > is used is determined by factors unrelated to nbytes and > src->length/dst->length. > > Since the condition for whether tmp_src/tmp_dst are used is very > complex, let's allocate them always instead of guessing. > > This fixes a number of weird crashes including those AES crashes > that people have been seeing with the 2.4 backport + ipt_conntrack. Applied, thanks Herbert. > PS I think someone should double-check the logic in the scatterwalk > stuff, especially the whichbuf bits. I've looked at this before, when it went in, but I'll double- check it now. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 2.6]: Make packet scheduler clock source configurable, David S. Miller |
|---|---|
| Next by Date: | Re: [CRYPTO] Fix stack overrun in crypt(), David S. Miller |
| Previous by Thread: | Re: [CRYPTO] Fix stack overrun in crypt(), Herbert Xu |
| Next by Thread: | Re: [CRYPTO] Fix stack overrun in crypt(), David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |