linux-sctp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: syzbot <syzbot+3950016bd95c2ca0377b@syzkaller.appspotmail.com>
Cc: linux-fbdev@vger.kernel.org, mareklindner@neomailbox.ch,
	nhorman@tuxdriver.com, b.zolnierkie@samsung.com,
	netdev@vger.kernel.org, vyasevich@gmail.com,
	b.a.t.m.a.n@lists.open-mesh.org, a@unstable.cc,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	syzkaller-bugs@googlegroups.com, lkundrak@v3.sk,
	linux-sctp@vger.kernel.org, sw@simonwunderlich.de,
	kuba@kernel.org, davem@davemloft.net
Subject: Re: general protection fault in sctp_ulpevent_nofity_peer_addr_change
Date: Fri, 20 Mar 2020 01:17:09 +0000	[thread overview]
Message-ID: <20200320011709.GE3756@localhost.localdomain> (raw)
In-Reply-To: <00000000000041ca9305a13ea3e0@google.com>

On Thu, Mar 19, 2020 at 05:48:02PM -0700, syzbot wrote:
> syzbot has bisected this bug to:
> 
> commit da2648390ce3d409218b6bbbf2386d8ddeec2265
> Author: Lubomir Rintel <lkundrak@v3.sk>
> Date:   Thu Dec 20 18:13:09 2018 +0000
> 
>     pxa168fb: trivial typo fix

Certainly not ;-)

  reply	other threads:[~2020-03-20  1:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 19:07 general protection fault in sctp_ulpevent_nofity_peer_addr_change syzbot
2020-03-20  0:48 ` syzbot
2020-03-20  1:17   ` Marcelo Ricardo Leitner [this message]
2020-08-10 15:37 ` general protection fault in sctp_ulpevent_notify_peer_addr_change syzbot
2020-08-10 18:30   ` Marcelo Ricardo Leitner
2020-08-12 14:19     ` Jonas Falkevik

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=20200320011709.GE3756@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=a@unstable.cc \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=davem@davemloft.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kuba@kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lkundrak@v3.sk \
    --cc=mareklindner@neomailbox.ch \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=sw@simonwunderlich.de \
    --cc=syzbot+3950016bd95c2ca0377b@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;
as well as URLs for NNTP newsgroup(s).