From: Greg KH <gregkh@linuxfoundation.org>
To: syzbot
<bot+9f03168400f56df89dbc6f1751f4458fe739ff29@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in sysfs_remove_group
Date: Fri, 27 Oct 2017 10:43:37 +0200 [thread overview]
Message-ID: <20171027084337.GA25695@kroah.com> (raw)
In-Reply-To: <001a113ed2fa7bedfe055c8316a5@google.com>
On Fri, Oct 27, 2017 at 01:29:31AM -0700, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 4ed590271a65b0fbe3eb1cf828ad5af16603c8ce
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
>
>
>
>
> sysfs group 'loop' not found for kobject 'loop1'
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 21947 at fs/sysfs/group.c:237
> sysfs_remove_group+0x156/0x1a0 fs/sysfs/group.c:235
> Kernel panic - not syncing: panic_on_warn set ...
It's a warning that someone did something wrong with their code, any
hint as to how you are triggering this?
thanks,
greg k-h
next parent reply other threads:[~2017-10-27 8:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a113ed2fa7bedfe055c8316a5@google.com>
2017-10-27 8:43 ` Greg KH [this message]
2017-10-27 9:10 ` WARNING in sysfs_remove_group Dmitry Vyukov
2017-10-27 9:23 ` Greg KH
2017-10-27 9:30 ` Dmitry Vyukov
2017-12-23 20:50 ` syzbot
2018-05-02 14:11 ` Tetsuo Handa
2018-05-02 14:24 ` Greg KH
2018-05-04 11:47 ` [PATCH] loop: remember whether sysfs_create_group() succeeded Tetsuo Handa
2018-05-04 14:15 ` Jens Axboe
2018-05-04 14:27 ` Tetsuo Handa
2018-05-04 14:30 ` Jens Axboe
2018-05-04 14:40 ` Tetsuo Handa
2018-05-04 14:43 ` Jens Axboe
2018-05-04 16:14 ` [PATCH v2] " Tetsuo Handa
2018-05-04 16:27 ` Jens Axboe
2018-05-04 16:47 ` Tetsuo Handa
2018-05-05 10:46 ` [PATCH] " Milan Broz
2018-05-05 11:49 ` Tetsuo Handa
2018-05-08 9:02 ` Milan Broz
2018-05-09 12:31 ` Jan Kara
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=20171027084337.GA25695@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bot+9f03168400f56df89dbc6f1751f4458fe739ff29@syzkaller.appspotmail.com \
--cc=linux-kernel@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.