From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: syzbot <syzbot+7823fa3f3e2d69341ea8@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
nhorman@tuxdriver.com, syzkaller-bugs@googlegroups.com,
vyasevich@gmail.com
Subject: Re: KASAN: use-after-free Read in sctp_outq_tail
Date: Tue, 12 Feb 2019 19:19:20 +0000 [thread overview]
Message-ID: <20190212191920.GI10665@localhost.localdomain> (raw)
In-Reply-To: <0000000000002015db0581b71858@google.com>
On Tue, Feb 12, 2019 at 11:04:27AM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: d4104460aec1 Add linux-next specific files for 20190211
> git tree: linux-next
I can't find this commit. How can I know for sure which commits are in?
Recent patches are involved with this code, but not sure what was
included on the test.
Marcelo
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: syzbot <syzbot+7823fa3f3e2d69341ea8@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
nhorman@tuxdriver.com, syzkaller-bugs@googlegroups.com,
vyasevich@gmail.com
Subject: Re: KASAN: use-after-free Read in sctp_outq_tail
Date: Tue, 12 Feb 2019 17:19:20 -0200 [thread overview]
Message-ID: <20190212191920.GI10665@localhost.localdomain> (raw)
In-Reply-To: <0000000000002015db0581b71858@google.com>
On Tue, Feb 12, 2019 at 11:04:27AM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: d4104460aec1 Add linux-next specific files for 20190211
> git tree: linux-next
I can't find this commit. How can I know for sure which commits are in?
Recent patches are involved with this code, but not sure what was
included on the test.
Marcelo
next prev parent reply other threads:[~2019-02-12 19:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 10:13 KASAN: use-after-free Read in sctp_outq_select_transport syzbot
2018-10-23 10:13 ` syzbot
2018-10-27 7:33 ` Xin Long
2018-10-27 7:33 ` Xin Long
2019-02-12 19:04 ` KASAN: use-after-free Read in sctp_outq_tail syzbot
2019-02-12 19:04 ` syzbot
2019-02-12 19:19 ` Marcelo Ricardo Leitner [this message]
2019-02-12 19:19 ` Marcelo Ricardo Leitner
2019-02-13 8:27 ` Dmitry Vyukov
2019-02-13 8:27 ` Dmitry Vyukov
2019-02-13 4:35 ` Xin Long
2019-02-13 4:35 ` Xin Long
2019-02-13 8:29 ` Dmitry Vyukov
2019-02-13 8:29 ` Dmitry Vyukov
2019-02-13 13:51 ` Marcelo Ricardo Leitner
2019-02-13 13:51 ` Marcelo Ricardo Leitner
2019-02-13 14:00 ` Dmitry Vyukov
2019-02-13 14:00 ` Dmitry Vyukov
2019-02-14 14:03 ` Xin Long
2019-02-14 14:03 ` Xin Long
2019-02-14 14:17 ` Marcelo Ricardo Leitner
2019-02-14 14:17 ` Marcelo Ricardo Leitner
2019-02-14 14:23 ` Marcelo Ricardo Leitner
2019-02-14 14:23 ` Marcelo Ricardo Leitner
2019-02-14 14:39 ` Marcelo Ricardo Leitner
2019-02-14 14:39 ` Marcelo Ricardo Leitner
2019-02-14 14:52 ` Xin Long
2019-02-14 14:52 ` Xin Long
2019-02-14 15:27 ` Marcelo Ricardo Leitner
2019-02-14 15:27 ` Marcelo Ricardo Leitner
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=20190212191920.GI10665@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=syzbot+7823fa3f3e2d69341ea8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.