From: Ming Lei <tom.leiming@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Jens Axboe <axboe@fb.com>, Hannes Reinecke <hare@suse.com>,
Mike Christie <mchristi@redhat.com>,
Omar Sandoval <osandov@fb.com>,
mnghuan@gmail.com, Petr Mladek <pmladek@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: loop: WARNING in sysfs_remove_group
Date: Fri, 24 Mar 2017 00:02:58 +0800 [thread overview]
Message-ID: <20170323160257.GA20432@ming.t460p> (raw)
In-Reply-To: <CACT4Y+ZgPwzao6-SJ5UzrEgnbdVXw=kez=c6jx-r4ixAQ=vrWA@mail.gmail.com>
On Thu, Mar 23, 2017 at 03:09:44PM +0100, Dmitry Vyukov wrote:
> Hello,
>
> I've got the following WARNING while running syzkaller on
> 093b995e3b55a0ae0670226ddfcb05bfbf0099ae. Note the preceding injected
> kmalloc failure, most likely it's the root cause.
>
> FAULT_INJECTION: forcing a failure.
> name failslab, interval 1, probability 0, space 0, times 0
> CPU: 3 PID: 21172 Comm: syz-executor4 Not tainted 4.11.0-rc3+ #364
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
> Call Trace:
> __dump_stack lib/dump_stack.c:16 [inline]
> dump_stack+0x1b8/0x28d lib/dump_stack.c:52
> fail_dump lib/fault-inject.c:45 [inline]
> should_fail+0x78a/0x870 lib/fault-inject.c:154
> should_failslab+0xec/0x120 mm/failslab.c:31
> slab_pre_alloc_hook mm/slab.h:434 [inline]
> slab_alloc mm/slab.c:3394 [inline]
> kmem_cache_alloc+0x200/0x720 mm/slab.c:3570
> kmem_cache_zalloc include/linux/slab.h:653 [inline]
> __kernfs_new_node+0xd1/0x430 fs/kernfs/dir.c:629
> kernfs_new_node+0x80/0xf0 fs/kernfs/dir.c:661
> kernfs_create_dir_ns+0x41/0x140 fs/kernfs/dir.c:933
> kernfs_create_dir include/linux/kernfs.h:477 [inline]
> internal_create_group+0xf7/0x8f0 fs/sysfs/group.c:124
> sysfs_create_group+0x1f/0x30 fs/sysfs/group.c:156
> loop_sysfs_init drivers/block/loop.c:802 [inline]
Looks we should have handled failure of loop_sys_init().
Thanks,
Ming
prev parent reply other threads:[~2017-03-23 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 14:09 Dmitry Vyukov
2017-03-23 16:02 ` Ming Lei [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=20170323160257.GA20432@ming.t460p \
--to=tom.leiming@gmail.com \
--cc=axboe@fb.com \
--cc=dvyukov@google.com \
--cc=hare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=mnghuan@gmail.com \
--cc=osandov@fb.com \
--cc=pmladek@suse.com \
--cc=syzkaller@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®