From: syzbot <syzbot+ad8ca40ecd77896d51e2@syzkaller.appspotmail.com>
To: catalin.marinas@arm.com, davem@davemloft.net, dvyukov@google.com,
herbert@gondor.apana.org.au, kuznet@ms2.inr.ac.ru,
kvalo@codeaurora.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, luciano.coelho@intel.com,
netdev@vger.kernel.org, steffen.klassert@secunet.com,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
yoshfuji@linux-ipv6.org
Subject: Re: memory leak in kobject_set_name_vargs (2)
Date: Fri, 26 Jul 2019 16:26:00 -0700 [thread overview]
Message-ID: <00000000000083ffc4058e9dddf0@google.com> (raw)
In-Reply-To: <000000000000edcb3c058e6143d5@google.com>
syzbot has bisected this bug to:
commit 0e034f5c4bc408c943f9c4a06244415d75d7108c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Wed May 18 18:51:25 2016 +0000
iwlwifi: fix mis-merge that breaks the driver
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10f955f0600000
start commit: 3bfe1fc4 Merge tag 'for-5.3/dm-changes-2' of git://git.ker..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=12f955f0600000
console output: https://syzkaller.appspot.com/x/log.txt?x=14f955f0600000
kernel config: https://syzkaller.appspot.com/x/.config?x=dcfc65ee492509c6
dashboard link: https://syzkaller.appspot.com/bug?extid=ad8ca40ecd77896d51e2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=135cbed0600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14dd4e34600000
Reported-by: syzbot+ad8ca40ecd77896d51e2@syzkaller.appspotmail.com
Fixes: 0e034f5c4bc4 ("iwlwifi: fix mis-merge that breaks the driver")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2019-07-26 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000edcb3c058e6143d5@google.com>
2019-07-26 23:26 ` syzbot [this message]
2019-07-27 2:29 ` Linus Torvalds
2019-07-27 2:56 ` Qian Cai
2019-08-08 17:04 ` Dmitry Vyukov
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=00000000000083ffc4058e9dddf0@google.com \
--to=syzbot+ad8ca40ecd77896d51e2@syzkaller.appspotmail.com \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luciano.coelho@intel.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--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