All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+9328206518f08318a5fd@syzkaller.appspotmail.com>
To: ap420073@gmail.com, arvid.brodin@alten.se, davem@davemloft.net,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: slab-out-of-bounds Read in hsr_debugfs_rename
Date: Sat, 28 Dec 2019 05:11:02 -0800	[thread overview]
Message-ID: <0000000000009360cb059ac3575d@google.com> (raw)
In-Reply-To: <000000000000b63799059aba5164@google.com>

syzbot has bisected this bug to:

commit 4c2d5e33dcd3a6333a7895be3b542ff3d373177c
Author: Taehee Yoo <ap420073@gmail.com>
Date:   Sun Dec 22 11:26:39 2019 +0000

     hsr: rename debugfs file when interface name is changed

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1391cfb6e00000
start commit:   3c2f450e Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree:       bpf
final crash:    https://syzkaller.appspot.com/x/report.txt?x=1051cfb6e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1791cfb6e00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7f6119e2e3675a73
dashboard link: https://syzkaller.appspot.com/bug?extid=9328206518f08318a5fd
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=106d4751e00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1775a49ee00000

Reported-by: syzbot+9328206518f08318a5fd@syzkaller.appspotmail.com
Fixes: 4c2d5e33dcd3 ("hsr: rename debugfs file when interface name is  
changed")

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

      reply	other threads:[~2019-12-28 13:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-28  2:25 KASAN: slab-out-of-bounds Read in hsr_debugfs_rename syzbot
2019-12-28 13:11 ` 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=0000000000009360cb059ac3575d@google.com \
    --to=syzbot+9328206518f08318a5fd@syzkaller.appspotmail.com \
    --cc=ap420073@gmail.com \
    --cc=arvid.brodin@alten.se \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.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.