linux-kernel - [rfc 0/2] timerfd -- implement missing parts to checkpoint and restore timerfd state

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 31 Mar 2014 21:54:07 +0400
From:	Cyrill Gorcunov <gorcunov@...nvz.org>
To:	linux-kernel@...r.kernel.org
Cc:	shawn@...rchofgit.com, tglx@...utronix.de,
	akpm@...ux-foundation.org, avagin@...nvz.org, xemul@...allels.com,
	gorcunov@...nvz.org
Subject: [rfc 0/2] timerfd -- implement missing parts to checkpoint and restore timerfd state

Timerfd interface provides to user-space almost all data needed to checkpoint
and restore it, the only missing parts are @clockid (and while @ticks can be
read by simple read() call there is no way to write its value back). The series
exports them to userspace via /proc/pid/fdinfo/N interface and with write()
call one can setup @ticks back to a timer.

Please take a look. This is rfc to figure out if there a better way
to handle timerfds (maybe ioctls with complete timer context or somthing).
Also I'm not sure in one aspect -- if someone sets non-zero @ticks to
a timer, should I mark it as expired? Thomas, could you please give
me some advice on it?

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