[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20161103.161941.367902189230382386.davem@davemloft.net>
Date: Thu, 03 Nov 2016 16:19:41 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: eric.dumazet@...il.com
Cc: andreyknvl@...gle.com, gerrit@....abdn.ac.uk, dccp@...r.kernel.org,
netdev@...r.kernel.org, syzkaller@...glegroups.com, kcc@...gle.com,
glider@...gle.com, edumazet@...gle.com, dvyukov@...gle.com
Subject: Re: [PATCH net] dccp: do not send reset to already closed sockets
From: Eric Dumazet <eric.dumazet@...il.com>
Date: Wed, 02 Nov 2016 18:04:24 -0700
> From: Eric Dumazet <edumazet@...gle.com>
>
> Andrey reported following warning while fuzzing with syzkaller
>
> WARNING: CPU: 1 PID: 21072 at net/dccp/proto.c:83 dccp_set_state+0x229/0x290
> Kernel panic - not syncing: panic_on_warn set ...
...
> Fix this the same way we did for TCP in commit 565b7b2d2e63
> ("tcp: do not send reset to already closed sockets")
>
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
> Reported-by: Andrey Konovalov <andreyknvl@...gle.com>
> Tested-by: Andrey Konovalov <andreyknvl@...gle.com>
Applied and queued up for -stable.
Powered by blists - more mailing lists