From: Catalin Marinas <catalin.marinas@arm.com>
To: Liam Howlett <liam.howlett@oracle.com>
Cc: Will Deacon <will@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Mark Brown <broonie@kernel.org>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] arm64: Change elfcore for_each_mte_vma() to use VMA iterator
Date: Wed, 23 Feb 2022 11:37:23 +0000 [thread overview]
Message-ID: <YhYcc+CGWuO0tUG+@arm.com> (raw)
In-Reply-To: <20220222185401.jntcd4g62pamfxvr@revolver>
On Tue, Feb 22, 2022 at 06:54:38PM +0000, Liam Howlett wrote:
> Once the maple tree is upstream, then you can take the patch I posted.
BTW, on the maple tree branch alone
(https://github.com/oracle/linux-uek.git maple/mainline), I get the
warning below and no core file generated. It's not MTE related as it
doesn't have my patches.
[ 67.887638] WARNING: CPU: 1 PID: 528 at fs/coredump.c:1116 dump_vma_snapshot+0x98/0x18c
[ 67.888594] Modules linked in: crct10dif_ce sm3_ce sm3_generic sha3_ce sha3_generic sha512_ce sha512_arm64 drm fuse ip_tables x_tables ipv6
[ 67.890017] CPU: 1 PID: 528 Comm: mte-coredump Not tainted 5.17.0-rc4-00071-gc8cf067d6a99 #1
[ 67.890494] Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015
[ 67.891054] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 67.891469] pc : dump_vma_snapshot+0x98/0x18c
[ 67.891787] lr : dump_vma_snapshot+0x74/0x18c
[ 67.892071] sp : ffff80000839b8f0
[ 67.892278] x29: ffff80000839b8f0 x28: ffffd4a81d76255c x27: 0000000000000000
[ 67.892894] x26: ffffd4a81da308e0 x25: 0000000000000000 x24: ffff80000839bc78
[ 67.893436] x23: ffff00000557cf00 x22: ffff00000557cf60 x21: ffff80000839b9e0
[ 67.893922] x20: ffff80000839b9e8 x19: ffff80000839b9dc x18: 0000000000000000
[ 67.894497] x17: 0000000000000000 x16: 0000ffff9e8effff x15: 0000000000000000
[ 67.895061] x14: 0000000000000000 x13: ffff0000025f9000 x12: ffff000001a2eb94
[ 67.895590] x11: ffff80000839b100 x10: ffff80000839b108 x9 : 0000000000000000
[ 67.896057] x8 : ffff80000839bb68 x7 : 0000000000000000 x6 : 0000000000896101
[ 67.896537] x5 : ffff0000016bf000 x4 : ffff80000839b8b0 x3 : 0000000000000001
[ 67.896961] x2 : 0000000000000000 x1 : 0000000000000001 x0 : 0000000000000011
[ 67.897493] Call trace:
[ 67.897679] dump_vma_snapshot+0x98/0x18c
[ 67.898034] elf_core_dump+0x50/0xcf0
[ 67.898274] do_coredump+0xbdc/0xfc4
[ 67.898553] get_signal+0x524/0x7f0
[ 67.898775] do_notify_resume+0x224/0x1330
[ 67.899046] el0_da+0x50/0x60
[ 67.899431] el0t_64_sync_handler+0xec/0x130
[ 67.899726] el0t_64_sync+0x1a0/0x1a4
--
Catalin
next prev parent reply other threads:[~2022-02-23 11:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 8:18 linux-next: build failure after merge of the maple tree Stephen Rothwell
2022-02-17 19:24 ` Will Deacon
2022-02-18 1:46 ` Liam Howlett
2022-02-18 2:37 ` [PATCH] arm64: Change elfcore for_each_mte_vma() to use VMA iterator Liam Howlett
2022-02-21 18:06 ` Catalin Marinas
2022-02-22 14:26 ` Liam Howlett
2022-02-22 16:20 ` Will Deacon
2022-02-22 17:26 ` Catalin Marinas
2022-02-22 18:54 ` Liam Howlett
2022-02-23 9:39 ` Catalin Marinas
2022-02-23 13:57 ` Liam Howlett
2022-02-23 11:37 ` Catalin Marinas [this message]
2022-02-23 14:11 ` Liam Howlett
2022-02-24 2:00 ` Liam Howlett
2022-02-25 15:50 ` Will Deacon
-- strict thread matches above, loose matches on Subject: below --
2022-02-23 2:32 linux-next: build failure after merge of the maple tree Liam Howlett
2022-02-23 12:47 ` [PATCH] arm64: Change elfcore for_each_mte_vma() to use VMA iterator kernel test robot
2022-02-23 13:08 ` kernel test robot
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=YhYcc+CGWuO0tUG+@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=will@kernel.org \
--cc=willy@infradead.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).