From: Marcelo <marcelo.leitner@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+5adcca18fca253b4cb15@syzkaller.appspotmail.com>,
David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
linux-sctp@vger.kernel.org, netdev <netdev@vger.kernel.org>,
Neil Horman <nhorman@tuxdriver.com>,
syzkaller-bugs@googlegroups.com,
Vladislav Yasevich <vyasevich@gmail.com>
Subject: Re: KASAN: use-after-free Read in sctp_packet_transmit
Date: Sat, 06 Jan 2018 15:16:54 -0200 [thread overview]
Message-ID: <A559F0F4-93AD-43E2-AFD6-7D4ABAF4E87C@gmail.com> (raw)
In-Reply-To: <CACT4Y+Y_kWEqfqSEiq_yOk7_nm5MuejNbORcfQgspzKHC3aTng@mail.gmail.com>
Em 6 de janeiro de 2018 15:09:45 BRST, Dmitry Vyukov <dvyukov@google.com> escreveu:
>On Sat, Jan 6, 2018 at 6:02 PM, Marcelo Ricardo Leitner
><marcelo.leitner@gmail.com> wrote:
>> On Fri, Jan 05, 2018 at 02:07:01PM -0800, syzbot wrote:
>>> Hello,
>>>
>>> syzkaller hit the following crash on
>>> 8a4816cad00bf14642f0ed6043b32d29a05006ce
>>>
>git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master
>>> compiler: gcc (GCC) 7.1.1 20170620
>>> .config is attached
>>> Raw console output is attached.
>>> Unfortunately, I don't have any reproducer for this bug yet.
>>
>> 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. So, no, there was
>nothing bad before this.
OK. Thanks
--
Enviado de meu dispositivo Android com K-9 mail. Desculpe-me pela brevidade.
next prev parent reply other threads:[~2018-01-06 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94eb2c1fcf4cf899b405620eaa66@google.com>
2018-01-06 6:50 ` Xin Long
2018-01-06 17:02 ` Marcelo Ricardo Leitner
2018-01-06 17:09 ` Dmitry Vyukov
2018-01-06 17:16 ` Marcelo [this message]
2018-01-06 17:29 ` Denis Kirjanov
2018-05-12 20:00 ` Eric Biggers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A559F0F4-93AD-43E2-AFD6-7D4ABAF4E87C@gmail.com \
--to=marcelo.leitner@gmail.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=syzbot+5adcca18fca253b4cb15@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vyasevich@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®