All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e1628a5e87492e6f1b76@syzkaller.appspotmail.com>
To: davem@davemloft.net, dledford@redhat.com, jgg@ziepe.ca,
	kuznet@ms2.inr.ac.ru, kvalo@codeaurora.org,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	monis@mellanox.com, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org
Subject: Re: INFO: trying to register non-static key in icmp_send
Date: Sat, 23 Mar 2019 18:25:00 -0700	[thread overview]
Message-ID: <000000000000e560fa0584ccf44d@google.com> (raw)
In-Reply-To: <0000000000007cd20e05809c2f96@google.com>

syzbot has bisected this bug to:

commit abd5f00844ec7fa507064ee4a22b3605c64c7d31
Author: Kalle Valo <kvalo@codeaurora.org>
Date:   Tue Mar 27 07:06:18 2018 +0000

     Merge ath-next from  
git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12f9389b200000
start commit:   4aa9fc2a Revert "mm, memory_hotplug: initialize struct pag..
git tree:       upstream
final crash:    https://syzkaller.appspot.com/x/report.txt?x=11f9389b200000
console output: https://syzkaller.appspot.com/x/log.txt?x=16f9389b200000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4fceea9e2d99ac20
dashboard link: https://syzkaller.appspot.com/bug?extid=e1628a5e87492e6f1b76
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=175c96ef400000

Reported-by: syzbot+e1628a5e87492e6f1b76@syzkaller.appspotmail.com
Fixes: abd5f00844ec ("Merge ath-next from  
git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  reply	other threads:[~2019-03-24  1:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 17:33 INFO: trying to register non-static key in icmp_send syzbot
2019-03-24  1:25 ` syzbot [this message]
2019-03-24 12:09   ` Kalle Valo

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=000000000000e560fa0584ccf44d@google.com \
    --to=syzbot+e1628a5e87492e6f1b76@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=monis@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yoshfuji@linux-ipv6.org \
    /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.