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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061202184035.GL3078@ftp.linux.org.uk>
Date:	Sat, 2 Dec 2006 18:40:35 +0000
From:	Al Viro <viro@....linux.org.uk>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	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 Sat, Dec 02, 2006 at 07:27:56PM +0100, Thomas Gleixner wrote:
> On Sat, 2006-12-02 at 18:19 +0000, Al Viro wrote:
> > > This is going to make a lot of data structures smaller, when the
> > > timer_list is embedded in the structure itself and for the lot, which
> > > ignores the timer callback argument anyway.
> > 
> > container_of => still lousy type safety.  All over the sodding place.
> 
> Not less than timer->data, where timer data is void *

RTFPosting.  It might be void *, but it's set via SETUP_TIMER which
does type checks before casting to void *.

IOW, I don't want _any_ typecasts/container_of necessary in the code.

Sane variant is

void foo_timer(struct net_device *dev)
{
	...
}

	struct foo_dev *p = netdev_priv(dev);
	SETUP_TIMER(&p->timer, foo_timer, dev);

etc.

With warning generated if foo_timer(dev) would not be type safe.  Without
typecasts.  Without container_of().  Without any bleeding cruft at all.
-
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/