From: Finn Thain <fthain@telegraphics.com.au>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Mike Rapoport <rppt@kernel.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Stan Johnson <userm57@yahoo.com>,
Angelo Dureghello <angelo@kernel-space.org>
Subject: Re: v5.11 (CONFIG_FLATMEM) boot crash
Date: Fri, 26 Mar 2021 14:12:41 +1100 (AEDT) [thread overview]
Message-ID: <5a8b344-dbf-58a0-ac3-ebfe47a69c@telegraphics.com.au> (raw)
In-Reply-To: <CAMuHMdX+t1_GQuL_EDPa4YdXNZiCVwsNf8tGs9NdosERSpJA1Q@mail.gmail.com>
On Thu, 25 Mar 2021, Geert Uytterhoeven wrote:
> On Thu, Mar 25, 2021 at 10:46 AM Mike Rapoport <rppt@kernel.org> wrote:
> >
> > There was a bug in the definition of ARCH_PFN_OFFSET that's quite
> > probably causes the crashes when the kernel is located in the second
> > memory bank.
> >
> > The fix was posted a while ago:
> >
> > https://lore.kernel.org/linux-m68k/20210228190828.392974-1-angelo@kernel-space.org
> >
> > Can you check if this helps?
>
> Thank you!
>
> I hadn't realized this applies to classic m68k, too.
> One more reason to annotate #else and #endif keywords, to avoid
> people guessing wrong...
>
> Greg: This is in linux-next, and still destined for v5.12, I assume?
> Thanks!
>
That message seems to have omitted 'Cc: stable@vger.kernel.org' and the
commit in linux-next seems to lack a 'Fixes' tag:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/m68k?id=06c5fa9b2168fcf185ca6807982bb97b72c0cfdb
It may be worthwhile to add the missing tag before pushing.
next prev parent reply other threads:[~2021-03-26 3:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 3:03 v5.11 (CONFIG_FLATMEM) boot crash Finn Thain
2021-03-25 9:45 ` Mike Rapoport
2021-03-25 9:56 ` Geert Uytterhoeven
2021-03-26 3:12 ` Finn Thain [this message]
[not found] ` <c1fbde1b-0f2a-bda0-7bb3-44156031bf41@yahoo.com>
2021-03-26 2:40 ` Finn Thain
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=5a8b344-dbf-58a0-ac3-ebfe47a69c@telegraphics.com.au \
--to=fthain@telegraphics.com.au \
--cc=angelo@kernel-space.org \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=rppt@kernel.org \
--cc=userm57@yahoo.com \
/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