linux-kernel - Re: [RFC] timers, pointers to functions and type safety

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: <20061203210113.GF9876@elf.ucw.cz>
Date:	Sun, 3 Dec 2006 22:01:13 +0100
From:	Pavel Machek <pavel@....cz>
To:	Roman Zippel <zippel@...ux-m68k.org>
Cc:	Russell King <rmk+lkml@....linux.org.uk>,
	Al Viro <viro@....linux.org.uk>,
	Thomas Gleixner <tglx@...utronix.de>,
	Matthew Wilcox <matthew@....cx>,
	Linus Torvalds <torvalds@...l.org>, linux-arch@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] timers, pointers to functions and type safety

On Sun 2006-12-03 16:21:25, Roman Zippel wrote:
> Hi,
> 
> On Sun, 3 Dec 2006, Russell King wrote:
> 
> > I agree with Al, Matthew and Pavel.  The current timer stuff is a pita
> > and needs fixing, and it seems Al has come up with a good way to do it
> > without adding additional crap into every single user of timers.
> 
> What exactly is the pita here? Al only came up with some rather 
> theoretical problems with no practical relevance.

Lack of type-checking in timers is ugly.

> > Al - I look forward to your changes.
> 
> I don't. The current API is maybe not perfect, but changing the API for no 
> practical benefit would be an even bigger pita. I'd rather keep it as is.

Al is trying to  add type-checking in pretty nice & straightforward
manner. Please let him do it.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/