Re: [PATCH] Initialized initrd_ctx so we don't free a random pointer from the stack.

2014-09-21 Thread Vladimir 'φ-coder/phcoder' Serbinenko
On 21.09.2014 08:39, Andrei Borzenkov wrote: > В Wed, 17 Sep 2014 16:30:11 -0400 > Peter Jones пишет: > >> Currently, if "linux" fails, the "goto fail;" in grub_cmd_initrd sends us >> into grub_initrd_close() without grub_initrd_init() being called, and thus >> it never clears initrd_ctx->compone

Re: [PATCH] Initialized initrd_ctx so we don't free a random pointer from the stack.

2014-09-20 Thread Andrei Borzenkov
В Wed, 17 Sep 2014 16:30:11 -0400 Peter Jones пишет: > Currently, if "linux" fails, the "goto fail;" in grub_cmd_initrd sends us > into grub_initrd_close() without grub_initrd_init() being called, and thus > it never clears initrd_ctx->components. grub_initrd_close() then frees that > address, w

[PATCH] Initialized initrd_ctx so we don't free a random pointer from the stack.

2014-09-17 Thread Peter Jones
Currently, if "linux" fails, the "goto fail;" in grub_cmd_initrd sends us into grub_initrd_close() without grub_initrd_init() being called, and thus it never clears initrd_ctx->components. grub_initrd_close() then frees that address, which is stale data from the stack. If the stack happens to hav