linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Peter Xu <peterx@redhat.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Hugh Dickins <hughd@google.com>,
	"Kirill A . Shutemov" <kirill@shutemov.name>,
	Randy Dunlap <rdunlap@infradead.org>,
	Mike Kravetz <mike.kravetz@oracle.com>,
	Yu Zhao <yuzhao@google.com>, Ryan Roberts <ryan.roberts@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Yang Shi <shy828301@gmail.com>
Subject: Re: [PATCH RFC v3] mm: Proper document tail pages fields for folio
Date: Wed, 16 Aug 2023 20:51:49 +0200	[thread overview]
Message-ID: <ae8ea59e-3081-072b-faa0-b67a5d5af047@redhat.com> (raw)
In-Reply-To: <ZN0YSOQmSR/voPVO@casper.infradead.org>

On 16.08.23 20:41, Matthew Wilcox wrote:
> On Wed, Aug 16, 2023 at 03:33:30PM +0200, David Hildenbrand wrote:
>> My simple tests passed so far. If there isn't something obvious missing,
>> I can do more testing and send this as an official patch.
> 
> I think you missed one:
> 
> +++ b/mm/swapfile.c
> @@ -1490,7 +1490,7 @@ int swp_swapcount(swp_entry_t entry)
> 
>          page = vmalloc_to_page(p->swap_map + offset);
>          offset &= ~PAGE_MASK;
> -       VM_BUG_ON(page_private(page) != SWP_CONTINUED);
> +       VM_BUG_ON(page_swap_entry(page).val != SWP_CONTINUED);

That falls under the "weird handling of SWP_CONTINUED using vmalloced 
pages". So different user of page_private().

Note that we don't even store swap entries in there but extended swap 
counts.

> 
>          do {
>                  page = list_next_entry(page, lru);
> 
> I'm not smart enough to understand the use of the one in
> add_swap_count_continuation().  Maybe that also needs to be fixed?

No, that's independent of THP_SWAP, we're not working on the memmap of 
the THP but some weird extension of swap counts.

Thanks for having a look!

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2023-08-16 18:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 21:25 Peter Xu
2023-08-16 13:33 ` David Hildenbrand
2023-08-16 16:53   ` Peter Xu
2023-08-16 18:59     ` David Hildenbrand
2023-08-16 18:41   ` Matthew Wilcox
2023-08-16 18:51     ` David Hildenbrand [this message]
2023-08-16 22:05       ` Matthew Wilcox
2023-08-18 14:38         ` David Hildenbrand

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=ae8ea59e-3081-072b-faa0-b67a5d5af047@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=peterx@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=ryan.roberts@arm.com \
    --cc=shy828301@gmail.com \
    --cc=willy@infradead.org \
    --cc=yuzhao@google.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