Re: [PATCH v2] tcp: identify cryptic messages as TCP seq # bugs

2018-07-18 Thread David Miller
From: Randy Dunlap Date: Tue, 17 Jul 2018 18:27:45 -0700 > From: Randy Dunlap > > Attempt to make cryptic TCP seq number error messages clearer by > (1) identifying the source of the message as "TCP", (2) identifying the > errors as "seq # bug", and (3) grouping the field identifiers and values

Re: [PATCH v2] tcp: identify cryptic messages as TCP seq # bugs

2018-07-17 Thread Eric Dumazet
On 07/17/2018 06:27 PM, Randy Dunlap wrote: > From: Randy Dunlap > > Attempt to make cryptic TCP seq number error messages clearer by > (1) identifying the source of the message as "TCP", (2) identifying the > errors as "seq # bug", and (3) grouping the field identifiers and values > by separa

[PATCH v2] tcp: identify cryptic messages as TCP seq # bugs

2018-07-17 Thread Randy Dunlap
From: Randy Dunlap Attempt to make cryptic TCP seq number error messages clearer by (1) identifying the source of the message as "TCP", (2) identifying the errors as "seq # bug", and (3) grouping the field identifiers and values by separating them with commas. E.g., the following message is chan