From: Linus Torvalds <torvalds@linux-foundation.org>
To: syzbot <syzbot+ad8ca40ecd77896d51e2@syzkaller.appspotmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
David Miller <davem@davemloft.net>,
Dmitry Vyukov <dvyukov@google.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
kuznet@ms2.inr.ac.ru, Kalle Valo <kvalo@codeaurora.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
luciano.coelho@intel.com, Netdev <netdev@vger.kernel.org>,
steffen.klassert@secunet.com,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
yoshfuji@linux-ipv6.org
Subject: Re: memory leak in kobject_set_name_vargs (2)
Date: Fri, 26 Jul 2019 19:29:16 -0700 [thread overview]
Message-ID: <CAHk-=why-PdP_HNbskRADMp1bnj+FwUDYpUZSYoNLNHMRPtoVA@mail.gmail.com> (raw)
In-Reply-To: <00000000000083ffc4058e9dddf0@google.com>
On Fri, Jul 26, 2019 at 4:26 PM syzbot
<syzbot+ad8ca40ecd77896d51e2@syzkaller.appspotmail.com> wrote:
>
> 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
While this bisection looks more likely than the other syzbot entry
that bisected to a version change, I don't think it is correct eitger.
The bisection ended up doing a lot of "git bisect skip" because of the
undefined reference to `nf_nat_icmp_reply_translation'
issue. Also, the memory leak doesn't seem to be entirely reliable:
when the bisect does 10 runs to verify that some test kernel is bad,
there are a couple of cases where only one or two of the ten run
failed.
Which makes me wonder if one or two of the "everything OK" runs were
actually buggy, but just happened to have all ten pass...
Linus
next prev parent reply other threads:[~2019-07-27 2:29 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
2019-07-27 2:29 ` Linus Torvalds [this message]
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='CAHk-=why-PdP_HNbskRADMp1bnj+FwUDYpUZSYoNLNHMRPtoVA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--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=syzbot+ad8ca40ecd77896d51e2@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox