public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Juergen Gross <jgross@suse.com>
Cc: Borislav Petkov <bp@alien8.de>,
	Mike Galbraith <mgalbraith@suse.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [x86-tip] RSDP changes converted i4790 box SMP -> UP
Date: Mon, 15 Jan 2018 16:32:43 +0100	[thread overview]
Message-ID: <20180115153243.3wst57a2fqin2h37@gmail.com> (raw)
In-Reply-To: <b2a941a3-ff75-d57a-6dac-9a91fb0f4c31@suse.com>


* Juergen Gross <jgross@suse.com> wrote:

> On 15/01/18 15:56, Borislav Petkov wrote:
> > On Mon, Jan 15, 2018 at 03:52:25PM +0100, Juergen Gross wrote:
> >> Ingo, with my finding that above boot failure is related to a bug in
> >> openSUSE's grub2 (I've verified it soesn't exist in upstream grub2),
> > 
> > The box I'm seeing this on has SLES12-SP2 grub:
> > 
> > Version        : 2.02~beta2-115.9.1
> > 
> > Does it have the same bug?
> 
> The patch introducing this problem is from 2012. So I guess: yes.

I suspect this makes it a widespread, unintended ABI. Can we detect and somehow avoid it?

The boot protocol ABI sucks if it's fragile against such mistakes.

Thanks,

	Ingo

  reply	other threads:[~2018-01-15 15:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1515675936.7350.15.camel@suse.de>
     [not found] ` <20180111133723.d7x3sekanz5jhut2@gmail.com>
     [not found]   ` <1515682631.16805.3.camel@suse.de>
     [not found]     ` <20180111150331.7zzkd7awdxele54b@gmail.com>
     [not found]       ` <20180111151044.GC6176@hirez.programming.kicks-ass.net>
     [not found]         ` <1515694412.7054.10.camel@suse.de>
2018-01-12  4:25           ` [x86-tip] RSDP changes converted i4790 box SMP -> UP Mike Galbraith
2018-01-12  6:40             ` Juergen Gross
2018-01-12  8:01               ` Mike Galbraith
2018-01-12 11:17                 ` Juergen Gross
2018-01-12 13:00                   ` Mike Galbraith
2018-01-15 14:41                 ` Juergen Gross
2018-01-15 15:08                   ` Mike Galbraith
2018-01-12 12:23             ` Borislav Petkov
2018-01-12 13:11             ` Ingo Molnar
2018-01-15 14:52               ` Juergen Gross
2018-01-15 14:56                 ` Borislav Petkov
2018-01-15 15:18                   ` Juergen Gross
2018-01-15 15:32                     ` Ingo Molnar [this message]
2018-01-15 15:40                       ` Juergen Gross
2018-01-15 16:29                         ` Gabriel C
2018-01-15 16:42                           ` Juergen Gross
2018-01-15 16:56                             ` Gabriel C
2018-01-15 17:04                               ` Juergen Gross
2018-01-15 17:22                                 ` Gabriel C

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=20180115153243.3wst57a2fqin2h37@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgalbraith@suse.de \
    --cc=peterz@infradead.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