- 1. net driver queue (score: 1)
- Author: xxxxxx>
- Date: Thu, 30 Oct 2003 13:29:02 +1100
- nd send the vendor netpoll patches that have been lying around in various vendor, -aa, etc. trees and send them along. So here goes -test9-bk3-netdrvr-exp2. B
- /archives/netdev/2003-10/msg00688.html (8,838 bytes)
- 2. o or ipsec stuff (score: 1)
- Author: y Vosburgh <fubar@xxxxxxxxxx>
- Date: Thu, 30 Oct 2003 12:17:32 +0900 (JST)
- rypto_alg_lookup, when I run the "spi" command from a freeswan snapshot from 13 October this year. The kernel is 2.6.0-test9. Oops: kernel access of bad area,
- /archives/netdev/2003-10/msg00689.html (9,609 bytes)
- 3. o or ipsec stuff (score: 1)
- Author: xxxxxxxxx>
- Date: Wed, 29 Oct 2003 22:22:50 -0500 (EST)
- what algorithm do you expect? == crypto/api.c 1.30 vs edited == -- 1.30/crypto/api.c Sat Mar 29 20:16:58 2003 +++ edited/crypto/api.c Thu Oct 30 12:07:43 200
- /archives/netdev/2003-10/msg00690.html (8,548 bytes)
- 4. o or ipsec stuff (score: 1)
- Author: xxxxxxx>
- Date: Thu, 30 Oct 2003 12:41:24 +0900 (JST)
- seems to me to be a bug in the calling code if it is trying to look up nothing -- I'd rather not paper that over. - James -- James Morris <jmorris@xxxxxxxxxx>
- /archives/netdev/2003-10/msg00691.html (9,518 bytes)
- 5. o or ipsec stuff (score: 1)
- Author: rras <paulus@xxxxxxxxx>
- Date: Wed, 29 Oct 2003 23:33:03 -0500
- r? Well, people may want to get just any algorithm. In such case, - crypto allows name == NULL, and return any algorithm (for example, an algorithm that we se
- /archives/netdev/2003-10/msg00692.html (9,246 bytes)
- 6. o or ipsec stuff (score: 1)
- Author: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
- Date: Wed, 29 Oct 2003 23:47:05 -0500 (EST)
- se
- /archives/netdev/2003-10/msg00693.html (9,504 bytes)
- 7. o or ipsec stuff (score: 1)
- Author: yoshfuji@xxxxxxxxxxxxxx>
- Date: Thu, 30 Oct 2003 14:24:58 +0900 (JST)
- luding if calling with null is a bug, and they get an inappropriate algorithm. An incorrect algorithm type could also be returned (e.g. digest instead of a ci
- /archives/netdev/2003-10/msg00694.html (10,871 bytes)
- 8. Bug somewhere in crypto or ipsec stuff (score: 1)
- Author: Paul Mackerras <paulus@xxxxxxxxx>
- Date: Thu, 30 Oct 2003 13:29:02 +1100
- I get this oops in strcmp, called from crypto_alg_lookup, when I run the "spi" command from a freeswan snapshot from 13 October this year. The kernel is 2.6.0-test9. Oops: kernel access of bad area,
- /archives/netdev/2003-10/msg01430.html (8,838 bytes)
- 9. Re: Bug somewhere in crypto or ipsec stuff (score: 1)
- Author: YOSHIFUJI Hideaki / <yoshfuji@xxxxxxxxxxxxxx>
- Date: Thu, 30 Oct 2003 12:17:32 +0900 (JST)
- I would just disallow name == NULL, well, what algorithm do you expect? == crypto/api.c 1.30 vs edited == -- 1.30/crypto/api.c Sat Mar 29 20:16:58 2003 +++ edited/crypto/api.c Thu Oct 30 12:07:43 200
- /archives/netdev/2003-10/msg01431.html (9,675 bytes)
- 10. Re: Bug somewhere in crypto or ipsec stuff (score: 1)
- Author: James Morris <jmorris@xxxxxxxxxx>
- Date: Wed, 29 Oct 2003 22:22:50 -0500 (EST)
- Good question. It seems to me to be a bug in the calling code if it is trying to look up nothing -- I'd rather not paper that over. - James -- James Morris <jmorris@xxxxxxxxxx>
- /archives/netdev/2003-10/msg01432.html (8,589 bytes)
- 11. Re: Bug somewhere in crypto or ipsec stuff (score: 1)
- Author: YOSHIFUJI Hideaki / <yoshfuji@xxxxxxxxxxxxxx>
- Date: Thu, 30 Oct 2003 12:41:24 +0900 (JST)
- Do you mean that we need to fix the caller? Well, people may want to get just any algorithm. In such case, - crypto allows name == NULL, and return any algorithm (for example, an algorithm that we se
- /archives/netdev/2003-10/msg01433.html (9,655 bytes)
- 12. Re: Bug somewhere in crypto or ipsec stuff (score: 1)
- Author: Valdis.Kletnieks@xxxxxx
- Date: Wed, 29 Oct 2003 23:33:03 -0500
- This could be embarasssing if somebody happened to have the rot13 debugging algorithm loaded..... Attachment: pgp0RzT9ode3U.pgp Description: PGP signature
- /archives/netdev/2003-10/msg01434.html (9,416 bytes)
- 13. Re: Bug somewhere in crypto or ipsec stuff (score: 1)
- Author: James Morris <jmorris@xxxxxxxxxx>
- Date: Wed, 29 Oct 2003 23:47:05 -0500 (EST)
- Yes. I think that could be dangerous, including if calling with null is a bug, and they get an inappropriate algorithm. An incorrect algorithm type could also be returned (e.g. digest instead of a ci
- /archives/netdev/2003-10/msg01435.html (9,545 bytes)
- 14. Re: Bug somewhere in crypto or ipsec stuff (score: 1)
- Author: YOSHIFUJI Hideaki / <yoshfuji@xxxxxxxxxxxxxx>
- Date: Thu, 30 Oct 2003 14:24:58 +0900 (JST)
- okay. how about this? == crypto/api.c 1.30 vs edited == -- 1.30/crypto/api.c Sat Mar 29 20:16:58 2003 +++ edited/crypto/api.c Thu Oct 30 14:21:53 2003 @@ -36,6 +36,9 @@ struct crypto_alg *crypto_alg_
- /archives/netdev/2003-10/msg01436.html (11,008 bytes)
This search system is powered by
Namazu