linux-kernel - Re: [ANNOUNCE] 3.0.4-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:	Mon, 12 Sep 2011 16:53:07 +0200
From:	Mike Galbraith <efault@....de>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: [ANNOUNCE] 3.0.4-rt13

On Mon, 2011-09-12 at 15:52 +0200, Mike Galbraith wrote:

> 36717            <...>-6266  [002]   242.543129: sys_semop <-system_call_fastpath
> 36718            <...>-6266  [002]   242.543129: sys_semtimedop <-sys_semop
> 36719            <...>-6266  [002]   242.543131: ipc_lock_check <-sys_semtimedop
> 36720            <...>-6266  [002]   242.543131: ipc_lock <-ipc_lock_check
> 36721            <...>-6266  [002]   242.543132: __rcu_read_lock <-ipc_lock
> 36722            <...>-6266  [002]   242.543133: migrate_disable <-ipc_lock
> 36723            <...>-6266  [002]   242.543134: migrate_disable: migrate_disable: in_atomic:0 p->migrate_disable_atomic:0 p->migrate_disable:0
> 36724            <...>-6266  [002]   242.543134: pin_current_cpu <-migrate_disable
> 36725            <...>-6266  [002]   242.543134: _raw_spin_lock_irqsave <-migrate_disable
> 36726            <...>-6266  [002]   242.543135: _raw_spin_unlock_irqrestore <-migrate_disable
> 36727            <...>-6266  [002]   242.543135: rt_spin_lock <-ipc_lock
> 36728            <...>-6266  [002]   242.543136: ipcperms <-sys_semtimedop
> 36729            <...>-6266  [002]   242.543137: ns_capable <-ipcperms
> 36730            <...>-6266  [002]   242.543138: cap_capable <-ns_capable
> 36731            <...>-6266  [002]   242.543138: pid_vnr <-sys_semtimedop
> 36732            <...>-6266  [002]   242.543139: try_atomic_semop <-sys_semtimedop
> 36733            <...>-6266  [002]   242.543140: do_smart_update <-sys_semtimedop
> 36734            <...>-6266  [002]   242.543140: update_queue <-do_smart_update
> 36735            <...>-6266  [002]   242.543141: try_atomic_semop <-update_queue
> 36736            <...>-6266  [002]   242.543142: update_queue <-do_smart_update
> 36737            <...>-6266  [002]   242.543142: try_atomic_semop <-update_queue
> 36738            <...>-6266  [002]   242.543143: update_queue <-do_smart_update
> 36739            <...>-6266  [002]   242.543143: try_atomic_semop <-update_queue
> 36740            <...>-6266  [002]   242.543144: get_seconds <-do_smart_update
> 36741            <...>-6266  [002]   242.543144: rt_spin_unlock <-sys_semtimedop
> 36742            <...>-6266  [002]   242.543144: migrate_enable <-sys_semtimedop
> 36743            <...>-6266  [002]   242.543145: migrate_enable: migrate_enable: in_atomic:1 p->migrate_disable_atomic:0 p->migrate_disable:1

Hm.  Seems this is home grown a non-preemptive wakeup in the making.

	-Mike


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