| 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: Mon, 24 Jul 2006 13:15:54 +0200 From: Ingo Molnar <mingo@...e.hu> To: Catalin Marinas <catalin.marinas@...il.com> Cc: Pekka Enberg <penberg@...helsinki.fi>, linux-kernel@...r.kernel.org, Arjan van de Ven <arjan@...radead.org> Subject: Re: [PATCH 2.6.17-rc6 7/9] Remove some of the kmemleak false positives * Ingo Molnar <mingo@...e.hu> wrote: > > To the other extreme is Ingo's suggestion of using exact type > > identification but I don't think this would be acceptable for the > > kernel as it would to modify all the memory alloc calls in the > > kernel to either pass an additional parameter (the type id) or > > another post-allocation call to kmemleak to update the id. > > passing in the type ID wouldnt be that bad and it would have other > advantages as well: for example we could do strict type-checking of > allocation size versus type-we-use-it-for. > > As long as the conversion is gradual i think we could try this. I.e. > we'd default to 'no ID passed', and in that case we would fall back to > the size-based method and generate an ID out of the structure size. update: there's also a neat gcc extension trick suggested by Arjan: __builtin_classify_type(). This converts types into integers! Ingo - 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