linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	Linux Memory Management List <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Xu <peterx@redhat.com>, Muchun Song <muchun.song@linux.dev>,
	Oscar Salvador <osalvador@suse.de>
Subject: Re: [linux-next:pending-fixes] [mm/hugetlb] d3fe1a0a02: WARNING:at_include/linux/hugetlb.h:#huge_pte_lockptr
Date: Wed, 31 Jul 2024 10:16:28 +0200	[thread overview]
Message-ID: <ff8619f5-7506-455d-ae13-124a4e87aa02@redhat.com> (raw)
In-Reply-To: <202407311421.95f5c759-lkp@intel.com>

On 31.07.24 09:20, kernel test robot wrote:
> 
> 
> Hello,
> 
> kernel test robot noticed "WARNING:at_include/linux/hugetlb.h:#huge_pte_lockptr" on:
> 
> commit: d3fe1a0a0272723474056e3000717d69923ad901 ("mm/hugetlb: fix hugetlb vs. core-mm PT locking")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git pending-fixes
> 
> [test failed on linux-next/master cd19ac2f903276b820f5d0d89de0c896c27036ed]
> 
> in testcase: trinity
> version: trinity-i386-abe9de86-1_20230429
> with following parameters:
> 
> 	runtime: 300s
> 	group: group-00
> 	nr_groups: 5
> 
> 
> 
> compiler: gcc-11
> test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
> 
> (please refer to attached dmesg/kmsg for entire log/backtrace)
> 
> 
> +------------------------------------------------------+------------+------------+
> |                                                      | e98970a1d2 | d3fe1a0a02 |
> +------------------------------------------------------+------------+------------+
> | WARNING:at_include/linux/hugetlb.h:#huge_pte_lockptr | 0          | 12         |
> | EIP:huge_pte_lockptr                                 | 0          | 12         |
> +------------------------------------------------------+------------+------------+
> 
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <oliver.sang@intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202407311421.95f5c759-lkp@intel.com
> 
> 
> [   39.570466][ T3479] ------------[ cut here ]------------
> [ 39.570921][ T3479] WARNING: CPU: 0 PID: 3479 at include/linux/hugetlb.h:948 huge_pte_lockptr (include/linux/hugetlb.h:948 (discriminator 1))

Helpful! Likely triggers because in that kernel cfg P4D_SIZE is 0.

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2024-07-31  8:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31  7:20 kernel test robot
2024-07-31  8:16 ` David Hildenbrand [this message]
2024-07-31  9:28   ` David Hildenbrand
2024-07-31  9:40     ` David Hildenbrand

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=ff8619f5-7506-455d-ae13-124a4e87aa02@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=muchun.song@linux.dev \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=osalvador@suse.de \
    --cc=peterx@redhat.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