| 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
| ||
|
Date: Tue, 20 May 2008 20:30:06 +0200 From: Andi Kleen <andi@...stfloor.org> To: Arjan van de Ven <arjan@...radead.org> CC: corbet@....net, linux-kernel@...r.kernel.org Subject: Re: [PATCH] [2/11] Add unlocked_fasync Arjan van de Ven wrote: > On Tue, 20 May 2008 17:28:43 +0200 (CEST) > Andi Kleen <andi@...stfloor.org> wrote: > >> Add a new fops entry point to allow fasync without BKL. > > I (again) really don't like having another entry point for this... > it'll stay around forever rather than doing this as one step and > move on. Yes the goal is for it staying around forever, correct. And ->fasync() will go instead. Advantage is that out of tree drivers will be compile broken which I consider an advantage. Yes I know Linus said earlier that's not important to him, but in this case my standards are higher than his. Also BTW if you're that worried about the audit not getting finished then the result would be just that lots of lock_kernel()s would stay around. Hardly better. But cannot do that many drivers in one step. My goal is to just audit the remaining ones and then remove ->fasync() and unlocked_fasync stays. Will be hopefully not that far away, since fasync is relatively easy. The conversions are mostly for me to keep track which ones I audited. -Andi -- 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