| 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
| ||
|
Message-Id: <1162339556.15900.222.camel@localhost.localdomain> Date: Wed, 01 Nov 2006 01:05:56 +0100 From: Thomas Gleixner <tglx@...utronix.de> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: akpm@...l.org, linux-kernel@...r.kernel.org, drepper@...hat.com, mingo@...e.hu, rusty@...tcorp.com.au Subject: Re: [patch 1/1] schedule removal of FUTEX_FD On Tue, 2006-10-31 at 23:48 +0000, Alan Cox wrote: > Ar Maw, 2006-10-31 am 15:09 -0800, ysgrifennodd akpm@...l.org: > > From: Andrew Morton <akpm@...l.org> > > > > Apparently FUTEX_FD is unfixably racy and nothing uses it (or if it does, it > > shouldn't). > > > > Add a warning printk, give any remaining users six months to migrate off it. > > Andrew - please use time based rate limits for this sort of thing, that > way you actually get to see who is actually using it. Not really: It might be one time calls, so a time based rate limit might exclude apps which get executed in a row. Maybe some thread->deprecated bitfield which rate limits the deprecated warning per caller would be an alternative solution. We should not have more than 32 of such deprecated functions at once. Of cource it would still spam the logs when high frequency forking servers use such interfaces, but I think the probability is low. tglx - 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