From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, slade@sladewatkins.com
Subject: Re: [PATCH 5.10 000/131] 5.10.131-rc2 review
Date: Wed, 13 Jul 2022 15:17:40 -0700 [thread overview]
Message-ID: <20220713221740.GA69517@roeck-us.net> (raw)
In-Reply-To: <20220713094820.698453505@linuxfoundation.org>
On Wed, Jul 13, 2022 at 03:10:15PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.131 release.
> There are 131 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 15 Jul 2022 09:47:55 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 163 pass: 162 fail: 1
Failed builds:
um:defconfig
Qemu test results:
total: 477 pass: 469 fail: 8
Failed tests:
x86_64:q35:SandyBridge:defconfig:smp4:net,ne2k_pci:efi32:mem1G:usb:hd
x86_64:q35:Conroe:defconfig:smp4:net,tulip:efi32:mem256:scsi[DC395]:hd
x86_64:q35:Skylake-Server:defconfig:smp4:net,e1000-82544gc:efi32:mem2G:scsi[53C895A]:hd
x86_64:q35:Opteron_G5:defconfig:smp4:net,i82559c:efi32:mem256:scsi[MEGASAS2]:hd
x86_64:pc:Opteron_G2:defconfig:smp:net,usb:efi32:mem2G:scsi[virtio-pci]:hd
x86_64:q35:Nehalem:defconfig:smp2:net,i82558a:efi32:mem1G:virtio:hd
x86_64:q35:Skylake-Client-IBRS:defconfig:preempt:smp2:net,i82558b:efi32:mem1G:sdhci:mmc:hd
x86_64:q35:Haswell-noTSX-IBRS:defconfig:nosmp:net,pcnet:efi32:mem2G:ata:hd
Build error:
/opt/kernel/gcc-11.3.0-2.38-nolibc/x86_64-linux/bin/../lib/gcc/x86_64-linux/11.3.0/../../../../x86_64-linux/bin/ld: arch/x86/um/../kernel/module.o: in function `module_finalize':
arch/x86/um/../kernel/module.c:283: undefined reference to `apply_returns'
Crash:
[ 0.709966] kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
[ 0.709966] BUG: unable to handle page fault for address: 0000000021803b80
[ 0.709966] #PF: supervisor instruction fetch in kernel mode
[ 0.709966] #PF: error_code(0x0011) - permissions violation
[ 0.709966] PGD 175a063 P4D 175a063 PUD 175b063 PMD 1766063 PTE 8000000021803063
[ 0.709966] Oops: 0011 [#1] SMP PTI
[ 0.709966] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.131-rc2+ #1
[ 0.709966] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
[ 0.709966] RIP: 0010:0x21803b80
[ 0.709966] Code: Unable to access opcode bytes at RIP 0x21803b56.
[ 0.709966] RSP: 0018:ffffffffb9403e80 EFLAGS: 00000046
[ 0.709966] RAX: 0000000000000000 RBX: 0000000001798000 RCX: 00000000df24be60
[ 0.709966] RDX: 000000003feab058 RSI: 0000000000000600 RDI: 000000003fe7e038
[ 0.709966] RBP: 0000000000000600 R08: 0000000001798000 R09: 00000000229ed067
[ 0.709966] R10: 0000000000000000 R11: 00000000229ed067 R12: 0000000000000030
[ 0.709966] R13: 0000000000000001 R14: ffff9aca41790000 R15: 0000000000000282
[ 0.709966] FS: 0000000000000000(0000) GS:ffff9aca7f800000(0000) knlGS:0000000000000000
[ 0.709966] CS: 0010 DS: 0018 ES: 0018 CR0: 0000000080050033
[ 0.709966] CR2: 0000000021803b80 CR3: 0000000001758000 CR4: 00000000000406b0
[ 0.709966] Call Trace:
[ 0.709966] ? efi_set_virtual_address_map+0x87/0x160
[ 0.709966] ? efi_enter_virtual_mode+0x39a/0x3f5
[ 0.709966] ? start_kernel+0x4aa/0x544
[ 0.709966] ? secondary_startup_64_no_verify+0xc2/0xcb
[ 0.709966] Modules linked in:
[ 0.709966] CR2: 0000000021803b80
[ 0.709966] ---[ end trace 1b5f45b6ffd42130 ]---
[ 0.709966] RIP: 0010:0x21803b80
[ 0.709966] Code: Unable to access opcode bytes at RIP 0x21803b56.
[ 0.709966] RSP: 0018:ffffffffb9403e80 EFLAGS: 00000046
[ 0.709966] RAX: 0000000000000000 RBX: 0000000001798000 RCX: 00000000df24be60
[ 0.709966] RDX: 000000003feab058 RSI: 0000000000000600 RDI: 000000003fe7e038
[ 0.709966] RBP: 0000000000000600 R08: 0000000001798000 R09: 00000000229ed067
[ 0.709966] R10: 0000000000000000 R11: 00000000229ed067 R12: 0000000000000030
[ 0.709966] R13: 0000000000000001 R14: ffff9aca41790000 R15: 0000000000000282
[ 0.709966] FS: 0000000000000000(0000) GS:ffff9aca7f800000(0000) knlGS:0000000000000000
[ 0.709966] CS: 0010 DS: 0018 ES: 0018 CR0: 0000000080050033
[ 0.709966] CR2: 0000000021803b80 CR3: 0000000001758000 CR4: 00000000000406b0
[ 0.709966] Kernel panic - not syncing: Attempted to kill the idle task!
This is the same for all stable release candidates, and is also seen
in the mainline kernel.
Guenter
next prev parent reply other threads:[~2022-07-13 22:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 13:10 [PATCH 5.10 000/131] 5.10.131-rc2 review Greg Kroah-Hartman
2022-07-13 13:22 ` Guenter Roeck
2022-07-13 15:57 ` Sudip Mukherjee (Codethink)
2022-07-13 16:06 ` Guenter Roeck
2022-07-13 18:24 ` Florian Fainelli
2022-07-13 22:17 ` Guenter Roeck [this message]
2022-07-14 11:47 ` Naresh Kamboju
2022-07-15 0:53 ` Samuel Zou
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=20220713221740.GA69517@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=slade@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.