linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	rafael@kernel.org, syzkaller-bugs@googlegroups.com,
	torvalds@linux-foundation.org
Cc: Muchun Song <smuchun@gmail.com>
Subject: Re: WARNING: refcount bug in kobject_add_internal
Date: Tue, 02 Jul 2019 12:44:18 +1000	[thread overview]
Message-ID: <38d777292f5335b5ea5f8fd7c0b58c514dda525a.camel@kernel.crashing.org> (raw)
In-Reply-To: <000000000000106b11058ca6f7f2@google.com>

Munchun, is this what your patch fixes ?


On Mon, 2019-07-01 at 16:27 -0700, syzbot wrote:
> syzbot has bisected this bug to:
> 
> commit 726e41097920a73e4c7c33385dcc0debb1281e18
> Author: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Date:   Tue Jul 10 00:29:10 2018 +0000
> 
>      drivers: core: Remove glue dirs from sysfs earlier
> 
> bisection log:  
> https://syzkaller.appspot.com/x/bisect.txt?x=140d6739a00000
> start commit:   6fbc7275 Linux 5.2-rc7
> git tree:       upstream
> final crash:    
> https://syzkaller.appspot.com/x/report.txt?x=160d6739a00000
> console output: 
> https://syzkaller.appspot.com/x/log.txt?x=120d6739a00000
> kernel config:  
> https://syzkaller.appspot.com/x/.config?x=bff6583efcfaed3f
> dashboard link: 
> https://syzkaller.appspot.com/bug?extid=32259bb9bc1a487ad206
> syz repro:      
> https://syzkaller.appspot.com/x/repro.syz?x=115bad39a00000
> C reproducer:   
> https://syzkaller.appspot.com/x/repro.c?x=1241bdd5a00000
> 
> Reported-by: syzbot+32259bb9bc1a487ad206@syzkaller.appspotmail.com
> Fixes: 726e41097920 ("drivers: core: Remove glue dirs from sysfs
> earlier")
> 
> For information about bisection process see: 
> https://goo.gl/tpsmEJ#bisection


  reply	other threads:[~2019-07-02  2:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 19:47 WARNING: refcount bug in kobject_add_internal syzbot
2019-07-01 23:27 ` syzbot
2019-07-02  2:44   ` Benjamin Herrenschmidt [this message]
2019-07-02  3:07     ` Muchun Song
2020-04-16  6:25 ` 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=38d777292f5335b5ea5f8fd7c0b58c514dda525a.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=smuchun@gmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=torvalds@linux-foundation.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).