| 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: <20150311.164807.1389597491151339402.davem@davemloft.net> Date: Wed, 11 Mar 2015 16:48:07 -0400 (EDT) From: David Miller <davem@...emloft.net> To: ryabinin.a.a@...il.com Cc: sasha.levin@...cle.com, rostedt@...dmis.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org, netdev@...r.kernel.org, linux-arch@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-crypto@...r.kernel.org Subject: Re: [PATCH] mm: kill kmemcheck From: Andrey Ryabinin <ryabinin.a.a@...il.com> Date: Wed, 11 Mar 2015 23:01:00 +0300 > 2015-03-11 21:44 GMT+03:00 David Miller <davem@...emloft.net>: >> From: Sasha Levin <sasha.levin@...cle.com> >> Date: Wed, 11 Mar 2015 13:25:47 -0400 >> >>> You're probably wondering why there are changes to SPARC in that patchset? :) >> >> Libsanitizer doesn't even build have the time on sparc, the release >> manager has to hand patch it into building again every major release >> because of the way ASAN development is done out of tree and local >> commits to the gcc tree are basically written over during the >> next merge. >> > > Libsanitizer is userspace lib it's for userspace ASan, KASan doesn't use it. > We have our own 'libsanitzer' in kernel. I was speaking about ASAN development in general, of which the libsanitizer issue is a byproduct. -- 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