From: Rohit Thapliyal <redacted>
np NULL check doesn't seem required here as it shall never
be NULL anyways in inet6_sk(sk).
Signed-off-by: Rohit Thapliyal <redacted>
Signed-off-by: Manjeet Pawar <redacted>
Signed-off-by: David Miller <davem@davemloft.net>
Reviewed-by: Akhilesh Kumar <redacted>
---
v2->v3: Modified as per the suggestion from David Miller
ip6_xmit calls are made without checking NULL np
pointer, so no need to explicitly check NULL np in
ip6_xmit.
include/linux/ipv6.h | 2 +-
net/ipv6/ip6_output.c | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
From: Eric Dumazet <hidden> Date: 2016-11-29 15:26:23
On Tue, 2016-11-29 at 12:02 +0530, Manjeet Pawar wrote:
quoted hunk
From: Rohit Thapliyal <redacted>
np NULL check doesn't seem required here as it shall never
be NULL anyways in inet6_sk(sk).
Signed-off-by: Rohit Thapliyal <redacted>
Signed-off-by: Manjeet Pawar <redacted>
Signed-off-by: David Miller <davem@davemloft.net>
Reviewed-by: Akhilesh Kumar <redacted>
---
v2->v3: Modified as per the suggestion from David Miller
ip6_xmit calls are made without checking NULL np
pointer, so no need to explicitly check NULL np in
ip6_xmit.
include/linux/ipv6.h | 2 +-
net/ipv6/ip6_output.c | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
David suggestion was about np being NULL or not in ip6_xmit()
But have you checked inet6_sk() was never called for a TCPv6 TIMEWAIT or
SYN_RECV request ?