linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: linux-arm-kernel@lists.infradead.org,
	chenxiang via <qemu-devel@nongnu.org>,
	"linuxarm@huawei.com" <linuxarm@huawei.com>
Subject: Re: regression: insmod module failed in VM with nvdimm on #forregzbot
Date: Fri, 3 Mar 2023 10:42:42 +0100	[thread overview]
Message-ID: <632d4ca3-01ed-4d51-41b0-40c1aa82ffe9@leemhuis.info> (raw)
In-Reply-To: <b4b81dfd-d30c-e8f4-3ea3-1af9140a82bb@leemhuis.info>

[TLDR: This mail in primarily relevant for Linux regression tracking. A
change or fix related to the regression discussed in this thread was
posted or applied, but it did not use a Link: tag to point to the
report, as Linus and the documentation call for. Things happen, no
worries -- but now the regression tracking bot needs to be told manually
about the fix. See link in footer if these mails annoy you.]

On 30.11.22 11:10, Thorsten Leemhuis wrote:
>
> On 30.11.22 03:52, chenxiang (M) wrote:
>>
>> We boot the VM using following commands (with nvdimm on)  (qemu version
>> 6.1.50, kernel 6.0-r4):
>>
>> qemu-system-aarch64 -machine
>> virt,kernel_irqchip=on,gic-version=3,nvdimm=on  -kernel
>> /home/kernel/Image -initrd /home/mini-rootfs/rootfs.cpio.gz -bios
>> /root/QEMU_EFI.FD -cpu host -enable-kvm -net none -nographic -m
>> 2G,maxmem=64G,slots=3 -smp 4 -append 'rdinit=init console=ttyAMA0
>> ealycon=pl0ll,0x90000000 pcie_ports=native pciehp.pciehp_debug=1'
>> -object memory-backend-ram,id=ram1,size=10G -device
>> nvdimm,id=dimm1,memdev=ram1  -device ioh3420,id=root_port1,chassis=1
>> -device vfio-pci,host=7d:01.0,id=net0,bus=root_port1
>> [...]
>> We git bisect the code, and find the patch c5a89f75d2a ("arm64: kaslr:
>> defer initialization to initcall where permitted").
> 
> Thanks for the report. To be sure below issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
> tracking bot:
> 
> #regzbot ^introduced fc5a89f75d2a
> #regzbot title arm64: kaslr: vmalloc error when boothing a VM with nvdimm
> #regzbot ignore-activity

#regzbot fix: arm64: kaslr: don't pretend KASLR is enabled if offset <
MIN_KIMG_ALIGN
#regzbot ignore-activity

Backstory:

https://lore.kernel.org/lkml/CAMj1kXGWEaQXoKj=DzG9XpVGi4t5zfE-RSG0BodVL-b47nsj-A@mail.gmail.com/
https://lore.kernel.org/all/20230223204101.1500373-1-ardb@kernel.org/

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-03-03  9:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30  2:52 regression: insmod module failed in VM with nvdimm on chenxiang (M)
2022-11-30  7:53 ` Marc Zyngier
2022-11-30  8:18   ` Ard Biesheuvel
2022-12-01  7:15     ` chenxiang (M)
2022-12-01  8:07       ` Ard Biesheuvel
2022-12-01 11:07         ` Ard Biesheuvel
2022-12-01 12:06           ` chenxiang (M)
2022-12-01 12:53             ` Ard Biesheuvel
2022-12-02  2:48           ` chenxiang (M)
2022-12-02 13:44             ` Ard Biesheuvel
2022-12-15 17:33               ` Thorsten Leemhuis
2022-12-01  7:01   ` chenxiang (M)
2022-11-30 10:10 ` regression: insmod module failed in VM with nvdimm on #forregzbot Thorsten Leemhuis
2023-03-03  9:42   ` Linux regression tracking #update (Thorsten Leemhuis) [this message]

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=632d4ca3-01ed-4d51-41b0-40c1aa82ffe9@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linuxarm@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=regressions@lists.linux.dev \
    /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).