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] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.58.0807011541490.27372@gandalf.stny.rr.com>
Date:	Tue, 1 Jul 2008 15:42:14 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Noah Watkins <noahwatkins@...il.com>
cc:	Sven-Thorsten Dietrich <sven@...bigcorporation.com>,
	LKML <linux-kernel@...r.kernel.org>,
	RT <linux-rt-users@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	paulmck <paulmck@...ux.vnet.ibm.com>
Subject: Re: [BUG RT] 2.6.25.8-rt7 on 8-way


On Tue, 1 Jul 2008, Noah Watkins wrote:

>
> While I have disabled RCU tracing to suppress the messages, I am
> getting them in another context:
>
> BUG: using smp_processor_id() in preemptible [00000000] code: sshd/3114
> caller is __qdisc_run+0x12e/0x1b5
> Pid: 3114, comm: sshd Not tainted 2.6.25.8-rt7 #3
>
> Call Trace:
>  [<ffffffff8112da39>] debug_smp_processor_id+0xad/0xb8
>  [<ffffffff8120e264>] __qdisc_run+0x12e/0x1b5
>  [<ffffffff811ff1c8>] dev_queue_xmit+0x140/0x278
>  [<ffffffff8122239e>] ip_queue_xmit+0x2c2/0x350
>  [<ffffffff8127f8a6>] add_preempt_count+0x12/0x94
>  [<ffffffff8108263e>] __inc_zone_state+0x6a/0x88
>  [<ffffffff81231ffe>] tcp_transmit_skb+0x77e/0x7ba
>  [<ffffffff8109aa60>] kmem_cache_alloc_node+0x129/0x152
>  [<ffffffff81233a75>] __tcp_push_pending_frames+0x713/0x7df
>  [<ffffffff81228da2>] tcp_sendmsg+0x93a/0xa52
>  [<ffffffff811f0e97>] sock_aio_write+0xf8/0x110
>  [<ffffffff8109feeb>] do_sync_write+0xc9/0x10c
>  [<ffffffff81046da6>] autoremove_wake_function+0x0/0x2e
>  [<ffffffff8103868b>] current_fs_time+0x1e/0x24
>  [<ffffffff810a06ae>] vfs_write+0xc0/0x156
>  [<ffffffff810a0c67>] sys_write+0x48/0x74
>  [<ffffffff8100bf6b>] tracesys+0xdc/0xe1
>
>

Thanks for reporting this. This is a different issue. I'll investigate it.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ