linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+438a5abd4f53adb1c073@syzkaller.appspotmail.com>
To: davem@davemloft.net, jon.maloy@ericsson.com,
	linux-kernel@vger.kernel.org,  linux-mm@kvack.org,
	netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	 tipc-discussion@lists.sourceforge.net, ying.xue@windriver.com
Subject: Re: BUG: unable to handle kernel paging request in free_block (5)
Date: Thu, 18 Apr 2019 02:59:00 -0700	[thread overview]
Message-ID: <000000000000274d750586cb0d38@google.com> (raw)
In-Reply-To: <000000000000c770710586c6fc92@google.com>

syzbot has bisected this bug to:

commit 52dfae5c85a4c1078e9f1d5e8947d4a25f73dd81
Author: Jon Maloy <jon.maloy@ericsson.com>
Date:   Thu Mar 22 19:42:52 2018 +0000

     tipc: obtain node identity from interface by default

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=15065bdd200000
start commit:   e6986423 socket: fix compat SO_RCVTIMEO_NEW/SO_SNDTIMEO_NEW
git tree:       net
final crash:    https://syzkaller.appspot.com/x/report.txt?x=17065bdd200000
console output: https://syzkaller.appspot.com/x/log.txt?x=13065bdd200000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4fb64439e07a1ec0
dashboard link: https://syzkaller.appspot.com/bug?extid=438a5abd4f53adb1c073
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12adddbf200000

Reported-by: syzbot+438a5abd4f53adb1c073@syzkaller.appspotmail.com
Fixes: 52dfae5c85a4 ("tipc: obtain node identity from interface by default")

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


       reply	other threads:[~2019-04-18  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000000000000c770710586c6fc92@google.com>
2019-04-18  9:59 ` syzbot [this message]
2020-08-14 22:59 ` syzbot

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=000000000000274d750586cb0d38@google.com \
    --to=syzbot+438a5abd4f53adb1c073@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=jon.maloy@ericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=ying.xue@windriver.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