public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Jianhui Zhou <jianhuizzzzz@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
	aarcange@redhat.com, akpm@linux-foundation.org, david@kernel.org,
	jonaszhou@zhaoxin.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, mike.kravetz@oracle.com,
	muchun.song@linux.dev, osalvador@suse.de, peterx@redhat.com,
	rppt@kernel.org, stable@vger.kernel.org,
	syzbot+f525fd79634858f478e7@syzkaller.appspotmail.com
Subject: Re: [PATCH] mm/userfaultfd: fix hugetlb fault mutex hash calculation
Date: Sun,  8 Mar 2026 15:57:27 -0700	[thread overview]
Message-ID: <20260308225727.77058-1-sj@kernel.org> (raw)
In-Reply-To: <20260308134152.6877-1-jianhuizzzzz@gmail.com>

On Sun,  8 Mar 2026 21:41:51 +0800 Jianhui Zhou <jianhuizzzzz@gmail.com> wrote:

> On Fri, Mar 07, 2026 at 03:27:00AM +0000, SeongJae Park wrote:
> > I just found this patch makes UML build fails as below.
> >
> >     ../include/linux/hugetlb.h:1214:16: error: implicit declaration of
> >     function 'linear_page_index' [-Wimplicit-function-declaration]
> 
> Thanks for catching this! As Peter pointed out, the
> !CONFIG_HUGETLB_PAGE stub is actually unnecessary since
> mfill_atomic_hugetlb() is only compiled when CONFIG_HUGETLB_PAGE is
> enabled. I have removed it in v2, which also fixes this build error.

Makes sense, thank you for the kind update, Jianhui!

I also confirmed mm-new that updated with the v2 doesn't cause the build error.


Thanks,
SJ

[...]

  reply	other threads:[~2026-03-08 22:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 14:03 [PATCH] mm/userfaultfd: fix hugetlb fault mutex hash calculation Jianhui Zhou
2026-03-06 16:53 ` Peter Xu
2026-03-07 13:37   ` 周建辉
2026-03-07 13:59   ` Jianhui Zhou
2026-03-07  3:27 ` SeongJae Park
2026-03-08 13:41   ` Jianhui Zhou
2026-03-08 22:57     ` SeongJae Park [this message]
2026-03-07 14:35 ` [PATCH v2] " Jianhui Zhou
2026-03-09  2:08   ` Hugh Dickins
2026-03-09  3:08     ` Jianhui Zhou
2026-03-09 16:47   ` David Hildenbrand (Arm)
2026-03-10 10:24     ` Jianhui Zhou
2026-03-09  3:30 ` [PATCH v3] " Jianhui Zhou
2026-03-10 11:05 ` [PATCH v4] " Jianhui Zhou
2026-03-10 19:47   ` jane.chu
2026-03-11 10:54     ` Jianhui Zhou
2026-03-25  0:03       ` Andrew Morton
2026-03-25  1:06         ` SeongJae Park
2026-03-25  6:07           ` Jianhui Zhou
2026-03-25  8:49             ` David Hildenbrand (Arm)
2026-03-25 19:08               ` Mike Rapoport
2026-03-25  8:49         ` David Hildenbrand (Arm)
2026-03-25 19:02           ` Mike Rapoport
2026-03-25 23:46           ` jane.chu
2026-03-26  9:18             ` David Hildenbrand (Arm)
2026-03-25 19:10         ` Mike Rapoport
  -- strict thread matches above, loose matches on Subject: below --
2026-03-06 13:59 [PATCH] " Jianhui Zhou
2026-03-06 13:51 Jianhui Zhou

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=20260308225727.77058-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=jianhuizzzzz@gmail.com \
    --cc=jonaszhou@zhaoxin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    --cc=peterx@redhat.com \
    --cc=rppt@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+f525fd79634858f478e7@syzkaller.appspotmail.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