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: <20130425142452.908423538@linutronix.de>
Date:	Thu, 25 Apr 2013 20:31:42 -0000
From:	Thomas Gleixner <tglx@...utronix.de>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	John Stultz <john.stultz@...aro.org>, Ingo Molnar <mingo@...e.hu>,
	Magnus Damm <magnus.damm@...il.com>
Subject: [patch 00/15] clocksource/events: Overhaul (un)registration

The clocksource_unregister() interface is broken. A clocksource can be
removed unconditionally even if there is no fallback clocksource
available. clocksources in a module can be removed as well. Aside of
that the registration part lacks a few sanity checks as well.

The clockevents layer does not allow unregistration, but for
reconfigurable hardware this is a must have feature.

The following patch series fixes the clocksource part and adds
unregister support for clockevent devices.

Thanks,

	tglx
---
 drivers/clocksource/dw_apb_timer.c |   12 -
 include/linux/clockchips.h         |    4 
 include/linux/clocksource.h        |    7 
 include/linux/dw_apb_timer.h       |    1 
 kernel/time/clockevents.c          |  271 ++++++++++++++++++++++++++++++++-----
 kernel/time/clocksource.c          |  190 +++++++++++++++++++------
 kernel/time/tick-broadcast.c       |   33 +++-
 kernel/time/tick-common.c          |  189 +++++++++----------------
 kernel/time/tick-internal.h        |   17 +-
 kernel/time/timekeeping.c          |   20 +-
 10 files changed, 514 insertions(+), 230 deletions(-)


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