ACK: [PATCH v2 Yakkety SRU 1/1] net: fix incorrect original ingress device index in PKTINFO

Seth Forshee seth.forshee at
Fri Apr 21 12:28:27 UTC 2017

On Thu, Apr 20, 2017 at 07:40:17PM -0300, jorge.niedbalski at wrote:
> From: Wei Zhang < at>
> BugLink:
> When we send a packet for our own local address on a non-loopback
> interface (e.g. eth0), due to the change had been introduced from
> commit 0b922b7a829c ("net: original ingress device index in PKTINFO"), the
> original ingress device index would be set as the loopback interface.
> However, the packet should be considered as if it is being arrived via the
> sending interface (eth0), otherwise it would break the expectation of the
> userspace application (e.g. the DHCPRELEASE message from dhcp_release
> binary would be ignored by the dnsmasq daemon, since it come from lo which
> is not the interface dnsmasq bind to)
> Fixes: 0b922b7a829c ("net: original ingress device index in PKTINFO")
> Acked-by: David Ahern <dsa at>
> Signed-off-by: Wei Zhang < at>
> Signed-off-by: David S. Miller <davem at>
> (cherry picked from commit f0c16ba8933ed217c2688b277410b2a37ba81591)
> Signed-off-by: Jorge Niedbalski <jorge.niedbalski at>

Acked-by: Seth Forshee <seth.forshee at>

More information about the kernel-team mailing list