public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Yang Shi <yang@os.amperecomputing.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the mm-hotfixes tree
Date: Wed, 3 Jul 2024 09:22:33 +1000	[thread overview]
Message-ID: <20240703092233.44f51416@canb.auug.org.au> (raw)
In-Reply-To: <20240703084440.3af9f526@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 3411 bytes --]

Hi Andrew,

On Wed, 3 Jul 2024 08:44:40 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Mon, 1 Jul 2024 11:15:17 -0700 Yang Shi <yang@os.amperecomputing.com> wrote:
> >
> > On 6/30/24 6:01 PM, Stephen Rothwell wrote:  
> > >
> > > On Mon, 1 Jul 2024 10:16:41 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:    
> > >> After merging the mm-hotfixes tree, today's linux-next build (powerpc
> > >> ppc64_defconfig) failed like this:
> > >>
> > >> mm/gup.c: In function 'gup_hugepte':
> > >> mm/gup.c:474:25: error: implicit declaration of function 'try_grab_folio_fast'; did you mean 'try_grab_folio'? [-Werror=implicit-function-declaration]
> > >>    474 |                 folio = try_grab_folio_fast(page, refs, flags);
> > >>        |                         ^~~~~~~~~~~~~~~~~~~
> > >>        |                         try_grab_folio
> > >> mm/gup.c:474:23: warning: assignment to 'struct folio *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
> > >>    474 |                 folio = try_grab_folio_fast(page, refs, flags);
> > >>        |                       ^
> > >> mm/gup.c: At top level:
> > >> mm/gup.c:2747:22: error: conflicting types for 'try_grab_folio_fast'; have 'struct folio *(struct page *, int,  unsigned int)'
> > >>   2747 | static struct folio *try_grab_folio_fast(struct page *page, int refs,
> > >>        |                      ^~~~~~~~~~~~~~~~~~~
> > >> mm/gup.c:474:25: note: previous implicit declaration of 'try_grab_folio_fast' with type 'int()'
> > >>    474 |                 folio = try_grab_folio_fast(page, refs, flags);
> > >>        |                         ^~~~~~~~~~~~~~~~~~~
> > >> cc1: some warnings being treated as errors
> > >>
> > >> Caused by commit
> > >>
> > >>    5f408bfe0d13 ("mm: gup: stop abusing try_grab_folio")
> > >>
> > >> I have reverted that commit for today.    
> > > And I also had to revert commit
> > >
> > >    52cca85b0ebf ("mm-gup-introduce-memfd_pin_folios-for-pinning-memfd-folios-fix")
> > >
> > > from the mm-unstable branch of the mm tree.    
> > 
> > The patch attached in this mail should fix the compile error.
> > 
> > https://lore.kernel.org/linux-mm/CAHbLzkowMSso-4Nufc9hcMehQsK9PNz3OSu-+eniU-2Mm-xjhA@mail.gmail.com/  
> 
> It looks like that patch has been applied to the mm tree instead of the
> mm-hotfixes tree - as a fix for commit
> 
>   50ceb37037f3 ("mm: gup: stop abusing try_grab_folio")

So for today, I have applied the following patch to the mm-hotfixes
tree merge and stopped reverting
mm-gup-introduce-memfd_pin_folios-for-pinning-memfd-folios-fix.

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed, 3 Jul 2024 08:52:20 +1000
Subject: [PATCH] fixup for "mm: gup: stop abusing try_grab_folio"

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 mm/gup.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/mm/gup.c b/mm/gup.c
index 12c7b41712f7..5f58c95b3ab9 100644
--- a/mm/gup.c
+++ b/mm/gup.c
@@ -437,6 +437,9 @@ static unsigned long hugepte_addr_end(unsigned long addr, unsigned long end,
 	return (__boundary - 1 < end - 1) ? __boundary : end;
 }
 
+static struct folio *try_grab_folio_fast(struct page *page, int refs,
+					 unsigned int flags);
+
 /*
  * Returns 1 if succeeded, 0 if failed, -EMLINK if unshare needed.
  *
-- 
2.45.2

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-07-02 23:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01  0:16 linux-next: build failure after merge of the mm-hotfixes tree Stephen Rothwell
2024-07-01  1:01 ` Stephen Rothwell
2024-07-01 18:15   ` Yang Shi
2024-07-02 22:44     ` Stephen Rothwell
2024-07-02 23:22       ` Stephen Rothwell [this message]
2024-07-03  0:40         ` Yang Shi
  -- strict thread matches above, loose matches on Subject: below --
2025-12-07 21:35 Stephen Rothwell
2025-12-08 10:30 ` Maciej Wieczor-Retman
2025-12-09  1:37   ` Andrew Morton
2025-08-21  6:05 Stephen Rothwell
2025-08-21  9:49 ` Harry Yoo
2025-05-28 23:59 Stephen Rothwell
2025-05-29  0:02 ` Andrew Morton
2025-05-29  1:57   ` Stephen Rothwell
2025-05-29  0:03 ` Stephen Rothwell
2023-12-13 22:18 Stephen Rothwell
2023-12-13 23:31 ` Liam R. Howlett
2022-12-12 22:30 Stephen Rothwell
2022-12-13  1:34 ` Kefeng Wang
2022-12-13  2:23   ` Andrew Morton
2022-12-13  2:45     ` Stephen Rothwell
2022-12-13  2:54     ` Kefeng Wang
2022-11-25  1:10 Stephen Rothwell
2022-11-25  5:24 ` Juergen Gross
2022-11-25  5:24 ` Andrew Morton
2022-11-25  5:48   ` Stephen Rothwell

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=20240703092233.44f51416@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=yang@os.amperecomputing.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