linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Naoya Horiguchi <naoya.horiguchi@linux.dev>, <linux-mm@kvack.org>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"David Hildenbrand" <david@redhat.com>,
	"Mike Kravetz" <mike.kravetz@oracle.com>,
	"Liu Shixin" <liushixin2@huawei.com>,
	"Yang Shi" <shy828301@gmail.com>,
	"Oscar Salvador" <osalvador@suse.de>,
	"Muchun Song" <songmuchun@bytedance.com>,
	"Naoya Horiguchi" <naoya.horiguchi@nec.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] arch/x86/mm/hugetlbpage.c: pud_huge() returns 0 when using 2-level paging
Date: Tue, 8 Nov 2022 09:36:27 +0800	[thread overview]
Message-ID: <60d8bdb2-4d51-7b67-1b0d-df54d9403062@huawei.com> (raw)
In-Reply-To: <20221107021010.2449306-1-naoya.horiguchi@linux.dev>

On 2022/11/7 10:10, Naoya Horiguchi wrote:
> From: Naoya Horiguchi <naoya.horiguchi@nec.com>
> 
> The following bug is reported to be triggered when starting X on x86-32
> system with i915:
> 
>   [  225.777375] kernel BUG at mm/memory.c:2664!
>   [  225.777391] invalid opcode: 0000 [#1] PREEMPT SMP
>   [  225.777405] CPU: 0 PID: 2402 Comm: Xorg Not tainted 6.1.0-rc3-bdg+ #86
>   [  225.777415] Hardware name:  /8I865G775-G, BIOS F1 08/29/2006
>   [  225.777421] EIP: __apply_to_page_range+0x24d/0x31c
>   [  225.777437] Code: ff ff 8b 55 e8 8b 45 cc e8 0a 11 ec ff 89 d8 83 c4 28 5b 5e 5f 5d c3 81 7d e0 a0 ef 96 c1 74 ad 8b 45 d0 e8 2d 83 49 00 eb a3 <0f> 0b 25 00 f0 ff ff 81 eb 00 00 00 40 01 c3 8b 45 ec 8b 00 e8 76
>   [  225.777446] EAX: 00000001 EBX: c53a3b58 ECX: b5c00000 EDX: c258aa00
>   [  225.777454] ESI: b5c00000 EDI: b5900000 EBP: c4b0fdb4 ESP: c4b0fd80
>   [  225.777462] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 EFLAGS: 00010202
>   [  225.777470] CR0: 80050033 CR2: b5900000 CR3: 053a3000 CR4: 000006d0
>   [  225.777479] Call Trace:
>   [  225.777486]  ? i915_memcpy_init_early+0x63/0x63 [i915]
>   [  225.777684]  apply_to_page_range+0x21/0x27
>   [  225.777694]  ? i915_memcpy_init_early+0x63/0x63 [i915]
>   [  225.777870]  remap_io_mapping+0x49/0x75 [i915]
>   [  225.778046]  ? i915_memcpy_init_early+0x63/0x63 [i915]
>   [  225.778220]  ? mutex_unlock+0xb/0xd
>   [  225.778231]  ? i915_vma_pin_fence+0x6d/0xf7 [i915]
>   [  225.778420]  vm_fault_gtt+0x2a9/0x8f1 [i915]
>   [  225.778644]  ? lock_is_held_type+0x56/0xe7
>   [  225.778655]  ? lock_is_held_type+0x7a/0xe7
>   [  225.778663]  ? 0xc1000000
>   [  225.778670]  __do_fault+0x21/0x6a
>   [  225.778679]  handle_mm_fault+0x708/0xb21
>   [  225.778686]  ? mt_find+0x21e/0x5ae
>   [  225.778696]  exc_page_fault+0x185/0x705
>   [  225.778704]  ? doublefault_shim+0x127/0x127
>   [  225.778715]  handle_exception+0x130/0x130
>   [  225.778723] EIP: 0xb700468a
> 
> Recently pud_huge() got aware of non-present entry by commit 3a194f3f8ad0
> ("mm/hugetlb: make pud_huge() and follow_huge_pud() aware of non-present
> pud entry") to handle some special states of gigantic page.  However, it's
> overlooked that pud_none() always returns false when running with 2-level
> paging, and as a result pmd_huge() can return true pointlessly.

LGTM. Thanks for your fixing.

Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>

Thanks,
Miaohe Lin




  parent reply	other threads:[~2022-11-08  1:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07  2:10 [PATCH v1] arch/x86/mm/hugetlbpage.c: pud_huge() returns 0 when using 2-level paging Naoya Horiguchi
2022-11-07 12:42 ` Ville Syrjälä
2022-11-08  0:00   ` HORIGUCHI NAOYA(堀口 直也)
2022-11-08  0:10     ` Andrew Morton
2022-11-08  1:36 ` Miaohe Lin [this message]
2022-11-09  3:14 ` Muchun Song

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=60d8bdb2-4d51-7b67-1b0d-df54d9403062@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liushixin2@huawei.com \
    --cc=mike.kravetz@oracle.com \
    --cc=naoya.horiguchi@linux.dev \
    --cc=naoya.horiguchi@nec.com \
    --cc=osalvador@suse.de \
    --cc=shy828301@gmail.com \
    --cc=songmuchun@bytedance.com \
    --cc=ville.syrjala@linux.intel.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;
as well as URLs for NNTP newsgroup(s).