From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Subject: Re: KASAN: use-after-free Read in sctp_packet_transmit Date: Sat, 06 Jan 2018 15:16:54 -0200 Message-ID: References: <94eb2c1fcf4cf899b405620eaa66@google.com> <20180106170254.GH725@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: syzbot , David Miller , LKML , linux-sctp@vger.kernel.org, netdev , Neil Horman , syzkaller-bugs@googlegroups.com, Vladislav Yasevich To: Dmitry Vyukov Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Em 6 de janeiro de 2018 15:09:45 BRST, Dmitry Vyukov escreveu: >On Sat, Jan 6, 2018 at 6:02 PM, Marcelo Ricardo Leitner > wrote: >> On Fri, Jan 05, 2018 at 02:07:01PM -0800, syzbot wrote: >>> Hello, >>> >>> syzkaller hit the following crash on >>> 8a4816cad00bf14642f0ed6043b32d29a05006ce >>> >git://git=2Ekernel=2Eorg/pub/scm/linux/kernel/git/davem/net-next=2Egit/ma= ster >>> compiler: gcc (GCC) 7=2E1=2E1 20170620 >>> =2Econfig is attached >>> Raw console output is attached=2E >>> Unfortunately, I don't have any reproducer for this bug yet=2E >> >> How can we tell if there wasn't any list corruption messages before >> the panic? > >Hi Marcelo, > >syzbot always gives reports on non-tainted kernels=2E So, no, there was >nothing bad before this=2E OK=2E Thanks --=20 Enviado de meu dispositivo Android com K-9 mail=2E Desculpe-me pela brevid= ade=2E