linux-kernel - [PATCH 0/3] posix timers: Extend kernel API to report more info about timers (v2)

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: <512665BA.9040802@parallels.com>
Date:	Thu, 21 Feb 2013 22:21:46 +0400
From:	Pavel Emelyanov <xemul@...allels.com>
To:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Michael Kerrisk <mtk.manpages@...il.com>,
	Matthew Helsley <matt.helsley@...il.com>,
	linux-api@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/3] posix timers: Extend kernel API to report more info about
 timers (v2)

Hi.

Here's another approach to address the problems with insufficient API 
of posix timers.

Currently kernel doesn't provide any API for getting information about
what timers are currently created by process and in which state they 
are. Initially the proposal was to add a couple of system calls that 
would list timers owned by a task and provide info about sigevent 
configuration of particular timer.

Matthew pointed out, that fixing the API in _that_ way should better be
left to POSIX people :) and we'd better go with new /proc files. So
here's how the /proc file can look like to provide info about timers
(patches 2 and 3).

And, yet again, I'd like to fix the way timer IDs are generated by
replacing global IDR with hashtable and making IDs generation 
per-signal_struct (patch 1). A note: mentioned by Matthew important
patches about timers IDR are "don't feed negative ID into idr_xxx
engine". Since I remove the whole IDR stuff from timers, I do
conflict with them, but this is easy to fix :)

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