From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Minchan Kim <minchan@kernel.org>
Subject: Re: linux-next: manual merge of the akpm-current tree with the slab tree
Date: Tue, 11 Jan 2022 22:51:01 +1100 [thread overview]
Message-ID: <20220111225101.114b655c@canb.auug.org.au> (raw)
In-Reply-To: <20211203182255.3800a09a@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2311 bytes --]
Hi all,
On Fri, 3 Dec 2021 18:22:55 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> mm/zsmalloc.c
>
> between commit:
>
> 5718b5cdd6e5 ("zsmalloc: Stop using slab fields in struct page")
>
> from the slab tree and commit:
>
> efcc1718fe08 ("zsmalloc: move huge compressed obj from page to zspage")
>
> from the akpm-current tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> diff --cc mm/zsmalloc.c
> index 0d3b65939016,7e03cc9363bb..000000000000
> --- a/mm/zsmalloc.c
> +++ b/mm/zsmalloc.c
> @@@ -824,10 -820,12 +820,12 @@@ static struct zspage *get_zspage(struc
>
> static struct page *get_next_page(struct page *page)
> {
> - if (unlikely(PageHugeObject(page)))
> + struct zspage *zspage = get_zspage(page);
> +
> + if (unlikely(ZsHugePage(zspage)))
> return NULL;
>
> - return page->freelist;
> + return (struct page *)page->index;
> }
>
> /**
> @@@ -900,8 -893,7 +893,7 @@@ static void reset_page(struct page *pag
> ClearPagePrivate(page);
> set_page_private(page, 0);
> page_mapcount_reset(page);
> - ClearPageHugeObject(page);
> - page->freelist = NULL;
> + page->index = 0;
> }
>
> static int trylock_zspage(struct zspage *zspage)
> @@@ -1042,9 -1039,9 +1039,9 @@@ static void create_page_chain(struct si
> SetPagePrivate(page);
> if (unlikely(class->objs_per_zspage == 1 &&
> class->pages_per_zspage == 1))
> - SetPageHugeObject(page);
> + SetZsHugePage(zspage);
> } else {
> - prev_page->freelist = page;
> + prev_page->index = (unsigned long)page;
> }
> prev_page = page;
> }
This is now a conflict between the akpm-current tree and Linus' tree -
that slab tree commit is now commit ffedd09fa9b0 ("zsmalloc: Stop using
slab fields in struct page") in Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-01-11 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 7:22 linux-next: manual merge of the akpm-current tree with the slab tree Stephen Rothwell
2022-01-11 11:51 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-03 7:19 Stephen Rothwell
2021-12-17 12:39 ` Stephen Rothwell
2021-12-21 0:10 ` 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=20220111225101.114b655c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=minchan@kernel.org \
--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