linux-kernel - [RFC] Posix timers improvements, requied for CRIU project

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

Date:	Tue, 9 Oct 2012 19:18:23 +0400
From:	Stanislav Kinsbursky <skinsbursky@...allels.com>
To:	"tglx@...utronix.de" <tglx@...utronix.de>,
	"devel@...nvz.org" <devel@...nvz.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Pavel Emelianov <xemul@...allels.com>
Subject: [RFC] Posix timers improvements, requied for CRIU project

Hi.
We would like to make CRIU able to migrate posix timers.
Currently we require additional info, which have to be provided by kernel.
In particular, it's:
1) Timers id's.
2) Timer clock (gained by id).
3) Timer sigevent structure.
4) Timer current overrun status (not the last one).

We are not sure, how to implement such support properly.

Right now we are considering two approaches of posix timers interface update 
(for dump):

1) First one it to use /proc filesystem to provide posix timers data by task 
(something like /proc/<pid>/posix_timers)

2) Second one is to add new system calls like:

int timer_getnext(int start_id);	// return next timer id after start-id
int timer_getclock(timer_t id, cclock_t *clock); // return clock
int timer_getsigevent(timer_t id, struct sigevent *evp); // return sigevent
int timer_getoverrun_cur(timer_t id, int *overrun); // current overrun

Of course, both approaches can be combined.

Also, we require a syscall to set desired overrun (on restore):

int timer_setoverrun(timer_t id, int *overrun);

Moreover, we need to make posix timer id to be allocated per task (not globally) 
to make sure, that we can restore timer with desired id (desired id can be 
passed to timer_create() in timerid variable).
Our current idea is to replace idr by hash table, where 
"per_process_struct_signal + per_process_id" will be the key.

We would greatly appreciate any comments or suggestions.
Thanks.

-- 
Best regards,
Stanislav Kinsbursky
--
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/