mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Williamson <awilliam@redhat.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: linux-kernel@vger.kernel.org, jforbes@redhat.com, mcgrof@kernel.org
Subject: Re: Kernel crash while doing chroot'ed grub2-mkconfig on qemu-emulated Nehalem CPU since late November 6.13 snapshot
Date: Mon, 13 Jan 2025 23:55:43 -0800	[thread overview]
Message-ID: <ef28883a944ea30e75f596c43ea5a1034b670648.camel@redhat.com> (raw)
In-Reply-To: <9cb0bdfc94643fb1544671837b357bc49800ce3f.camel@redhat.com>

On Mon, 2025-01-13 at 11:16 -0800, Adam Williamson wrote:
> On Sun, 2025-01-12 at 10:47 -0800, Adam Williamson wrote:
> > > 
> > > I don't think that CPU flavour is important here. I'll greatly appreciate
> > > your testing.
> > 
> > Update - I tried doing a quick build yesterday but the patch doesn't
> > apply cleanly against our current Fedora Rawhide kernel. I'll look at
> > it again tomorrow. Sorry for the delay.
> 
> OK, I've got a test build working now. Looks like `struct execmem_area
> *area;` is not in Linus' current tree, I guess it's from your branch or
> something? Fortunately I just had to drop that line from the patch and
> it applies fine.

OK, so good news: initial testing of that patch (the
`get_vm_area_page_order(vm) + PAGE_SHIFT` one) looks good. I've run it
through 40 installs so far without a hang. Just as a sanity check, I
also ran the non-patched kernel through 10 installs on the same openQA
instance and it hung four times.

I'll run some more cycles tomorrow to be sure, but it looks good.
Thanks!
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net





  parent reply	other threads:[~2025-01-14  7:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 16:51 Adam Williamson
2025-01-02 20:16 ` Adam Williamson
2025-01-04  1:51   ` Luis Chamberlain
2025-01-04  2:57     ` Adam Williamson
2025-01-06  7:09     ` Adam Williamson
2025-01-10  9:57   ` Mike Rapoport
2025-01-10 17:28     ` Adam Williamson
2025-01-11  8:50       ` Mike Rapoport
     [not found]         ` <358da653bcd8b7875f59e673e5572bddd3677aea.camel@redhat.com>
     [not found]           ` <9cb0bdfc94643fb1544671837b357bc49800ce3f.camel@redhat.com>
2025-01-14  7:55             ` Adam Williamson [this message]
2025-01-14  8:08               ` Adam Williamson

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=ef28883a944ea30e75f596c43ea5a1034b670648.camel@redhat.com \
    --to=awilliam@redhat.com \
    --cc=jforbes@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=rppt@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

all inboxes | Powered by JetHome®