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: Thu, 17 Nov 2016 18:02:33 +0000 From: "Reshetova, Elena" <elena.reshetova@...el.com> To: Peter Zijlstra <peterz@...radead.org> CC: David Windsor <dave@...gbits.org>, Kees Cook <keescook@...omium.org>, Greg KH <gregkh@...uxfoundation.org>, Will Deacon <will.deacon@....com>, Arnd Bergmann <arnd@...db.de>, Thomas Gleixner <tglx@...utronix.de>, "Ingo Molnar" <mingo@...nel.org>, "H. Peter Anvin" <hpa@...or.com>, LKML <linux-kernel@...r.kernel.org>, Alexei Starovoitov <alexei.starovoitov@...il.com>, Daniel Borkmann <daniel@...earbox.net> Subject: RE: [RFC][PATCH 2/7] kref: Add kref_read() > Even if we now find all occurrences of atomic_t used as refcounter > (which we cannot actually guarantee in any case unless someone > manually reads every line) and convert it to refcount_t, we still have > atomic_t type present and new usage of it as refount will crawl in. It > is just a matter of time IMO. >Improve tooling. The patterns shouldn't be _that_ hard to find. Once the tools are good, new code isn't a problem either. Moreover, thinking of out of tree drivers: you think they would always do checkpatch or run some of our tools for security checks?
Powered by blists - more mailing lists