linux-kernel - BUG at net/core/sock.c when using PREEMPT_VOLUNTARY/PREEMPT

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-next>] [day] [month] [year] [list]

Message-ID: <s2xe6bf505b1004230933z9416196cobef1b2847fef1feb@mail.gmail.com>
Date:	Fri, 23 Apr 2010 11:33:23 -0500
From:	Xianghua Xiao <xiaoxianghua@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	Thomas Gleixner <tglx@...utronix.de>
Subject: BUG at net/core/sock.c when using PREEMPT_VOLUNTARY/PREEMPT_DESKTOP

I'm running a 2.6.33.1 on a powerpc board, when choose either
PREEMPT_NONE or PREEMPT_RT I can run iperf between two boards just
fine.

However when I enable PREEMPT_VOLUNTARY, I saw BUG immediately when I
start to run iperf:
-------------------------------------------
BUG: sleeping function called from invalid context at net/core/sock.c:1537
pcnt: 0 256 in_atomic(): 0, irqs_disabled(): 0, pid: 1364, name: iperf
Call Trace:
[cdc19d10] [c0009614] show_stack+0x70/0x1b8 (unreliable)
[cdc19d50] [c001d370] __might_sleep+0x104/0x108
[cdc19d60] [c0283018] release_sock+0x6c/0xd0
[cdc19d80] [c02c27d0] tcp_sendmsg+0x258/0xc70
[cdc19df0] [c027e86c] sock_aio_write+0x13c/0x14c
--- Exception: cdc19df8 at (null)
    LR = (null)
[cdc19e50] [c008cd58] do_sync_write+0xb4/0x140 (unreliable)
[cdc19ef0] [c008dcb4] vfs_write+0x198/0x1a0
[cdc19f10] [c008ddf4] sys_write+0x58/0xc8
[cdc19f40] [c00134c8] ret_from_syscall+0x0/0x38
--- Exception: c01 at 0x1001b010
    LR = 0x1001aff8

If I enable PREEMPT_DESKTOP instead, I saw BUG before I even start iperf:
-------------------------------------------
BUG: sleeping function called from invalid context at net/core/sock.c:1537
pcnt: 0 256 in_atomic(): 0, irqs_disabled(): 0, pid: 1089, name: xsupplicant
Call Trace:
[ce3abd90] [c00097c0] show_stack+0x70/0x1b8 (unreliable)
[ce3abdd0] [c001ca5c] __might_sleep+0x104/0x108
[ce3abde0] [c02ac900] release_sock+0xa0/0x120
[ce3abe00] [c0311a20] inet_stream_connect+0x98/0x2f4
[ce3abe50] [c02a9f38] sys_connect+0x84/0xe4
[ce3abf00] [c02ab330] sys_socketcall+0x1f0/0x20c
[ce3abf40] [c00139e8] ret_from_syscall+0x0/0x38

Anyone can reproduce this?

Thanks,
Xianghua
--
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/