Re: [PATCH v2 net-next] tcp: Check daddr_cache before use in tracepoint

2017-10-18 Thread David Ahern
On 10/18/17 7:15 AM, David Miller wrote: > From: David Ahern > Date: Mon, 16 Oct 2017 15:32:07 -0700 > >> Running perf in one window to capture tcp_retransmit_skb tracepoint: >> $ perf record -e tcp:tcp_retransmit_skb -a >> >> And causing a retransmission on an active TCP session (e.g., dropp

Re: [PATCH v2 net-next] tcp: Check daddr_cache before use in tracepoint

2017-10-18 Thread David Miller
From: David Ahern Date: Mon, 16 Oct 2017 15:32:07 -0700 > Running perf in one window to capture tcp_retransmit_skb tracepoint: > $ perf record -e tcp:tcp_retransmit_skb -a > > And causing a retransmission on an active TCP session (e.g., dropping > packets in the receiver, changing MTU on the

Re: [PATCH v2 net-next] tcp: Check daddr_cache before use in tracepoint

2017-10-16 Thread Cong Wang
On Mon, Oct 16, 2017 at 3:32 PM, David Ahern wrote: > Running perf in one window to capture tcp_retransmit_skb tracepoint: > $ perf record -e tcp:tcp_retransmit_skb -a > > And causing a retransmission on an active TCP session (e.g., dropping > packets in the receiver, changing MTU on the inter

[PATCH v2 net-next] tcp: Check daddr_cache before use in tracepoint

2017-10-16 Thread David Ahern
Running perf in one window to capture tcp_retransmit_skb tracepoint: $ perf record -e tcp:tcp_retransmit_skb -a And causing a retransmission on an active TCP session (e.g., dropping packets in the receiver, changing MTU on the interface to 500 and back to 1500) triggers a panic: [ 58.543144