On 2013-02-05 15:38, Johannes Berg wrote:
What's protecting this feature from stomping on an existing connection
when specifying the source port?
Nothing. Presumably if you specify it you know what you're doing, and
don't also create a connection to the same IP from the same port?
Hmm. Maybe we could allocate the socket anyway and make it allocate the
chosen port, failing if it isn't available? I guess I need to check the
APIs.
I guess this might work: http://p.sipsolutions.net/e5bc789d26b5e34a.txt
Yep, seems to work, I'll fold that in. (Tested by having a TCP
connection open and requesting the same port to be used)
Great! Patch looks good otherwise IMHO.
Cheers,
Pontus
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
