From: Mike Galbraith <efault@gmx.de>
To: Will Deacon <will@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
lstoakes@gmail.com, wangkefeng.wang@huawei.com,
catalin.marinas@arm.com, ardb@kernel.org
Subject: Re: arm64: perf test 26 rpi4 oops
Date: Mon, 31 Jul 2023 13:37:04 +0200 [thread overview]
Message-ID: <b26b34cf503ad570a3b40c72f312482921d7104f.camel@gmx.de> (raw)
In-Reply-To: <20230731104340.GA24767@willie-the-truck>
On Mon, 2023-07-31 at 11:43 +0100, Will Deacon wrote:
> The easiest way to trigger the problem is simply:
>
> # objdump -d /proc/kcore
>
> Looking at the history, I wonder whether this is because of a combination
> of:
>
> e025ab842ec3 ("mm: remove kern_addr_valid() completely")
>
> which removed the kern_addr_valid() check on the basis that kcore used
> copy_from_kernel_nofault() anyway, and:
>
> 2e1c0170771e ("fs/proc/kcore: avoid bounce buffer for ktext data")
>
> which replaced the copy_from_kernel_nofault() with _copy_to_user().
>
> So with both of those applied, we're missing the address check on arm64.
Hm, I see trace_printk() in the future of self and x86_64 desktop box.
While my attempt to bisect the two arm64 allocation failures was doomed
by an apparent inability to reliably type sudo perf test 26, I still
suspect they might be a part of this fossilized bug.. see last two with
funny looking addr/len.
dmesg|tail -2
[ 1506.732999] __vm_enough_memory: pid: 3824, comm: objdump, not enough memory for the allocation of 64913409 pages
[ 1506.733050] __vm_enough_memory: pid: 3824, comm: objdump, not enough memory for the allocation of 64913441 pages
cat trace|grep 3824
...
objdump-3824 [000] ....... 1506.708497: vm_unmapped_area: addr=0x7fa9ac8000 err=0 total_vm=0x52f flags=0x1 len=0x2e7000 lo=0x1000 hi=0x7faa24e000 mask=0x0 ofs=0x0
objdump-3824 [000] ....... 1506.708657: vm_unmapped_area: addr=0x7faa213000 err=0 total_vm=0x816 flags=0x1 len=0x7000 lo=0x1000 hi=0x7faa24e000 mask=0x0 ofs=0x0
objdump-3824 [000] ....... 1506.709740: vm_unmapped_area: addr=0x7fa86f7000 err=0 total_vm=0x81d flags=0x1 len=0x13d1000 lo=0x1000 hi=0x7faa24e000 mask=0x0 ofs=0x0
objdump-3824 [000] ....... 1506.732991: vm_unmapped_area: addr=0x17995df000 err=0 total_vm=0x831 flags=0x1 len=0x3de8001000 lo=0x1000 hi=0x7faa24e000 mask=0x0 ofs=0x0
objdump-3824 [000] ....... 1506.733049: vm_unmapped_area: addr=0x17995bf000 err=0 total_vm=0x831 flags=0x1 len=0x3de8021000 lo=0x1000 hi=0x7faa24e000 mask=0x0 ofs=0x0
objdump-3824 [000] ....... 1506.733846: exit_mmap: mt_mod ffffff8149991980, DESTROY
next prev parent reply other threads:[~2023-07-31 11:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 4:06 Mike Galbraith
2023-07-28 14:18 ` Will Deacon
2023-07-28 15:12 ` Mike Galbraith
2023-07-28 15:23 ` Will Deacon
2023-07-28 16:35 ` Mike Galbraith
2023-07-29 16:30 ` Mike Galbraith
2023-07-30 5:54 ` Mike Galbraith
2023-07-30 11:01 ` Mike Galbraith
2023-07-30 16:09 ` Mike Galbraith
2023-07-31 10:43 ` Will Deacon
2023-07-31 11:37 ` Mike Galbraith [this message]
2023-07-31 11:52 ` Will Deacon
2023-07-31 16:07 ` Mike Galbraith
2023-07-31 21:08 ` Lorenzo Stoakes
2023-07-31 21:54 ` Lorenzo Stoakes
2023-07-31 23:27 ` Mike Galbraith
2023-07-31 23:48 ` Mike Galbraith
2023-08-01 0:33 ` Mike Galbraith
2023-08-01 4:34 ` Mike Galbraith
2023-08-01 7:27 ` Will Deacon
2023-08-01 8:39 ` Mike Galbraith
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=b26b34cf503ad570a3b40c72f312482921d7104f.camel@gmx.de \
--to=efault@gmx.de \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lstoakes@gmail.com \
--cc=mark.rutland@arm.com \
--cc=wangkefeng.wang@huawei.com \
--cc=will@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®