From: Yu Zhao <yuzhao@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>
Cc: Linux-MM <linux-mm@kvack.org>
Subject: mm-everything-2022-06-09-20-57: locked page at free
Date: Sat, 11 Jun 2022 14:59:41 -0600 [thread overview]
Message-ID: <CAOUHufZnj7ZWYvdcRq7Vi_te1wRd=U7E9NmgyQfabsvzm-Z77Q@mail.gmail.com> (raw)
BUG: Bad page state in process cros_configfs pfn:109fb1
page:fffffffe0227ec40 refcount:0 mapcount:0 mapping:0000000000000000
index:0x0 pfn:0x109fb1
flags: 0xb980000000000001(locked|zone=2|kasantag=0xe6)
raw: b980000000000001 dead000000000100 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set
Modules linked in:
CPU: 7 PID: 210 Comm: cros_configfs Tainted: G W
5.19.0-rc1-lockdep+ #3
Call trace:
dump_backtrace+0x1a0/0x200
show_stack+0x24/0x30
dump_stack_lvl+0x7c/0xa0
dump_stack+0x18/0x44
bad_page+0x190/0x194
check_free_page_bad+0x38/0x48
free_pcp_prepare+0x230/0x404
free_unref_page_prepare+0x2c/0xc8
free_unref_page+0x74/0x1a8
__put_page+0x70/0x90
filemap_free_folio+0xe0/0x12c
filemap_remove_folio+0xec/0x118
read_pages+0x150/0x20c
page_cache_ra_unbounded+0x228/0x2a0
do_page_cache_ra+0x6c/0x78
page_cache_ra_order+0x238/0x25c
ondemand_readahead+0x3f0/0x570
page_cache_sync_ra+0xc0/0xd4
filemap_get_pages+0x194/0x468
filemap_read+0x1a0/0x4e0
generic_file_read_iter+0x74/0x1ec
vfs_read+0x388/0x484
ksys_read+0xb4/0x134
__arm64_sys_read+0x48/0x54
el0_svc_common+0xfc/0x1cc
do_el0_svc_compat+0x38/0x5c
el0_svc_compat+0x68/0xf4
el0t_32_sync_handler+0xc0/0xf0
el0t_32_sync+0x190/0x194
next reply other threads:[~2022-06-11 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 20:59 Yu Zhao [this message]
2022-06-11 21:21 ` Matthew Wilcox
2022-06-11 21:31 ` Yu Zhao
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='CAOUHufZnj7ZWYvdcRq7Vi_te1wRd=U7E9NmgyQfabsvzm-Z77Q@mail.gmail.com' \
--to=yuzhao@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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