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: <alpine.LFD.0.999.0707301452380.13448@enigma.security.iitk.ac.in>
Date:	Mon, 30 Jul 2007 15:01:28 +0530 (IST)
From:	Satyam Sharma <satyam@...radead.org>
To:	Rodolfo Giometti <giometti@...eenne.com>
cc:	Chris Friesen <cfriesen@...tel.com>,
	David Woodhouse <dwmw2@...radead.org>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: LinuxPPS & spinlocks

Hi Rodolfo,


On Mon, 30 Jul 2007, Rodolfo Giometti wrote:

> On Mon, Jul 30, 2007 at 10:39:38AM +0530, Satyam Sharma wrote:
> > 
> > Nopes, this isn't quite correct/safe. I suggest you should read:
> > 
> > http://www.kernel.org/pub/linux/kernel/people/rusty/kernel-locking/
> 
> I read it but still I don't see why my solution isn't correct/safe. :)

What does the section on locking between hard irq contexts (or between
user process context and hard irq context) say?

> Can you please propose to me your solution?

As I said, you could just use the spin_lock_irqsave/restore() variants ...
If you want, I can try and implement the other bits that I had suggested
for the other things as well :-)


Ciao,
Satyam
-
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