Results:
References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CRYPTO\]\s+Fix\s+stack\s+overrun\s+in\s+crypt\(\)\s*$/: 12 ]
Total 12 documents matching your query.
- 1. [CRYPTO] Fix stack overrun in crypt() (score: 1)
- Author: rusty@xxxxxxxxxxx>
- Date: Thu, 15 Jul 2004 21:48:40 +1000
- The stack allocation in crypt() is bogus as whether tmp_src/tmp_dst is used is determined by factors unrelated to nbytes and Since the condition for whether tmp_src/tmp_dst are used is very complex,
- /archives/netdev/2004-07/msg00386.html (8,651 bytes)
- 2. Re: [CRYPTO] Fix stack overrun in crypt() (score: 1)
- Author: vgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Date: Fri, 16 Jul 2004 11:27:36 -0400 (EDT)
- Ok, thanks, looks good. Adam Richter rewrote that code, and I have walked through it before (I guess Dave did too). Any more code reviewers welcome. - James -- James Morris <jmorris@xxxxxxxxxx>
- /archives/netdev/2004-07/msg00442.html (8,696 bytes)
- 3. Re: [CRYPTO] Fix stack overrun in crypt() (score: 1)
- Author: xena@xxxxxxxxxxx>
- Date: Sat, 17 Jul 2004 17:43:19 +1000
- Thanks for reviewing it. Unfortunately it looks like we still have a problem. gcc 3.3.4 appears to be generating incorrect output on i386 with the dynamic stack allocation used in crypt() and the fun
- /archives/netdev/2004-07/msg00456.html (9,485 bytes)
- 4. Re: [CRYPTO] Fix stack overrun in crypt() (score: 1)
- Author:
- Date: Sat, 17 Jul 2004 19:48:29 +1000
- I got it wrong. gcc is simply allocating some (12 bytes) of the space unconditionally. Sorry for the noise. -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxx
- /archives/netdev/2004-07/msg00458.html (9,114 bytes)
- 5. Re: [CRYPTO] Fix stack overrun in crypt() (score: 1)
- Author: xxxx>
- Date: Wed, 21 Jul 2004 14:58:15 -0700
- Applied, thanks Herbert. I've looked at this before, when it went in, but I'll doublecheck it now.
- /archives/netdev/2004-07/msg00501.html (8,536 bytes)
- 6. Re: [CRYPTO] Fix stack overrun in crypt() (score: 1)
- Author: xxxx>
- Date: Wed, 21 Jul 2004 15:02:19 -0700
- The goal of scatterwalk_whichbuf() is to use the temporary buffer if we are walking over a page boundary. We can use walk->data, and thus directly the page involved, if we do not cross such a boundar
- /archives/netdev/2004-07/msg00502.html (8,550 bytes)
- 7. [CRYPTO] Fix stack overrun in crypt() (score: 1)
- Author: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 15 Jul 2004 21:48:40 +1000
- Hi: The stack allocation in crypt() is bogus as whether tmp_src/tmp_dst is used is determined by factors unrelated to nbytes and Since the condition for whether tmp_src/tmp_dst are used is very compl
- /archives/netdev/2004-07/msg01202.html (8,696 bytes)
- 8. Re: [CRYPTO] Fix stack overrun in crypt() (score: 1)
- Author: James Morris <jmorris@xxxxxxxxxx>
- Date: Fri, 16 Jul 2004 11:27:36 -0400 (EDT)
- Ok, thanks, looks good. Adam Richter rewrote that code, and I have walked through it before (I guess Dave did too). Any more code reviewers welcome. - James -- James Morris <jmorris@xxxxxxxxxx>
- /archives/netdev/2004-07/msg01258.html (8,754 bytes)
- 9. Re: [CRYPTO] Fix stack overrun in crypt() (score: 1)
- Author: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Date: Sat, 17 Jul 2004 17:43:19 +1000
- Thanks for reviewing it. Unfortunately it looks like we still have a problem. gcc 3.3.4 appears to be generating incorrect output on i386 with the dynamic stack allocation used in crypt() and the fun
- /archives/netdev/2004-07/msg01272.html (9,656 bytes)
- 10. Re: [CRYPTO] Fix stack overrun in crypt() (score: 1)
- Author: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Date: Sat, 17 Jul 2004 19:48:29 +1000
- I got it wrong. gcc is simply allocating some (12 bytes) of the space unconditionally. Sorry for the noise. -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxx
- /archives/netdev/2004-07/msg01274.html (9,304 bytes)
- 11. Re: [CRYPTO] Fix stack overrun in crypt() (score: 1)
- Author: "David S. Miller" <davem@xxxxxxxxxx>
- Date: Wed, 21 Jul 2004 14:58:15 -0700
- Applied, thanks Herbert. I've looked at this before, when it went in, but I'll doublecheck it now.
- /archives/netdev/2004-07/msg01317.html (8,594 bytes)
- 12. Re: [CRYPTO] Fix stack overrun in crypt() (score: 1)
- Author: "David S. Miller" <davem@xxxxxxxxxx>
- Date: Wed, 21 Jul 2004 15:02:19 -0700
- The goal of scatterwalk_whichbuf() is to use the temporary buffer if we are walking over a page boundary. We can use walk->data, and thus directly the page involved, if we do not cross such a boundar
- /archives/netdev/2004-07/msg01318.html (8,608 bytes)
Current List: 1 - 12
Page: [1]
This search system is powered by
Namazu