From: Gavin Shan <gshan@redhat.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
willy@infradead.org, david@redhat.com, vbabka@suse.cz,
osalvador@suse.de, gehao@kylinos.cn, shan.gavin@gmail.com
Subject: Re: [PATCH 0/2] Fix parameter passed to page_mapcount_is_type()
Date: Fri, 21 Mar 2025 15:34:55 +1000 [thread overview]
Message-ID: <141f7331-43fd-4bf4-88ca-36c18b02b133@redhat.com> (raw)
In-Reply-To: <20250321053148.1434076-1-gshan@redhat.com>
On 3/21/25 3:31 PM, Gavin Shan wrote:
> Found by code inspection. There are two places where the parameter
> passed to page_mapcount_is_type() is (page->__mapcount), which is
> correct since it should be one more than the value, as explained in
^^^^^^^
s/correct/incorrect
> the comments to page_mapcount_is_type(): (a) page_has_type() in
> page-flags.h (b) __dump_folio() in mm/debug.c
>
> PATCH[1] fixes the parameter for (a)
> PATCH[2] fixes the parameter for (b)
>
> Gavin Shan (2):
> mm: Fix parameter passed to page_mapcount_is_type()
> mm/debug: Fix parameter passed to page_mapcount_is_type()
>
> include/linux/page-flags.h | 2 +-
> mm/debug.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
next prev parent reply other threads:[~2025-03-21 5:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 5:31 Gavin Shan
2025-03-21 5:31 ` [PATCH 1/2] mm: " Gavin Shan
2025-03-21 10:13 ` David Hildenbrand
2025-03-21 11:26 ` Gavin Shan
2025-03-21 11:28 ` David Hildenbrand
2025-03-21 5:31 ` [PATCH 2/2] mm/debug: " Gavin Shan
2025-03-21 10:14 ` David Hildenbrand
2025-03-21 5:34 ` Gavin Shan [this message]
2025-03-21 9:23 ` [PATCH 0/2] " Vlastimil Babka
2025-03-21 10:11 ` David Hildenbrand
2025-03-21 11:25 ` Gavin Shan
2025-03-21 11:27 ` David Hildenbrand
2025-03-21 11:33 ` Vlastimil Babka
2025-03-21 12:07 ` Gavin Shan
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=141f7331-43fd-4bf4-88ca-36c18b02b133@redhat.com \
--to=gshan@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gehao@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=shan.gavin@gmail.com \
--cc=vbabka@suse.cz \
--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