public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Luiz Capitulino <luizcap@redhat.com>
To: Matthew Wilcox <willy@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vlastimil Babka <vbabka@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	David Hildenbrand <david@redhat.com>
Subject: Re: linux-next: manual merge of the slab tree with the mm-unstable tree
Date: Mon, 21 Jul 2025 17:35:42 -0400	[thread overview]
Message-ID: <954b5aa4-0dbd-445f-8859-320fb6a1186d@redhat.com> (raw)
In-Reply-To: <aH6XIUX4xyo2pZfY@casper.infradead.org>

On 2025-07-21 15:38, Matthew Wilcox wrote:
> On Mon, Jul 21, 2025 at 02:20:01PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> Today's linux-next merge of the slab tree got a conflict in:
>>
>>    fs/proc/page.c
>>
>> between commit:
>>
>>    a602ee331e31 ("fs: stable_page_flags(): use snapshot_page()")
>>
>> from the mm-unstable tree and commit:
>>
>>    d8178294c53e ("proc: Remove mention of PG_slab")
>>
>> from the slab tree.
>>
>> I fixed it up (I just used the former version) and can carry the fix as
>> necessary. This is now fixed as far as linux-next is concerned, but any
> 
> I think the snapshot_page commit was incorrect in removing this comment.
> It is still valuable information.  I think the comment from d8178294c53e
> should remain in the tree after the resolution.

The comment wasn't just dropped, David suggested a new version for the comment
(which is similar to yours). The new comment is now part of set_ps_flags()
which is where we set this flag in the snapshot_page() implementation:

static void set_ps_flags(struct page_snapshot *ps, const struct folio *folio,
                          const struct page *page)
{
         /*
          * Only the first page of a high-order buddy page has PageBuddy() set.
          * So we have to check manually whether this page is part of a high-
          * order buddy page.
          */
         if (PageBuddy(page))
                 ps->flags |= PAGE_SNAPSHOT_PG_BUDDY;
         else if (page_count(page) == 0 && is_free_buddy_page(page))
                 ps->flags |= PAGE_SNAPSHOT_PG_BUDDY;

         if (folio_test_idle(folio))
                 ps->flags |= PAGE_SNAPSHOT_PG_IDLE;
}


  reply	other threads:[~2025-07-21 21:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-21  4:20 linux-next: manual merge of the slab tree with the mm-unstable tree Stephen Rothwell
2025-07-21 19:38 ` Matthew Wilcox
2025-07-21 21:35   ` Luiz Capitulino [this message]
2025-07-22  8:30     ` Vlastimil Babka
  -- strict thread matches above, loose matches on Subject: below --
2025-09-04  6:20 Stephen Rothwell
2025-09-04  6:29 Stephen Rothwell
2025-09-04  8:39 ` Vlastimil Babka
2025-09-04 21:39   ` Andrew Morton
2025-11-14  4:13 Stephen Rothwell
2025-11-14  5:06 ` Christoph Hellwig
2025-11-14  8:46   ` Vlastimil Babka
2025-11-14  9:13     ` Thomas Weißschuh
2025-11-14 11:55       ` Christoph Hellwig
2025-11-20 13:31         ` Thomas Weißschuh
2025-11-20 17:51           ` Vlastimil Babka

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=954b5aa4-0dbd-445f-8859-320fb6a1186d@redhat.com \
    --to=luizcap@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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