All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Ibrahim Jirdeh <ibrahimjirdeh@meta.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	Amir Goldstein <amir73il@gmail.com>,
	<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<ibrahimjirdeh@meta.com>, <jack@suse.cz>, <josef@toxicpanda.com>,
	<lesha@meta.com>, <sargun@meta.com>, <oliver.sang@intel.com>
Subject: Re: [PATCH v4 3/3] fanotify: introduce event response identifier
Date: Wed, 16 Jul 2025 14:25:17 +0800	[thread overview]
Message-ID: <202507160713.34ee11f5-lkp@intel.com> (raw)
In-Reply-To: <20250711183101.4074140-4-ibrahimjirdeh@meta.com>



Hello,

kernel test robot noticed "INFO:trying_to_register_non-static_key" on:

commit: 16091e7d62ae910fee1e3bfc72943ec678e8df35 ("[PATCH v4 3/3] fanotify: introduce event response identifier")
url: https://github.com/intel-lab-lkp/linux/commits/Ibrahim-Jirdeh/fanotify-add-support-for-a-variable-length-permission-event/20250712-023425
base: https://git.kernel.org/cgit/linux/kernel/git/jack/linux-fs.git fsnotify
patch link: https://lore.kernel.org/all/20250711183101.4074140-4-ibrahimjirdeh@meta.com/
patch subject: [PATCH v4 3/3] fanotify: introduce event response identifier

in testcase: trinity
version: 
with following parameters:

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



config: x86_64-randconfig-006-20250712
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)


+----------------------------------------+------------+------------+
|                                        | feb842cee4 | 16091e7d62 |
+----------------------------------------+------------+------------+
| INFO:trying_to_register_non-static_key | 0          | 11         |
+----------------------------------------+------------+------------+


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/202507160713.34ee11f5-lkp@intel.com


[  570.145604][ T3660] INFO: trying to register non-static key.
[  570.152934][ T3660] The code is fine but needs lockdep annotation, or maybe
[  570.161254][ T3660] you didn't initialize this object before use?
[  570.168674][ T3660] turning off the locking correctness validator.
[  570.176388][ T3660] CPU: 0 UID: 0 PID: 3660 Comm: trinity-c3 Not tainted 6.16.0-rc3-00238-g16091e7d62ae #1 PREEMPT(lazy)
[  570.189708][ T3660] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[  570.202248][ T3660] Call Trace:
[  570.206437][ T3660]  <TASK>
[ 570.210125][ T3660] dump_stack_lvl (arch/x86/include/asm/irqflags.h:26 (discriminator 3) arch/x86/include/asm/irqflags.h:109 (discriminator 3) arch/x86/include/asm/irqflags.h:151 (discriminator 3) lib/dump_stack.c:123 (discriminator 3)) 
[ 570.215892][ T3660] dump_stack (lib/dump_stack.c:130) 
[ 570.220985][ T3660] register_lock_class (kernel/locking/lockdep.c:988 kernel/locking/lockdep.c:1302) 
[ 570.227173][ T3660] __lock_acquire (kernel/locking/lockdep.c:5116) 
[ 570.232580][ T3660] lock_acquire (kernel/locking/lockdep.c:473 kernel/locking/lockdep.c:5873) 
[ 570.237898][ T3660] ? ida_destroy (lib/idr.c:615) 
[ 570.243703][ T3660] ? _raw_spin_lock_irqsave (include/linux/spinlock_api_smp.h:110 kernel/locking/spinlock.c:162) 
[ 570.250176][ T3660] ? ida_destroy (lib/idr.c:615) 
[ 570.255813][ T3660] ? trace_preempt_off (kernel/trace/trace_preemptirq.c:128) 
[ 570.261457][ T3660] ? ida_destroy (lib/idr.c:615) 
[ 570.266841][ T3660] _raw_spin_lock_irqsave (include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) 
[ 570.272831][ T3660] ? ida_destroy (lib/idr.c:615) 
[ 570.278373][ T3660] ida_destroy (lib/idr.c:615) 
[ 570.283784][ T3660] ? xas_next_entry (include/trace/events/filemap.h:49) 
[ 570.290885][ T3660] ? kfree (mm/slub.c:2312 mm/slub.c:4643 mm/slub.c:4842) 
[ 570.295967][ T3660] fanotify_free_group_priv (fs/notify/fanotify/fanotify.c:1049) 
[ 570.302446][ T3660] fsnotify_put_group (fs/notify/group.c:28 fs/notify/group.c:110) 
[ 570.308643][ T3660] fsnotify_destroy_group (fs/notify/group.c:51) 
[ 570.315249][ T3660] ? fsnotify_group_stop_queueing (fs/notify/group.c:51) 
[ 570.322447][ T3660] ? lockdep_init_map_type (kernel/locking/lockdep.c:4976) 
[ 570.329051][ T3660] ? lockdep_init_map_type (kernel/locking/lockdep.c:4976) 
[ 570.335640][ T3660] ? __init_waitqueue_head (include/linux/list.h:37 kernel/sched/wait.c:12) 
[ 570.342015][ T3660] __do_sys_fanotify_init (fs/notify/fanotify/fanotify_user.c:1718) 
[ 570.348111][ T3660] ? __rcu_read_unlock (kernel/rcu/tree_plugin.h:445 (discriminator 3)) 
[ 570.353754][ T3660] __x64_sys_fanotify_init (fs/notify/fanotify/fanotify_user.c:1526) 
[ 570.360325][ T3660] ? trace_hardirqs_on (kernel/trace/trace_preemptirq.c:80 (discriminator 22)) 
[ 570.366287][ T3660] x64_sys_call (arch/x86/entry/syscall_64.c:41) 
[ 570.371831][ T3660] do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94) 
[ 570.377436][ T3660] entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) 
[  570.384571][ T3660] RIP: 0033:0x463519
[ 570.389240][ T3660] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 db 59 00 00 c3 66 2e 0f 1f 84 00 00 00 00
All code
========
   0:	00 f3                	add    %dh,%bl
   2:	c3                   	ret
   3:	66 2e 0f 1f 84 00 00 	cs nopw 0x0(%rax,%rax,1)
   a:	00 00 00 
   d:	0f 1f 40 00          	nopl   0x0(%rax)
  11:	48 89 f8             	mov    %rdi,%rax
  14:	48 89 f7             	mov    %rsi,%rdi
  17:	48 89 d6             	mov    %rdx,%rsi
  1a:	48 89 ca             	mov    %rcx,%rdx
  1d:	4d 89 c2             	mov    %r8,%r10
  20:	4d 89 c8             	mov    %r9,%r8
  23:	4c 8b 4c 24 08       	mov    0x8(%rsp),%r9
  28:	0f 05                	syscall
  2a:*	48 3d 01 f0 ff ff    	cmp    $0xfffffffffffff001,%rax		<-- trapping instruction
  30:	0f 83 db 59 00 00    	jae    0x5a11
  36:	c3                   	ret
  37:	66                   	data16
  38:	2e                   	cs
  39:	0f                   	.byte 0xf
  3a:	1f                   	(bad)
  3b:	84 00                	test   %al,(%rax)
  3d:	00 00                	add    %al,(%rax)
	...

Code starting with the faulting instruction
===========================================
   0:	48 3d 01 f0 ff ff    	cmp    $0xfffffffffffff001,%rax
   6:	0f 83 db 59 00 00    	jae    0x59e7
   c:	c3                   	ret
   d:	66                   	data16
   e:	2e                   	cs
   f:	0f                   	.byte 0xf
  10:	1f                   	(bad)
  11:	84 00                	test   %al,(%rax)
  13:	00 00                	add    %al,(%rax)
	...
[  570.411823][ T3660] RSP: 002b:00007fff92c9e6d8 EFLAGS: 00000246 ORIG_RAX: 000000000000012c
[  570.421741][ T3660] RAX: ffffffffffffffda RBX: 000000000000012c RCX: 0000000000463519
[  570.430814][ T3660] RDX: 0000000004000055 RSI: 00000000001c1400 RDI: 000000000000002c
[  570.440208][ T3660] RBP: 00007f4a06748000 R08: ffffffffffffffb7 R09: 0000000000000000
[  570.449706][ T3660] R10: 0000000000002c85 R11: 0000000000000246 R12: 0000000000000002
[  570.458904][ T3660] R13: 00007f4a06748058 R14: 0000000036007850 R15: 00007f4a06748000
[  570.468210][ T3660]  </TASK>


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



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


      parent reply	other threads:[~2025-07-16  6:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 18:30 [PATCH v4 0/3] fanotify: introduce response identifier Ibrahim Jirdeh
2025-07-11 18:30 ` [PATCH v4 1/3] fanotify: add support for a variable length permission event Ibrahim Jirdeh
2025-07-22 14:01   ` Jan Kara
2025-07-22 15:13     ` Amir Goldstein
2025-07-23  7:43       ` Jan Kara
2025-07-23 10:24         ` Amir Goldstein
2025-07-11 18:31 ` [PATCH v4 2/3] fanotify: allow pre-content events with fid info Ibrahim Jirdeh
2025-07-11 18:31 ` [PATCH v4 3/3] fanotify: introduce event response identifier Ibrahim Jirdeh
2025-07-12  6:16   ` Amir Goldstein
2025-07-12 20:51   ` kernel test robot
2025-07-16  6:25   ` 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=202507160713.34ee11f5-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=amir73il@gmail.com \
    --cc=ibrahimjirdeh@meta.com \
    --cc=jack@suse.cz \
    --cc=josef@toxicpanda.com \
    --cc=lesha@meta.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=sargun@meta.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.