From: Borislav Petkov <bp@alien8.de>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed
Date: Fri, 27 Jan 2017 10:09:15 +0100 [thread overview]
Message-ID: <20170127090915.zh7ct7cnvx2ds7qk@pd.tnic> (raw)
In-Reply-To: <7d07442a-c64e-797b-c8c4-ef453df30cde@virtuozzo.com>
On Fri, Jan 27, 2017 at 11:14:06AM +0300, Andrey Ryabinin wrote:
> Works for me as well.
> Tested-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
Thanks!
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-01-27 9:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 16:58 x86/microcode: use-after-free after cpu offline/online Andrey Ryabinin
2017-01-25 17:23 ` Borislav Petkov
2017-01-25 19:14 ` Andrey Ryabinin
2017-01-25 19:23 ` Borislav Petkov
2017-01-26 16:58 ` [PATCH] x86/microcode: Do not access the initrd after it has been freed Borislav Petkov
2017-01-27 8:14 ` Andrey Ryabinin
2017-01-27 9:09 ` Borislav Petkov [this message]
2017-01-30 8:46 ` Ingo Molnar
2017-01-30 9:35 ` Borislav Petkov
2017-01-31 7:43 ` Ingo Molnar
2017-01-31 10:01 ` Borislav Petkov
2017-01-31 11:31 ` Mike Galbraith
2017-01-31 12:31 ` Borislav Petkov
2017-01-31 17:49 ` Borislav Petkov
2017-01-31 18:05 ` Mike Galbraith
2017-01-31 18:03 ` Thomas Gleixner
2017-01-31 19:25 ` [tip:irq/urgent] x86/irq: Make irq activate operations symmetric tip-bot for Thomas Gleixner
2017-01-31 16:39 ` [PATCH] x86/microcode: Do not access the initrd after it has been freed Ingo Molnar
2017-01-30 8:49 ` [tip:x86/microcode] " tip-bot for Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170127090915.zh7ct7cnvx2ds7qk@pd.tnic \
--to=bp@alien8.de \
--cc=aryabinin@virtuozzo.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).