Re: [PATCH net-next] TCP: make seq # error messages more readable

2018-07-13 Thread Randy Dunlap
On 07/13/2018 06:38 AM, Eric Dumazet wrote: > > > On 07/12/2018 05:48 PM, Randy Dunlap wrote: >> From: Randy Dunlap >> >> Attempt to make cryptic TCP seq number error messages clearer by >> (1) adding the function name, (2) identifying the errors as "seq # bug", >> and (3) grouping the field ide

Re: [PATCH net-next] TCP: make seq # error messages more readable

2018-07-13 Thread Eric Dumazet
On 07/12/2018 05:48 PM, Randy Dunlap wrote: > From: Randy Dunlap > > Attempt to make cryptic TCP seq number error messages clearer by > (1) adding the function name, (2) identifying the errors as "seq # bug", > and (3) grouping the field identifiers and values by separating them > with commas.

[PATCH net-next] TCP: make seq # error messages more readable

2018-07-12 Thread Randy Dunlap
From: Randy Dunlap Attempt to make cryptic TCP seq number error messages clearer by (1) adding the function name, (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 changed from: recvmsg bug