All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	"David Wang" <00107082@163.com>,
	Kent Overstreet <kent.overstreet@linux.dev>,
	"Minchan Kim" <minchan@google.com>,
	Pasha Tatashin <pasha.tatashin@soleen.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	Sourav Panda <souravpanda@google.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Vlastimil Babka <vbabka@suse.cz>, "Yu Zhao" <yuzhao@google.com>,
	Zhenhua Huang <quic_zhenhuah@quicinc.com>, <linux-mm@kvack.org>,
	<oliver.sang@intel.com>
Subject: [linux-next:master] [alloc_tag]  0d1ae800a1: WARNING:at_include/linux/alloc_tag.h:#__pgalloc_tag_sub
Date: Fri, 14 Feb 2025 11:04:27 +0800	[thread overview]
Message-ID: <202502141006.21ae07ee-lkp@intel.com> (raw)


hi, Suren Baghdasaryan and all,

we know that this commit is not the root cause of the WARNING. it just changes
the WARNING stats bot captured.

fd942e78294214c8 0d1ae800a1923762d8240dc4987
---------------- ---------------------------
       fail:runs  %reproduction    fail:runs
           |             |             |
           :6           50%           3:6     dmesg.WARNING:at_include/linux/alloc_tag.h:#__pgalloc_tag_sub
          6:6         -100%            :6     dmesg.WARNING:at_include/linux/alloc_tag.h:#pgalloc_tag_sub

we made out this report just FYI, in case anybody has interests to look further
about this existing WARNING.

below is full report.


Hello,

kernel test robot noticed "WARNING:at_include/linux/alloc_tag.h:#__pgalloc_tag_sub" on:

commit: 0d1ae800a1923762d8240dc4987761f29a35d1a9 ("alloc_tag: uninline code gated by mem_alloc_profiling_key in page allocator")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master

[test failed on linux-next/master 7b7a883c7f4de1ee5040bd1c32aabaafde54d209]

in testcase: trinity
version: trinity-i386-abe9de86-1_20230429
with following parameters:

	runtime: 300s
	group: group-02
	nr_groups: 5



config: x86_64-randconfig-071-20250210
compiler: clang-19
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G

(please refer to attached dmesg/kmsg for entire log/backtrace)



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/202502141006.21ae07ee-lkp@intel.com


[  115.486807][ T6579] ------------[ cut here ]------------
[  115.487378][ T6579] alloc_tag was not set
[ 115.487709][ T6579] WARNING: CPU: 0 PID: 6579 at include/linux/alloc_tag.h:152 __pgalloc_tag_sub (include/linux/alloc_tag.h:152) 
[  115.488409][ T6579] Modules linked in: 8021q mrp garp stp qrtr nfc caif_socket caif phonet llc2 llc sha1_ssse3 serio_raw tiny_power_button button
[  115.489418][ T6579] CPU: 0 UID: 0 PID: 6579 Comm: date Tainted: G                T  6.14.0-rc2-00048-g0d1ae800a192 #1 2337137258306bf95f42324e33e4040ee055b8c6
[  115.490636][ T6579] Tainted: [T]=RANDSTRUCT
[  115.490962][ T6579] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 115.491699][ T6579] RIP: 0010:__pgalloc_tag_sub (include/linux/alloc_tag.h:152) 
[ 115.492110][ T6579] Code: 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 90 0f 0b 90 eb eb c6 05 0b ed 01 03 01 48 c7 c7 20 76 f2 ad 90 e8 81 7e c0 ff 90 <0f> 0b 90 90 4c 8b 7d d0 4d 85 ff 0f 85 25 ff ff ff e9 72 ff ff ff
All code
========
   0:	48 83 c4 08          	add    $0x8,%rsp
   4:	5b                   	pop    %rbx
   5:	41 5c                	pop    %r12
   7:	41 5d                	pop    %r13
   9:	41 5e                	pop    %r14
   b:	41 5f                	pop    %r15
   d:	5d                   	pop    %rbp
   e:	c3                   	ret
   f:	90                   	nop
  10:	0f 0b                	ud2
  12:	90                   	nop
  13:	eb eb                	jmp    0x0
  15:	c6 05 0b ed 01 03 01 	movb   $0x1,0x301ed0b(%rip)        # 0x301ed27
  1c:	48 c7 c7 20 76 f2 ad 	mov    $0xffffffffadf27620,%rdi
  23:	90                   	nop
  24:	e8 81 7e c0 ff       	call   0xffffffffffc07eaa
  29:	90                   	nop
  2a:*	0f 0b                	ud2		<-- trapping instruction
  2c:	90                   	nop
  2d:	90                   	nop
  2e:	4c 8b 7d d0          	mov    -0x30(%rbp),%r15
  32:	4d 85 ff             	test   %r15,%r15
  35:	0f 85 25 ff ff ff    	jne    0xffffffffffffff60
  3b:	e9 72 ff ff ff       	jmp    0xffffffffffffffb2

Code starting with the faulting instruction
===========================================
   0:	0f 0b                	ud2
   2:	90                   	nop
   3:	90                   	nop
   4:	4c 8b 7d d0          	mov    -0x30(%rbp),%r15
   8:	4d 85 ff             	test   %r15,%r15
   b:	0f 85 25 ff ff ff    	jne    0xffffffffffffff36
  11:	e9 72 ff ff ff       	jmp    0xffffffffffffff88
[  115.493423][ T6579] RSP: 0000:ffff888137d8f340 EFLAGS: 00010286
[  115.493859][ T6579] RAX: 0000000000000015 RBX: ffff8881064018f8 RCX: 0000000000000000
[  115.494407][ T6579] RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000001
[  115.494963][ T6579] RBP: ffff888137d8f370 R08: ffffffffaef2cdb3 R09: 1ffffffff5de59b6
[  115.495520][ T6579] R10: dffffc0000000000 R11: fffffbfff5de59b7 R12: ffffea00040013d8
[  115.496063][ T6579] R13: dffffc0000000000 R14: 0000000000001000 R15: 0000000000000000
[  115.496621][ T6579] FS:  0000000000000000(0000) GS:ffffffffaeabf000(0000) knlGS:0000000000000000
[  115.497251][ T6579] CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
[  115.497706][ T6579] CR2: 00000000ff941ee0 CR3: 0000000127139000 CR4: 00000000000406b0
[  115.498261][ T6579] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  115.498840][ T6579] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[  115.499429][ T6579] Call Trace:
[  115.499681][ T6579]  <TASK>
[ 115.499913][ T6579] ? show_regs (arch/x86/kernel/dumpstack.c:479) 
[ 115.500340][ T6579] ? __warn (kernel/panic.c:748) 
[ 115.500642][ T6579] ? __pgalloc_tag_sub (include/linux/alloc_tag.h:152) 
[ 115.501001][ T6579] ? __pgalloc_tag_sub (include/linux/alloc_tag.h:152) 
[ 115.501369][ T6579] ? report_bug (lib/bug.c:?) 
[ 115.501693][ T6579] ? handle_bug (arch/x86/kernel/traps.c:285) 
[ 115.502002][ T6579] ? exc_invalid_op (arch/x86/kernel/traps.c:309) 
[ 115.502337][ T6579] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) 
[ 115.502715][ T6579] ? __pgalloc_tag_sub (include/linux/alloc_tag.h:152) 
[ 115.503097][ T6579] free_frozen_pages (include/linux/mm.h:2250 mm/page_alloc.c:1210 mm/page_alloc.c:2738) 
[ 115.503472][ T6579] __free_slab (mm/slub.c:2669) 
[ 115.503801][ T6579] free_slab (mm/slub.c:2692) 
[ 115.504112][ T6579] discard_slab (mm/slub.c:2698) 
[ 115.504434][ T6579] __slab_free (mm/slub.c:?) 
[ 115.504772][ T6579] ? qlist_free_all (mm/kasan/quarantine.c:163) 
[ 115.505111][ T6579] ___cache_free (mm/slub.c:4575) 
[ 115.505447][ T6579] qlist_free_all (mm/kasan/quarantine.c:174) 
[ 115.505777][ T6579] kasan_quarantine_reduce (mm/kasan/quarantine.c:287) 
[ 115.506170][ T6579] __kasan_slab_alloc (mm/kasan/common.c:331) 
[ 115.506526][ T6579] kmem_cache_alloc_noprof (mm/slub.c:4129) 
[ 115.506911][ T6579] ? vm_area_dup (include/linux/sched.h:2248) 
[ 115.507234][ T6579] vm_area_dup (include/linux/sched.h:2248) 
[ 115.507551][ T6579] __split_vma (mm/vma.c:481) 
[ 115.507889][ T6579] vms_gather_munmap_vmas (mm/vma.c:1307) 
[ 115.508307][ T6579] mmap_region (mm/vma.c:2259) 
[ 115.508610][ T6579] ? __kasan_check_read (mm/kasan/shadow.c:31) 
[ 115.508961][ T6579] ? validate_chain (arch/x86/include/asm/bitops.h:227 arch/x86/include/asm/bitops.h:239 include/asm-generic/bitops/instrumented-non-atomic.h:142 kernel/locking/lockdep.c:230 kernel/locking/lockdep.c:3818 kernel/locking/lockdep.c:3874) 
[ 115.509301][ T6579] ? perf_event_mmap (kernel/events/core.c:9193) 
[ 115.509759][ T6579] do_mmap (mm/mmap.c:561) 
[ 115.510073][ T6579] vm_mmap_pgoff (mm/util.c:575) 
[ 115.510467][ T6579] ksys_mmap_pgoff (mm/mmap.c:607) 
[ 115.510820][ T6579] __ia32_sys_mmap_pgoff (mm/mmap.c:614) 
[ 115.511197][ T6579] ia32_sys_call (kbuild/obj/consumer/x86_64-randconfig-071-20250210/./arch/x86/include/generated/asm/syscalls_32.h:317) 
[ 115.511542][ T6579] do_int80_emulation (arch/x86/entry/common.c:?) 
[ 115.511914][ T6579] ? up_write (arch/x86/include/asm/preempt.h:103 kernel/locking/rwsem.c:1375 kernel/locking/rwsem.c:1630) 
[ 115.512237][ T6579] ? vm_mmap_pgoff (mm/util.c:579) 
[ 115.512587][ T6579] ? fput (arch/x86/include/asm/preempt.h:103 include/linux/preempt.h:480 include/linux/file_ref.h:161 fs/file_table.c:516) 
[ 115.512885][ T6579] ? __this_cpu_preempt_check (lib/smp_processor_id.c:67) 
[ 115.513279][ T6579] ? lockdep_hardirqs_on (kernel/locking/lockdep.c:4470) 
[ 115.513639][ T6579] ? syscall_exit_to_user_mode (kernel/entry/common.c:221) 
[ 115.514057][ T6579] ? do_int80_emulation (arch/x86/entry/common.c:257) 
[ 115.514418][ T6579] ? __this_cpu_preempt_check (lib/smp_processor_id.c:67) 
[ 115.514793][ T6579] ? trace_hardirqs_off_finish (include/trace/events/preemptirq.h:36) 
[ 115.515191][ T6579] ? do_int80_emulation (include/linux/entry-common.h:118) 
[ 115.515553][ T6579] asm_int80_emulation (arch/x86/include/asm/idtentry.h:626) 
[  115.515906][ T6579] RIP: 0023:0xf7f7ccb0
[ 115.516201][ T6579] Code: 4c 24 34 89 44 24 0c 8b 44 24 44 8b 54 24 38 8b 74 24 3c 8b 7c 24 40 a9 ff 0f 00 00 75 1c c1 e8 0c 89 c5 b8 c0 00 00 00 cd 80 <3d> 00 f0 ff ff 77 21 83 c4 1c 5b 5e 5f 5d c3 90 83 c4 1c b8 ea ff
All code
========
   0:	4c 24 34             	rex.WR and $0x34,%al
   3:	89 44 24 0c          	mov    %eax,0xc(%rsp)
   7:	8b 44 24 44          	mov    0x44(%rsp),%eax
   b:	8b 54 24 38          	mov    0x38(%rsp),%edx
   f:	8b 74 24 3c          	mov    0x3c(%rsp),%esi
  13:	8b 7c 24 40          	mov    0x40(%rsp),%edi
  17:	a9 ff 0f 00 00       	test   $0xfff,%eax
  1c:	75 1c                	jne    0x3a
  1e:	c1 e8 0c             	shr    $0xc,%eax
  21:	89 c5                	mov    %eax,%ebp
  23:	b8 c0 00 00 00       	mov    $0xc0,%eax
  28:	cd 80                	int    $0x80
  2a:*	3d 00 f0 ff ff       	cmp    $0xfffff000,%eax		<-- trapping instruction
  2f:	77 21                	ja     0x52
  31:	83 c4 1c             	add    $0x1c,%esp
  34:	5b                   	pop    %rbx
  35:	5e                   	pop    %rsi
  36:	5f                   	pop    %rdi
  37:	5d                   	pop    %rbp
  38:	c3                   	ret
  39:	90                   	nop
  3a:	83 c4 1c             	add    $0x1c,%esp
  3d:	b8                   	.byte 0xb8
  3e:	ea                   	(bad)
  3f:	ff                   	.byte 0xff

Code starting with the faulting instruction
===========================================
   0:	3d 00 f0 ff ff       	cmp    $0xfffff000,%eax
   5:	77 21                	ja     0x28
   7:	83 c4 1c             	add    $0x1c,%esp
   a:	5b                   	pop    %rbx
   b:	5e                   	pop    %rsi
   c:	5f                   	pop    %rdi
   d:	5d                   	pop    %rbp
   e:	c3                   	ret
   f:	90                   	nop
  10:	83 c4 1c             	add    $0x1c,%esp
  13:	b8                   	.byte 0xb8
  14:	ea                   	(bad)
  15:	ff                   	.byte 0xff


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250214/202502141006.21ae07ee-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2025-02-14  3:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202502141006.21ae07ee-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=00107082@163.com \
    --cc=akpm@linux-foundation.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=minchan@google.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=pasha.tatashin@soleen.com \
    --cc=peterz@infradead.org \
    --cc=quic_zhenhuah@quicinc.com \
    --cc=rostedt@goodmis.org \
    --cc=shakeel.butt@linux.dev \
    --cc=souravpanda@google.com \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=yuzhao@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.