From: Chuck Wolber <[email protected]> Date: Thu, 29 Sep 2005 23:25:14 -0700 (PDT) > Does this really qualify as a necessary bug fix? Yes. Without this unconnected ipv6 UDP sockets end up using the wrong route or IPSEC path. - 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/
- Follow-Ups:
- Re: [PATCH 07/10] [PATCH] check connect(2) status for IPv6 UDP socket
- From: Mitsuru KANDA / 神田 充 <[email protected]>
- Re: [PATCH 07/10] [PATCH] check connect(2) status for IPv6 UDP socket
- References:
- [PATCH 00/10] -stable review
- From: Chris Wright <[email protected]>
- [PATCH 07/10] [PATCH] check connect(2) status for IPv6 UDP socket
- From: Chris Wright <[email protected]>
- Re: [PATCH 07/10] [PATCH] check connect(2) status for IPv6 UDP socket
- From: Chuck Wolber <[email protected]>
- [PATCH 00/10] -stable review
- Prev by Date: Re: [linux-usb-devel] RFC drivers/usb/storage/libusual
- Next by Date: Re: 2.6.14-rc2-git7 crashed on amd64 (usenet gateway) after 18 hours
- Previous by thread: Re: [PATCH 07/10] [PATCH] check connect(2) status for IPv6 UDP socket
- Next by thread: Re: [PATCH 07/10] [PATCH] check connect(2) status for IPv6 UDP socket
- Index(es):
