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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 18 Jan 2022 19:33:53 -0400 From: Jason Gunthorpe <jgg@...pe.ca> To: Kees Cook <keescook@...omium.org> Cc: Jann Horn <jannh@...gle.com>, Peter Huewe <peterhuewe@....de>, Jarkko Sakkinen <jarkko@...nel.org>, linux-integrity@...r.kernel.org, Stefan Berger <stefanb@...ux.ibm.com>, linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org Subject: Re: [PATCH v2] tpm: vtpm_proxy: Double-check to avoid buffer overflow On Tue, Jan 18, 2022 at 01:20:40PM -0800, Kees Cook wrote: > I haven't been able to reproduce the specific cause of why GCC decided to > do the bounds checking, but it's not an unreasonable thing to check for, > just for robustness. Well, the commit message should explain this is to silence a compiler bug and maybe put some colour on what version(s) are actually buggy.. Jason
Powered by blists - more mailing lists