From: Greg KH <gregkh@linuxfoundation.org>
To: Andy Grover <agrover@redhat.com>
Cc: hjk@hansjkoch.de, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: __might_sleep in uio_read()?
Date: Wed, 2 Sep 2015 16:11:13 -0700 [thread overview]
Message-ID: <20150902231113.GA11383@kroah.com> (raw)
In-Reply-To: <55E77BF6.9000109@redhat.com>
On Wed, Sep 02, 2015 at 03:45:10PM -0700, Andy Grover wrote:
> Hi Hans and Greg,
>
> Is this an issue with uio? I swear it didn't used to throw this warning...
>
> Thanks -- Andy
>
> [ 5174.883261] ------------[ cut here ]------------
> [ 5174.883617] WARNING: CPU: 0 PID: 1532 at
> /home/agrover/git/kernel/kernel/sched/core.c:7389 __might_sleep+0x7d/0x90()
> [ 5174.884407] do not call blocking ops when !TASK_RUNNING; state=1 set at
> [<ffffffffa02a5821>] uio_read+0x91/0x170 [uio]
> [ 5174.885198] Modules linked in: tcm_loop target_core_user uio
> target_core_pscsi target_core_file target_core_iblock iscsi_target_mod
> target_core_mod uinput fuse nfsv3 nfs_acl nfs lockd grace fscache sunrpc
> microcode i2c_piix4 virtio_balloon i2c_core xfs libcrc32c crc32c_intel
> virtio_net virtio_blk
> [ 5174.887351] CPU: 0 PID: 1532 Comm: tcmu-runner Not tainted 4.2.0-rc7+
> #178
> [ 5174.887853] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
> 1.8.1-20150318_183358- 04/01/2014
> [ 5174.888633] ffffffff81a3b870 ffff880045393ca8 ffffffff817afaae
> 0000000000000000
> [ 5174.889224] ffff880045393cf8 ffff880045393ce8 ffffffff8109a846
> ffff880045393cd8
> [ 5174.889793] ffffffffa02a7150 00000000000002dc 0000000000000000
> ffff880045008000
> [ 5174.890375] Call Trace:
> [ 5174.890562] [<ffffffff817afaae>] dump_stack+0x4c/0x65
> [ 5174.890938] [<ffffffff8109a846>] warn_slowpath_common+0x86/0xc0
> [ 5174.891388] [<ffffffff8109a8c6>] warn_slowpath_fmt+0x46/0x50
> [ 5174.891808] [<ffffffffa02a5821>] ? uio_read+0x91/0x170 [uio]
> [ 5174.892237] [<ffffffffa02a5821>] ? uio_read+0x91/0x170 [uio]
> [ 5174.892653] [<ffffffff810c584d>] __might_sleep+0x7d/0x90
> [ 5174.893055] [<ffffffff811ea023>] __might_fault+0x43/0xa0
> [ 5174.893448] [<ffffffff817b31ce>] ? schedule+0x3e/0x90
> [ 5174.893820] [<ffffffffa02a58c2>] uio_read+0x132/0x170 [uio]
> [ 5174.894240] [<ffffffff810cbb80>] ? wake_up_q+0x70/0x70
> [ 5174.894620] [<ffffffff81236168>] __vfs_read+0x28/0xe0
> [ 5174.894993] [<ffffffff81353233>] ? security_file_permission+0xa3/0xc0
> [ 5174.895541] [<ffffffff8123678f>] ? rw_verify_area+0x4f/0xf0
> [ 5174.896006] [<ffffffff812368ba>] vfs_read+0x8a/0x140
> [ 5174.896391] [<ffffffff817b28f5>] ? __schedule+0x425/0xcc0
> [ 5174.896788] [<ffffffff812375d9>] SyS_read+0x49/0xb0
> [ 5174.897160] [<ffffffff817b9bee>] entry_SYSCALL_64_fastpath+0x12/0x76
> [ 5174.897625] ---[ end trace 61765cb39fe48dd5 ]---
I don't think anything has changed here in a while, any chance you can
bisect this?
And what uio driver are you using?
thanks,
greg k-h
next prev parent reply other threads:[~2015-09-02 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 22:45 __might_sleep in uio_read()? Andy Grover
2015-09-02 23:11 ` Greg KH [this message]
2015-09-03 12:26 ` Michal Hocko
2015-09-03 18:47 ` Andy Grover
2015-09-03 19:12 ` Greg KH
2015-09-03 20:12 ` Andy Grover
2015-09-04 3:59 ` Greg KH
2015-09-04 8:13 ` Michal Hocko
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=20150902231113.GA11383@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=agrover@redhat.com \
--cc=hjk@hansjkoch.de \
--cc=linux-kernel@vger.kernel.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 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.