{"push_id":2026920312,"size":2,"distinct_size":1,"ref":"refs/heads/shigeru_work","head":"6f98e3a079a33932eab42fb60ba4e281273f2026","before":"8ab34e581be44dce45b5eb9a6d6853034c5b652e","commits":[{"sha":"67ff9a521615c6a7f55cf378a9eb964911c4b198","author":{"name":"brooks","email":"5d1086e4a3aa87388b8f0d622f05565a0e9026dc@FreeBSD.org"},"message":"Remove an unneeded and incorrect memset().\n\nOn Variant I TLS architectures (aarch64, arm, mips, powerpc, and riscv)\nthe __libc_allocate_tls function allocates thread local storage memory\nwith calloc(). It then copies initialization data over the portions with\nnon-zero initial values. Before this change it would then pointlessly\nzero the already zeroed remainder of the storage. Unfortunately the\ncalculation was wrong and it would zero TLS_TCB_SIZE (2*sizeof(void *))\nadditional bytes.\n\nIn practice, this overflow only matters if the TLS segment is sized such\nthat calloc() allocates a less than TLS_TCB_SIZE extra memory. Even\nthen, the likely result will be zeroing part of the next bucket. This\ncoupled with the impact being confined to Tier II platforms means there\nwill be no security advisory for this issue.\n\nReviewed by:\tkib, dfr\nDiscussed with:\tsecurity-officer (delphij)\nMFC after:\t1 week\nFound by:\tCHERI\nSponsored by:\tDARPA, AFRL\nDifferential Revision:\thttps://reviews.freebsd.org/D12547","distinct":false,"url":"https://api.github.com/repos/bsd-hacker/freebsd/commits/67ff9a521615c6a7f55cf378a9eb964911c4b198"},{"sha":"6f98e3a079a33932eab42fb60ba4e281273f2026","author":{"name":"Jenkins CI","email":"61eb39d4445155efb6068840385577c11776cd20@jenkins-00.os-hackers.jp"},"message":"Merge branch 'master' into shigeru_work","distinct":true,"url":"https://api.github.com/repos/bsd-hacker/freebsd/commits/6f98e3a079a33932eab42fb60ba4e281273f2026"}]}
{"actor":{"display_login":"bsd-hacker"}}