linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Thomas Gleixner <tglx@linutronix.de>, Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	DaveYoung <dyoung@redhat.com>, Baoquan He <bhe@redhat.com>,
	kexec@lists.infradead.org, x86@kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] x86/crash: fix crash_setup_memmap_entries() out-of-bounds access
Date: Sat, 17 Apr 2021 02:05:27 +0200	[thread overview]
Message-ID: <d725b19b4c02273eaab38a10853fa6fb6d5bc76c.camel@gmx.de> (raw)
In-Reply-To: <87sg3puco5.ffs@nanos.tec.linutronix.de>

On Fri, 2021-04-16 at 23:44 +0200, Thomas Gleixner wrote:
>
> Can all of you involved stop this sandpit fight and do something useful
> to fix that obvious bug already?

?? We're not fighting afaik.  Boris hated my changelog enough to offer
to write a better one, and I'm fine with that.  It's a seven year old
*latent* buglet of microscopic proportions, hardly a pressing issue.

	-Mike


  reply	other threads:[~2021-04-17  0:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15 17:56 x86/crash: fix crash_setup_memmap_entries() out-of-bounds access Mike Galbraith
2021-04-16 11:07 ` Dave Young
2021-04-16 11:28   ` Mike Galbraith
2021-04-16 11:47     ` Dave Young
2021-04-16 12:02       ` [patch] " Mike Galbraith
2021-04-16 12:16         ` Borislav Petkov
2021-04-16 13:16           ` Mike Galbraith
2021-04-16 14:44             ` Borislav Petkov
2021-04-16 15:13               ` Mike Galbraith
2021-04-16 21:44                 ` Thomas Gleixner
2021-04-17  0:05                   ` Mike Galbraith [this message]
2021-04-19  8:52                     ` Borislav Petkov
2021-04-19  9:37                       ` DaveYoung
2021-04-20 18:00         ` [tip: x86/urgent] x86/crash: Fix " tip-bot2 for Mike Galbraith

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=d725b19b4c02273eaab38a10853fa6fb6d5bc76c.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=bp@alien8.de \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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).