linux-kernel - Re: A better interface, perhaps: a timed signal flag

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

Message-Id: <1154104885.13509.142.camel@localhost.localdomain>
Date:	Fri, 28 Jul 2006 17:41:25 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Theodore Tso <tytso@....edu>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Neil Horman <nhorman@...driver.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Segher Boessenkool <segher@...nel.crashing.org>,
	Dave Airlie <airlied@...il.com>, linux-kernel@...r.kernel.org,
	a.zummo@...ertech.it, jg@...edesktop.org
Subject: Re: A better interface, perhaps: a timed signal flag

Ar Gwe, 2006-07-28 am 10:52 -0400, ysgrifennodd Theodore Tso:
> Good point, and limiting this facility to one such timeout per
> task_struct seems like a reasonable restriction. 

Why is this any better than using a thread or signal handler ? From the
implementation side its certainly horrible - we will be trying to write
user pages from an IRQ event. Far better to let the existing thread code
deal with it.


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