linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: vcaputo@pengaru.com
To: Arnd Bergmann <arnd@arndb.de>
Cc: Pavel Machek <pavel@ucw.cz>,
	Olivier Galibert <galibert@pobox.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	jikos@suse.cz
Subject: Re: Linux 4.15-rc7
Date: Fri, 12 Jan 2018 14:58:03 -0800	[thread overview]
Message-ID: <20180112225802.lok5rda3fudlm4cc@shells.gnugeneration.com> (raw)
In-Reply-To: <CAK8P3a3E7NZ+dA_MzBbw_EepoLwk+n6xXoZW=53v1kERQ4uNHg@mail.gmail.com>

On Fri, Jan 12, 2018 at 11:08:58PM +0100, Arnd Bergmann wrote:
> On Fri, Jan 12, 2018 at 11:04 PM,  <vcaputo@pengaru.com> wrote:
> > On Fri, Jan 12, 2018 at 09:11:38PM +0100, Arnd Bergmann wrote:
> >
> >> - I haven't found a definite answer on whether Netburst-based CPUs
> >>   are affected by meltdown at all. Some people claim it's affected,
> >>   others say it's not. If the code from https://github.com/IAIK/meltdown
> >>   is successful on your Celeron D, then we know it's affected, if not,
> >>   then you could decide to not care about KPTI (Spectre would still
> >>   be an issue).
> >>
> >
> > I tried that when the code was first made public, but libkdump doesn't
> > support 32-bit; it's full of 64-bit register use in the assembly bits.
> 
> Apparently 32-bit support was added on Wednesday, maybe you
> can try again with today's version.
> 

Thanks for informing me of this, I hadn't noticed.

I just tried it out, and confirmed the Celeron D is vulnerable to
meltdown.

Regards,
Vito Caputo

  reply	other threads:[~2018-01-12 22:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07 22:55 Linux 4.15-rc7 Linus Torvalds
2018-01-08  7:20 ` Thomas Gleixner
2018-01-10 23:32 ` Pavel Machek
2018-01-11 11:29   ` Olivier Galibert
2018-01-11 14:06     ` Nikolay Borisov
2018-01-12 11:06     ` Pavel Machek
2018-01-12 13:23       ` Arnd Bergmann
2018-01-12 14:43         ` Pavel Machek
2018-01-12 17:20         ` vcaputo
2018-01-12 20:11           ` Arnd Bergmann
2018-01-12 22:04             ` vcaputo
2018-01-12 22:08               ` Arnd Bergmann
2018-01-12 22:58                 ` vcaputo [this message]
2018-01-12 17:34         ` Linus Torvalds
2018-01-12 19:38           ` Pavel Machek
2018-01-12 19:44             ` Linus Torvalds
2018-01-12 20:41               ` Pavel Machek
2018-01-13 12:52               ` kernel page table isolation for x86-32 was " Pavel Machek
2018-01-11 14:07   ` Jiri Kosina
2018-01-19 10:28     ` Pavel Machek

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=20180112225802.lok5rda3fudlm4cc@shells.gnugeneration.com \
    --to=vcaputo@pengaru.com \
    --cc=arnd@arndb.de \
    --cc=galibert@pobox.com \
    --cc=jikos@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=torvalds@linux-foundation.org \
    /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).