linux-kernel - RE: 2.6.24.7-rt26 and 2.6.26.8-rt13

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]

Date:	Wed, 21 Jan 2009 08:10:28 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Lampersperger Andreas <lampersperger.andreas@...denhain.de>
cc:	LKML <linux-kernel@...r.kernel.org>,
	RT <linux-rt-users@...r.kernel.org>
Subject: RE: 2.6.24.7-rt26 and 2.6.26.8-rt13


On Wed, 21 Jan 2009, Lampersperger Andreas wrote:

> Hi,
> 
> I'm using kernel 2.6.26.8-rt13 with CONFIG_DYNAMIC_FTRACE=y set.
> When loading a kernel object the following message appear:
> 
> BUG: sleeping function called from invalid context insmod(1370) at include/asm/uaccess_32.h:560
> in_atomic():0 [00000000], irqs_disabled():1
> Pid: 1370, comm: insmod Not tainted 2.6.26.8-rt13-heros5 #8
>  [<c011e13e>] __might_sleep+0xe5/0xea
>  [<c011439a>] ftrace_modify_code+0x22/0xa6
>  [<c0114364>] ? ftrace_test_p6nop+0x0/0xa
>  [<c0162fb4>] __ftrace_update_code+0xed/0x2cf
>  [<c0114364>] ? ftrace_test_p6nop+0x0/0xa
>  [<c0163730>] ftrace_convert_nops+0x57/0x73
>  [<c0163761>] ftrace_init_module+0x15/0x17
>  [<c01491da>] sys_init_module+0x14c9/0x1a7d
>  [<c016d89d>] ? generic_file_aio_read+0x49a/0x4d6
>  [<c0311ef9>] ? sub_preempt_count+0xa2/0xb0
>  [<c02180c4>] ? strpbrk+0x0/0x2b
>  [<c019b7b9>] ? dput+0x34/0xe4
>  [<c0104b31>] sysenter_past_esp+0x6a/0x99
>  =======================
> 
> Is it not possible to use rt-patches and dynamic tracepoints?

No, it should. That is a bug, I'll try to reproduce it, could you send me 
your config.

Thanks,

-- Steve

--
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/