Yes, something that can be done later. I have no issues, but was pointing out this particular path, that might be optimized later, no worries. Thanks. -- To unsubscribe from this list: send the line
So what I am really reading it for is ip_local_out which I change to take a struct net a few patches later in the series. The patches that changes everything is noticably cleaner and easier to review
Note that under normal SYNACK processing, we do not read sock_net(sk) here. Generally speaking, I do not see why storing 'struct net' pointer into a variable in the stack is very different from sk->s
Author: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
Date: Tue, 6 Oct 2015 13:53:10 -0500
Compute net and store it in a variable in the functions ip_build_and_send_pkt and ip_queue_xmit so that it does not need to be recomputed next time it is needed. Signed-off-by: "Eric W. Biederman" <e