netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+b1212b1215db82ff9211@syzkaller.appspotmail.com>
To: alexios.zavras@intel.com, allison@lohutok.net, andriin@fb.com,
	ap420073@gmail.com, ast@kernel.org, bpf@vger.kernel.org,
	daniel@iogearbox.net, davem@davemloft.net, ebiederm@xmission.com,
	gregkh@linuxfoundation.org, jhogan@kernel.org, kafai@fb.com,
	keescook@chromium.org, kuba@kernel.org, kuznet@ms2.inr.ac.ru,
	linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
	lirongqing@baidu.com, mojha@codeaurora.org,
	netdev@vger.kernel.org, paulburton@kernel.org,
	penguin-kernel@I-love.SAKURA.ne.jp, ptalbert@redhat.com,
	ralf@linux-mips.org, rppt@linux.ibm.com, songliubraving@fb.com,
	swinslow@gmail.com, syzkaller-bugs@googlegroups.com,
	tbogendoerfer@suse.de, tglx@linutronix.de, yhs@fb.com,
	yoshfuji@linux-ipv6.org
Subject: Re: WARNING: refcount bug in sk_alloc (2)
Date: Sat, 21 Mar 2020 03:06:03 -0700	[thread overview]
Message-ID: <000000000000b0a7eb05a15a8ce7@google.com> (raw)
In-Reply-To: <000000000000e9ca5105a08797f2@google.com>

syzbot has bisected this bug to:

commit b78e9d63a3b6307b6b786e6ba189d3978b60ceb5
Author: Thomas Bogendoerfer <tbogendoerfer@suse.de>
Date:   Thu Jan 9 12:33:40 2020 +0000

    MIPS: SGI-IP27: use asm/sn/agent.h for including HUB related stuff

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17330a23e00000
start commit:   0d1c3530 net_sched: keep alloc_hash updated after hash all..
git tree:       net
final crash:    https://syzkaller.appspot.com/x/report.txt?x=14b30a23e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=10b30a23e00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c2e311dba9a02ba9
dashboard link: https://syzkaller.appspot.com/bug?extid=b1212b1215db82ff9211
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14e76a39e00000

Reported-by: syzbot+b1212b1215db82ff9211@syzkaller.appspotmail.com
Fixes: b78e9d63a3b6 ("MIPS: SGI-IP27: use asm/sn/agent.h for including HUB related stuff")

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

      reply	other threads:[~2020-03-21 10:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 22:25 WARNING: refcount bug in sk_alloc (2) syzbot
2020-03-21 10:06 ` syzbot [this message]

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=000000000000b0a7eb05a15a8ce7@google.com \
    --to=syzbot+b1212b1215db82ff9211@syzkaller.appspotmail.com \
    --cc=alexios.zavras@intel.com \
    --cc=allison@lohutok.net \
    --cc=andriin@fb.com \
    --cc=ap420073@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jhogan@kernel.org \
    --cc=kafai@fb.com \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=lirongqing@baidu.com \
    --cc=mojha@codeaurora.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulburton@kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=ptalbert@redhat.com \
    --cc=ralf@linux-mips.org \
    --cc=rppt@linux.ibm.com \
    --cc=songliubraving@fb.com \
    --cc=swinslow@gmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tbogendoerfer@suse.de \
    --cc=tglx@linutronix.de \
    --cc=yhs@fb.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 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).