From: Matthew Wilcox <willy@infradead.org>
To: Yikebaer Aizezi <yikebaer61@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
David Howells <dhowells@redhat.com>
Subject: Re: WARNING in try_grab_page
Date: Fri, 4 Aug 2023 14:32:58 +0100 [thread overview]
Message-ID: <ZMz+CoJcCuh01Ie4@casper.infradead.org> (raw)
In-Reply-To: <ZMxzo0GzEkBGcxRu@casper.infradead.org>
On Fri, Aug 04, 2023 at 04:42:27AM +0100, Matthew Wilcox wrote:
> On Fri, Aug 04, 2023 at 11:14:45AM +0800, Yikebaer Aizezi wrote:
> > Just patched it, then I rerun the reproduce program, and I got this
> > output from console:
> >
> > BUG: Bad page state in process POC pfn:0eb8d
> > page:ffffea00003ae340 refcount:0 mapcount:0 mapping:0000000000000000
> > index:0x0 pfn:0xeb8d
> > flags: 0xfff00000001000(reserved|node=0|zone=1|lastcpupid=0x7ff)
> > page_type: 0xffffffff()
> > raw: 00fff00000001000 ffffea00003ae348 ffffea00003ae348 0000000000000000
> > raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
> > page dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set
> > page_owner info is not present (never set?)
> > Modules linked in:
> > CPU: 0 PID: 7959 Comm: POC Not tainted 6.5.0-rc2 #2
> > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
> > rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014
> > Call Trace:
> > <TASK>
> > __dump_stack lib/dump_stack.c:88 [inline]
> > dump_stack_lvl+0xd4/0xf0 lib/dump_stack.c:106
> > bad_page+0x71/0x1a0 mm/page_alloc.c:533
> > free_page_is_bad_report mm/page_alloc.c:974 [inline]
> > free_page_is_bad mm/page_alloc.c:984 [inline]
> > free_pages_prepare mm/page_alloc.c:1153 [inline]
> > free_unref_page_prepare+0x5f3/0xb50 mm/page_alloc.c:2348
> > free_unref_page+0x2f/0x3c0 mm/page_alloc.c:2443
> > __folio_put_small mm/swap.c:106 [inline]
> > __folio_put+0xa2/0x110 mm/swap.c:129
> > folio_put include/linux/mm.h:1423 [inline]
> > put_page include/linux/mm.h:1492 [inline]
> > extract_user_to_sg lib/scatterlist.c:1151 [inline]
>
> Ohh. I think this is something Dave Howells has a patch for.
Can you try
https://lore.kernel.org/mm-commits/20230726204730.B89D8C433C7@smtp.kernel.org/
?
next prev parent reply other threads:[~2023-08-04 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 8:56 Yikebaer Aizezi
2023-08-03 12:50 ` Matthew Wilcox
2023-08-03 13:19 ` Matthew Wilcox
2023-08-04 3:14 ` Yikebaer Aizezi
2023-08-04 3:42 ` Matthew Wilcox
2023-08-04 13:32 ` Matthew Wilcox [this message]
2023-08-04 13:35 ` David Howells
2023-08-06 7:51 ` Yikebaer Aizezi
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=ZMz+CoJcCuh01Ie4@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-mm@kvack.org \
--cc=yikebaer61@gmail.com \
/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