All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: syzbot <syzbot+e5b57b8780297657b25b@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, leon@kernel.org,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
	nhorman@tuxdriver.com, roid@mellanox.com, saeedm@mellanox.com,
	syzkaller-bugs@googlegroups.com, vladbu@mellanox.com,
	vyasevich@gmail.com
Subject: Re: KASAN: use-after-free Read in sctp_sock_dump
Date: Mon, 28 Oct 2019 12:36:48 -0300	[thread overview]
Message-ID: <20191028153648.GF4250@localhost.localdomain> (raw)
In-Reply-To: <000000000000e68ee20595fa33be@google.com>

On Mon, Oct 28, 2019 at 08:32:08AM -0700, syzbot wrote:
> Hello,
> 
> syzbot found the following crash on:
> 
> HEAD commit:    d6d5df1d Linux 5.4-rc5
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=17ef5a70e00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=2bcb64e504d04eff
> dashboard link: https://syzkaller.appspot.com/bug?extid=e5b57b8780297657b25b
> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> userspace arch: i386
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16cd8800e00000
> 
> The bug was bisected to:
> 
> commit 61086f391044fd587af9d70a9b8f6f800dd474ba
> Author: Vlad Buslov <vladbu@mellanox.com>
> Date:   Fri Aug 2 19:21:56 2019 +0000
> 
>     net/mlx5e: Protect encap hash table with mutex
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=135960af600000

This is weird. This mlx5e commit has nothing to do with SCTP diag
dump.

  Marcelo

WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: syzbot <syzbot+e5b57b8780297657b25b@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, leon@kernel.org,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
	nhorman@tuxdriver.com, roid@mellanox.com, saeedm@mellanox.com,
	syzkaller-bugs@googlegroups.com, vladbu@mellanox.com,
	vyasevich@gmail.com
Subject: Re: KASAN: use-after-free Read in sctp_sock_dump
Date: Mon, 28 Oct 2019 15:36:48 +0000	[thread overview]
Message-ID: <20191028153648.GF4250@localhost.localdomain> (raw)
In-Reply-To: <000000000000e68ee20595fa33be@google.com>

On Mon, Oct 28, 2019 at 08:32:08AM -0700, syzbot wrote:
> Hello,
> 
> syzbot found the following crash on:
> 
> HEAD commit:    d6d5df1d Linux 5.4-rc5
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x\x17ef5a70e00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x+cb64e504d04eff
> dashboard link: https://syzkaller.appspot.com/bug?extidåb57b8780297657b25b
> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> userspace arch: i386
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x\x16cd8800e00000
> 
> The bug was bisected to:
> 
> commit 61086f391044fd587af9d70a9b8f6f800dd474ba
> Author: Vlad Buslov <vladbu@mellanox.com>
> Date:   Fri Aug 2 19:21:56 2019 +0000
> 
>     net/mlx5e: Protect encap hash table with mutex
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x\x135960af600000

This is weird. This mlx5e commit has nothing to do with SCTP diag
dump.

  Marcelo

  reply	other threads:[~2019-10-28 15:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28 15:32 KASAN: use-after-free Read in sctp_sock_dump syzbot
2019-10-28 15:32 ` syzbot
2019-10-28 15:36 ` Marcelo Ricardo Leitner [this message]
2019-10-28 15:36   ` Marcelo Ricardo Leitner
2019-10-28 21:18   ` Eric Dumazet
2019-10-28 21:18     ` Eric Dumazet

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=20191028153648.GF4250@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=davem@davemloft.net \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=roid@mellanox.com \
    --cc=saeedm@mellanox.com \
    --cc=syzbot+e5b57b8780297657b25b@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vladbu@mellanox.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.