There have been some cases where external tooling (e.g., kpatch-build)
creates a corrupt relocation which targets the wrong address. This is a
silent failure which can corrupt memory in unexpected places.
On x86, the bytes of data being overwritten by relocations are always
initialized to zero be
+++ Josh Poimboeuf [02/11/17 21:19 -0500]:
On Thu, Nov 02, 2017 at 04:57:11PM -0500, Josh Poimboeuf wrote:
There have been some cases where external tooling (e.g., kpatch-build)
creates a corrupt relocation which targets the wrong address. This is a
silent failure which can corrupt memory in un
On Thu, Nov 02, 2017 at 04:57:11PM -0500, Josh Poimboeuf wrote:
> There have been some cases where external tooling (e.g., kpatch-build)
> creates a corrupt relocation which targets the wrong address. This is a
> silent failure which can corrupt memory in unexpected places.
>
> On x86, the bytes
There have been some cases where external tooling (e.g., kpatch-build)
creates a corrupt relocation which targets the wrong address. This is a
silent failure which can corrupt memory in unexpected places.
On x86, the bytes of data being overwritten by relocations are always
initialized to zero be
4 matches
Mail list logo