From: kernel test robot <oliver.sang@intel.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>, <oliver.sang@intel.com>
Subject: Re: [PATCH v3] locking/mutex: remove redundant argument from __mutex_lock_common()
Date: Mon, 18 Sep 2023 15:52:06 +0800 [thread overview]
Message-ID: <202309181501.b44a0030-oliver.sang@intel.com> (raw)
In-Reply-To: <13334f7016362b2031eb65b03cb1a49b6500957f.1694548262.git.mirq-linux@rere.qmqm.pl>
Hello,
kernel test robot noticed "canonical_address#:#[##]" on:
commit: e51feab54b4cf9e46f5f1c70a95bd783d71bea17 ("[PATCH v3] locking/mutex: remove redundant argument from __mutex_lock_common()")
url: https://github.com/intel-lab-lkp/linux/commits/Micha-Miros-aw/locking-mutex-remove-redundant-argument-from-__mutex_lock_common/20230913-040021
base: https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git 68373ebb9d61985e05574313a356f751ef9911ab
patch link: https://lore.kernel.org/all/13334f7016362b2031eb65b03cb1a49b6500957f.1694548262.git.mirq-linux@rere.qmqm.pl/
patch subject: [PATCH v3] locking/mutex: remove redundant argument from __mutex_lock_common()
in testcase: boot
compiler: gcc-12
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/202309181501.b44a0030-oliver.sang@intel.com
[ 32.125787][ T1] AVX2 or AES-NI instructions are not detected.
[ 32.126826][ T1] AVX or AES-NI instructions are not detected.
[ 32.127952][ T1] AVX2 or AES-NI instructions are not detected.
[ 32.131287][ T1] AVX512/GFNI instructions are not detected.
[ 32.132975][ T1] Beginning ww mutex selftests
[ 36.707495][ T37] general protection fault, probably for non-canonical address 0xfbd59c00000000a2: 0000 [#1] SMP KASAN PTI
[ 36.708950][ T37] KASAN: maybe wild-memory-access in range [0xdead000000000510-0xdead000000000517]
[ 36.708950][ T37] CPU: 0 PID: 37 Comm: kworker/u4:2 Not tainted 6.5.0-rc3-00003-ge51feab54b4c #1 d00dc367a39745ce3f654e553e9329c6c6efc292
[ 36.708950][ T37] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 36.708950][ T37] Workqueue: test-ww_mutex stress_inorder_work
[ 36.708950][ T37] RIP: 0010:__ww_mutex_check_waiters (mutex.c:?)
[ 36.708950][ T37] Code: 01 38 d0 7c 08 84 d2 0f 85 45 01 00 00 66 41 83 7f 16 00 74 45 48 b8 00 00 00 00 00 fc ff df 48 8d 7e 10 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84 c0 74 08 3c 03 0f 8e 30 01 00 00 8b 4e 10 85 c9 75
All code
========
0: 01 38 add %edi,(%rax)
2: d0 7c 08 84 sarb -0x7c(%rax,%rcx,1)
6: d2 0f rorb %cl,(%rdi)
8: 85 45 01 test %eax,0x1(%rbp)
b: 00 00 add %al,(%rax)
d: 66 41 83 7f 16 00 cmpw $0x0,0x16(%r15)
13: 74 45 je 0x5a
15: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
1c: fc ff df
1f: 48 8d 7e 10 lea 0x10(%rsi),%rdi
23: 48 89 fa mov %rdi,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
2a:* 0f b6 04 02 movzbl (%rdx,%rax,1),%eax <-- trapping instruction
2e: 84 c0 test %al,%al
30: 74 08 je 0x3a
32: 3c 03 cmp $0x3,%al
34: 0f 8e 30 01 00 00 jle 0x16a
3a: 8b 4e 10 mov 0x10(%rsi),%ecx
3d: 85 c9 test %ecx,%ecx
3f: 75 .byte 0x75
Code starting with the faulting instruction
===========================================
0: 0f b6 04 02 movzbl (%rdx,%rax,1),%eax
4: 84 c0 test %al,%al
6: 74 08 je 0x10
8: 3c 03 cmp $0x3,%al
a: 0f 8e 30 01 00 00 jle 0x140
10: 8b 4e 10 mov 0x10(%rsi),%ecx
13: 85 c9 test %ecx,%ecx
15: 75 .byte 0x75
[ 36.708950][ T37] RSP: 0000:ffff88811273fa38 EFLAGS: 00010a02
[ 36.708950][ T37] RAX: dffffc0000000000 RBX: ffff8881108afbf0 RCX: 0000000000000000
[ 36.708950][ T37] RDX: 1bd5a000000000a2 RSI: dead000000000500 RDI: dead000000000510
[ 36.708950][ T37] RBP: ffff88815a089060 R08: 0000000000000000 R09: 0000000000000000
[ 36.708950][ T37] R10: 0000000000000000 R11: 0000000000000000 R12: ffff88815a0890b0
[ 36.708950][ T37] R13: ffffed10224e7f90 R14: dffffc0000000000 R15: ffff88811273fc70
[ 36.708950][ T37] FS: 0000000000000000(0000) GS:ffff8883af000000(0000) knlGS:0000000000000000
[ 36.708950][ T37] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 36.708950][ T37] CR2: ffff88843ffff000 CR3: 000000000508a000 CR4: 00000000000406f0
[ 36.708950][ T37] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 36.708950][ T37] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 36.708950][ T37] Call Trace:
[ 36.708950][ T37] <TASK>
[ 36.708950][ T37] ? die_addr (??:?)
[ 36.738985][ T37] ? exc_general_protection (??:?)
[ 36.738985][ T37] ? asm_exc_general_protection (??:?)
[ 36.738985][ T37] ? __ww_mutex_check_waiters (mutex.c:?)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230918/202309181501.b44a0030-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-09-18 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 19:55 [PATCH v3] locking/mutex: remove redundant argument from __mutex_lock_common() Michał Mirosław
2023-09-18 7:52 ` kernel test robot [this message]
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=202309181501.b44a0030-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=oe-lkp@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/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