linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "max.schulze@online.de" <max.schulze@online.de>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
	naush@raspberrypi.com, linux-mm@kvack.org,
	akpm@linux-foundation.org
Subject: Aw: Re: BUG: Bad page map in process/Bad Swap file entry, RPI CM4 on clone syscall
Date: Fri, 26 Aug 2022 10:39:31 +0200	[thread overview]
Message-ID: <trinity-32397ec8-0094-4aa9-ba8e-68ccb0874b7d-1661503171831@3c-app-1and1-bs05> (raw)
In-Reply-To: <20220824153045.GA18443@willie-the-truck>

> 
> 
> I think the issue is much more fundamental than that; you appear to have
> page-table corruption (for example, "pte:262d2626292a2627" and
> "pte:1110111111111111" are definitely corrupted) and so anything dealing
> with 'struct page' derived from the physical address in the pte is going to
> go wonky.
> 
>  From the logs here, the pmds look ok but these are the pte values I 
> spotted:
> 
> 0x1110111111111111
> 0x262d2626292a2627
> 0xa098a09aa29ea8a4
> 0x212725231f242323
> 0x2626262023222323
> 
> which don't seem to correspond to any sort of poison, but are possibly
> artifacts of repeated patterns with random bits cleared?
> 
> Will


Very valuable thought. I am streaming camera data, and generally the image captured from my desk is very dark (so these might be 8-bit brightness values from a mono ov9281 sensor).

I then set the camera to generate a test pattern, i.e. it will only produce output  like this

00000090: ffff ffff ffff ffff ffff 00ff 00ff 00ff
000000a0: 00ff 00ff 00ff 00ff 00ff 00ff 00ff 00ff

( also ff00 and 0000 ).

And those were the crashes that followed:

[   54.838582] BUG: Bad page map in process pool-upowerd  pte:ff00ffffffffff pmd:800000001801003
[   54.839187] BUG: Bad page map in process pool-upowerd  pte:ff00ff00ff00ff pmd:800000001801003
[   54.839615] BUG: Bad page map in process pool-upowerd  pte:ff00ff00ff00ff pmd:800000001801003
[   54.845439] BUG: Bad page map in process pool-upowerd  pte:ff00ff00ff00ff pmd:800000001801003

[   49.664066] BUG: Bad page map in process gmain  pte:ff00ffffffffff pmd:800000001801003
[   49.664515] BUG: Bad page map in process gmain  pte:ff00ff00ff00ff pmd:800000001801003
[   49.664879] BUG: Bad page map in process gmain  pte:ff00ff00ff00ff pmd:800000001801003
[   49.665245] BUG: Bad page map in process gmain  pte:ff00ff00ff00ff pmd:800000001801003
[   49.665610] BUG: Bad page map in process gmain  pte:ff00ff00ff00ff pmd:800000001801003
[   49.665973] BUG: Bad page map in process gmain  pte:ff00ff00ff00ff pmd:800000001801003
[   49.666336] BUG: Bad page map in process gmain  pte:ff00ff00ff00ff pmd:800000001801003
[   49.666698] BUG: Bad page map in process gmain  pte:ff00ff00ff00ff pmd:800000001801003
[   49.667061] BUG: Bad page map in process gmain  pte:ff00ff00ff00ff pmd:800000001801003

That confirms my suspicion of a dma write-out-of-bounds from a very separate angle (thanks again for the valuable idea).
I have since taken this to https://github.com/raspberrypi/linux/issues/5138 but will update the list once investigation has found a solution.

Thanks,
Max


      reply	other threads:[~2022-08-26  8:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d5f3cea4-20e6-f401-f3e7-8cb2f26033dc@online.de>
     [not found] ` <20220815142213.GA10448@willie-the-truck>
     [not found]   ` <ef144edd-facb-b49e-4482-74f4b42b1ad1@online.de>
2022-08-18 17:14     ` Max Schulze
2022-08-24 15:30       ` Will Deacon
2022-08-26  8:39         ` max.schulze [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=trinity-32397ec8-0094-4aa9-ba8e-68ccb0874b7d-1661503171831@3c-app-1and1-bs05 \
    --to=max.schulze@online.de \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=naush@raspberrypi.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