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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 20 Jan 2008 10:27:48 +1100 From: Rusty Russell <rusty@...tcorp.com.au> To: Tejun Heo <htejun@...il.com> Cc: linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Jeff Garzik <jgarzik@...ox.com>, Ash Willis <ashwillis@...grammer.net>, linux-pcmcia@...ts.infradead.org, virtualization@...ts.linux-foundation.org Subject: Re: [PATCH 3/3] Makes lguest's irq handler typesafe On Saturday 19 January 2008 15:08:28 Tejun Heo wrote: > Rusty Russell wrote: > > There are three possibilities: (1) force everyone to use void *, (2) > > force everyone to be type-correct, (3) allow both with some tricks. > > Currently we're on (1). For kthread, with only dozens of users, I chose > > (2) (very simple, easy to understand). I think for widespread things > > like timer and interrupt handlers, I think (3) is the right way to go. > > Yeah, during transition, we definitely want (3). Hi Tejun. I'm thinking an open-ended transition. I don't see a big reason to churn working code, since we can easily support both. > Yeah, I think we need a good flame war to determine our > heading and converting timer shouldn't take too much of your time, right? Insightful comment, you've convinced me! Thanks, Rusty. -- 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