linux-kernel - Re: [next-20141231] sched: WARNING: CPU: 1 PID: 2539 at kernel/sched/core.c:7303 __might

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+icZUVMEqD9uDouL=FM8147NoWsgufkn2odTKEDgtiqcN3_3Q@mail.gmail.com>
Date:	Sun, 4 Jan 2015 00:42:38 +0100
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	linux-next <linux-next@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>,
	Ming Lei <ming.lei@...onical.com>, Jens Axboe <axboe@...com>
Subject: Re: [next-20141231] sched: WARNING: CPU: 1 PID: 2539 at
 kernel/sched/core.c:7303 __might_sleep+0xbd/0xd0()

On Thu, Jan 1, 2015 at 11:28 AM, Sedat Dilek <sedat.dilek@...il.com> wrote:
> Hi,
>
> with next-20141231 I am seeing this call-trace:
>
> [   88.028632] ------------[ cut here ]------------
> [   88.028643] WARNING: CPU: 1 PID: 2539 at kernel/sched/core.c:7303
> __might_sleep+0xbd/0xd0()
> [   88.028646] do not call blocking ops when !TASK_RUNNING; state=1
> set at [<ffffffff810b82dd>] prepare_to_wait_event+0x5d/0x110
> [   88.028648] Modules linked in: ppp_deflate bsd_comp ppp_async
> crc_ccitt arc4 iwldvm uvcvideo mac80211 snd_hda_codec_hdmi
> snd_hda_codec_realtek parport_pc videobuf2_vmalloc
> snd_hda_codec_generic ppdev videobuf2_memops snd_hda_intel
> videobuf2_core rfcomm bnep snd_hda_controller option snd_hda_codec
> v4l2_common i915 joydev videodev usb_wwan snd_hwdep usbserial
> cdc_ether snd_pcm usbnet btusb snd_seq_midi snd_seq_midi_event
> bluetooth psmouse snd_rawmidi iwlwifi snd_seq i2c_algo_bit
> drm_kms_helper snd_timer serio_raw snd_seq_device samsung_laptop drm
> snd cfg80211 soundcore video lpc_ich intel_rst wmi mac_hid binfmt_misc
> lp parport hid_generic usbhid hid r8169 mii usb_storage
> [   88.028694] CPU: 1 PID: 2539 Comm: fio Not tainted
> 3.19.0-rc2-next20141231-1-iniza-small #1
> [   88.028695] Hardware name: SAMSUNG ELECTRONICS CO., LTD.
> 530U3BI/530U4BI/530U4BH/530U3BI/530U4BI/530U4BH, BIOS 13XK 03/28/2013
> [   88.028697]  ffffffff81a66d5f ffff880070f43c38 ffffffff8175c50c
> 0000000000000000
> [   88.028700]  ffff880070f43c88 ffff880070f43c78 ffffffff810753ba
> ffff880070f43d28
> [   88.028703]  ffffffff81a67ef5 000000000000026d 0000000000000000
> 0000000000dce810
> [   88.028706] Call Trace:
> [   88.028712]  [<ffffffff8175c50c>] dump_stack+0x4c/0x65
> [   88.028716]  [<ffffffff810753ba>] warn_slowpath_common+0x8a/0xc0
> [   88.028719]  [<ffffffff81075436>] warn_slowpath_fmt+0x46/0x50
> [   88.028722]  [<ffffffff810c2c3d>] ? mark_held_locks+0x6d/0xa0
> [   88.028725]  [<ffffffff81761732>] ? mutex_lock_nested+0x2b2/0x4e0
> [   88.028727]  [<ffffffff810b82dd>] ? prepare_to_wait_event+0x5d/0x110
> [   88.028729]  [<ffffffff810b82dd>] ? prepare_to_wait_event+0x5d/0x110
> [   88.028731]  [<ffffffff8109c3ad>] __might_sleep+0xbd/0xd0
> [   88.028734]  [<ffffffff817614af>] mutex_lock_nested+0x2f/0x4e0
> [   88.028736]  [<ffffffff810b82d3>] ? prepare_to_wait_event+0x53/0x110
> [   88.028739]  [<ffffffff8124433f>] aio_read_events+0x4f/0x2d0
> [   88.028742]  [<ffffffff810c2e7d>] ? trace_hardirqs_on+0xd/0x10
> [   88.028745]  [<ffffffff812447c0>] read_events+0x200/0x320
> [   88.028747]  [<ffffffff810b81c0>] ? wait_woken+0xc0/0xc0
> [   88.028750]  [<ffffffff810e9690>] ? hrtimer_get_res+0x50/0x50
> [   88.028753]  [<ffffffff81244ca0>] ? lookup_ioctx+0xd0/0x140
> [   88.028755]  [<ffffffff812466b2>] SyS_io_getevents+0x62/0x100
> [   88.028759]  [<ffffffff813b59be>] ? trace_hardirqs_on_thunk+0x3a/0x3f
> [   88.028762]  [<ffffffff817663ed>] system_call_fastpath+0x16/0x1b
> [   88.028764] ---[ end trace dba4f4a06fcdd178 ]---
>
> Attached are my kernel-config, kern-log and patch.
>
> Please, contact me if you need more informations.
>

[ CC Jens and Ming Lei ]

This is reprocible when running fio for example.

# grep "Comm: fio" /var/log/kern.log | grep next
Dec 31 22:16:11 fambox kernel: [ 4164.195498] CPU: 0 PID: 31786 Comm:
fio Not tainted 3.19.0-rc2-next20141231-2-iniza-small #1
Dec 31 22:32:28 fambox kernel: [   88.028694] CPU: 1 PID: 2539 Comm:
fio Not tainted 3.19.0-rc2-next20141231-1-iniza-small #1
Jan  1 14:57:24 fambox kernel: [  152.560454] CPU: 3 PID: 2647 Comm:
fio Not tainted 3.19.0-rc2-next20141231-1-loopmq-small #1
Jan  1 15:41:36 fambox kernel: [  132.919590] CPU: 0 PID: 2667 Comm:
fio Not tainted 3.19.0-rc2-next20141231-3-loopmq-small #1
Jan  1 21:45:48 fambox kernel: [  603.958985] CPU: 3 PID: 2868 Comm:
fio Not tainted 3.19.0-rc2-next20141231-4-loopmq-small #1
Jan  2 00:13:58 fambox kernel: [  306.024050] CPU: 1 PID: 2977 Comm:
fio Not tainted 3.19.0-rc2-next20141231.4-loopmq-small #1
Jan  2 05:37:00 fambox kernel: [  372.874364] CPU: 2 PID: 3088 Comm:
fio Not tainted 3.19.0-rc2-next-20141231.5-loopmq-small #1
Jan  3 14:43:09 fambox kernel: [  557.742941] CPU: 0 PID: 7003 Comm:
fio-2.2.3 Not tainted 3.19.0-rc2-next-20141231.6-loopmq-small #1
Jan  3 19:37:27 fambox kernel: [ 1428.960438] CPU: 1 PID: 4936 Comm:
fio-2.2.3 Not tainted 3.19.0-rc2-next-20141231.6-loopmq-small #1
Jan  4 00:34:06 fambox kernel: [15101.094582] CPU: 0 PID: 12394 Comm:
fio-2.2.3 Not tainted 3.19.0-rc2-next-20141231.6-loopmq-small #1

- Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/