linux-kernel - LinuxPPS & spinlocks

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]

Message-ID: <20070727184418.GV9840@enneenne.com>
Date:	Fri, 27 Jul 2007 20:44:18 +0200
From:	Rodolfo Giometti <giometti@...eenne.com>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: LinuxPPS & spinlocks

By looking at spinlocks and thinking better to the lock problems for
pps_events() I found this (possible) solution...

The pps_event() is now protected by a spinlock against
pps_register_source() and pps_unregister_source(), but since I cannot
disable IRQs I used the spin_trylock() into the pps_events() so even
if the process context holds the lock and an PPS event arrives (IRQ)
the system doesn't hang. Note that we cannot lose an event without
problems.

It could be more acceptable? I removed the "volatile" attribute! :)

Rodolfo

-- 

GNU/Linux Solutions                  e-mail:    giometti@...eenne.com
Linux Device Driver                             giometti@...dd.com
Embedded Systems                     		giometti@...ux.it
UNIX programming                     phone:     +39 349 2432127

View attachment "proposed_patch" of type "text/plain" (67888 bytes)