From: David Hildenbrand <david@redhat.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
willy@infradead.org, Kefeng Wang <wangkefeng.wang@huawei.com>,
Barry Song <baohua@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Dan Carpenter <dan.carpenter@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: LTP: fork13: kernel panic on rk3399-rock-pi-4 running mainline 6.10.rc3
Date: Tue, 11 Jun 2024 12:32:44 +0200 [thread overview]
Message-ID: <e8c10a52-61f9-4b46-bc50-e2c267b1aa56@redhat.com> (raw)
In-Reply-To: <CA+G9fYvKmr84WzTArmfaypKM9+=Aw0uXCtuUKHQKFCNMGJyOgQ@mail.gmail.com>
On 11.06.24 12:14, Naresh Kamboju wrote:
> The kernel panic was noticed while running LTP syscalls fork13 (long running) on
> the mainline master 6.10.rc3 kernel on arm64 rk3399-rock-pi-4 device.
>
> Please find detailed logs in the links,
>
> As you know fork13 is a stress test case trying to generate a maximum number
> of PID's in a 100,000 loop.
>
> This device is running via NFS mounted filesystem.
>
> I have tried to reproduce this problem in a loop but failed to reproduce the
> crash.
>
>
> Crash flow:
> ------
> fork13 run started
> BUG: Bad page map in process fork13
> BUG: Bad rss-counter state mm:
> Unable to handle kernel paging request at virtual address
> Internal error: Oops: 0000000096000046
> run for 800 secs ( 13 minutes) and more.
> fork14 run started and completed
>
> fpathconf01 run started and completed
> sugov:
>
> Unable to handle kernel NULL pointer dereference at virtual address
>
> Insufficient stack space to handle exception!
> end Kernel panic - not syncing: kernel stack overflow
>
> I have tried to decode stack dump by not being useful [1].
> [1] https://people.linaro.org/~naresh.kamboju/output-rk3399.txt
>
> Test log :
> --------
> tst_test.c:1733: TINFO: LTP version: 20240524
> tst_test.c:1617: TINFO: Timeout per run is 0h 15m 00s
> [ 904.280569] BUG: Bad page map in process fork13 pte:2000000019ffc3
> pmd:80000000df55003
> [ 904.281397] page: refcount:1 mapcount:-1 mapping:0000000000000000
> index:0x0 pfn:0x19f
Mapcount underflow on a small folio (head: not printed).
[...]
> [ 904.294564] BUG: Bad page map in process fork13 pte:200000002e4fc3
> pmd:80000000df55003
> [ 904.295275] page: refcount:2 mapcount:-1 mapping:000000007885152f
> index:0x6 pfn:0x2e4
Another mapcount underflow on a small folio (head: not printed).
> [ 904.309309] BUG: Bad page map in process fork13 pte:20000000cc6fc3
> pmd:80000000df55003
> [ 904.310031] page: refcount:1 mapcount:-1 mapping:0000000000000000
> index:0x6 pfn:0xcc6
> [ 904.310728] head: order:3 mapcount:-1 entire_mapcount:0
> nr_pages_mapped:8388607 pincount:0
Mapcount underflow on a large folio.
...
> [ 904.326666] BUG: Bad page map in process fork13 pte:20000000268fc3
> pmd:80000000df55003
> [ 904.327390] page: refcount:1 mapcount:-1 mapping:00000000f0624181
> index:0x1b pfn:0x268
Another mapcount underflow on a small folio (head: not printed).
> [ 904.328094] memcg:ffff0000016b4000
> [ 904.328401] aops:nfs_file_aops ino:8526e6 dentry
> name:"libgpg-error.so.0.36.0"
> [ 904.329051] flags:
> 0x3fffe000000002c(referenced|uptodate|lru|node=0|zone=0|lastcpupid=0x1ffff)
> [ 904.329878] raw: 03fffe000000002c fffffdffc0009a48 fffffdffc022f3c8
> ffff00000688bd60
> [ 904.330561] raw: 000000000000001b 0000000000000000 00000001fffffffe
> ffff0000016b4000
> [ 904.331240] page dumped because: bad pte
> [ 904.331590] addr:0000aaaad9afe000 vm_flags:00000075
> anon_vma:0000000000000000 mapping:ffff0000300d4188 index:2e
> [ 904.332476] file:fork13 fault:filemap_fault mmap:nfs_file_mmap
> read_folio:nfs_read_folio
> [ 904.333245] CPU: 5 PID: 22685 Comm: fork13 Tainted: G B
Are these maybe side-effects due to
https://lkml.kernel.org/r/20240607103241.1298388-1-wangkefeng.wang@huawei.com
How reproducible is this?
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-06-11 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 10:14 Naresh Kamboju
2024-06-11 10:32 ` David Hildenbrand [this message]
2024-06-11 11:39 ` Baolin Wang
2024-06-11 12:09 ` David Hildenbrand
2024-06-12 1:40 ` Baolin Wang
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=e8c10a52-61f9-4b46-bc50-e2c267b1aa56@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=rmk+kernel@armlinux.org.uk \
--cc=ryan.roberts@arm.com \
--cc=wangkefeng.wang@huawei.com \
--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