From: kernel test robot <oliver.sang@intel.com>
To: Valentine Sinitsyn <valesini@yandex-team.ru>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
Tejun Heo <tj@kernel.org>, Bjorn Helgaas <bhelgaas@google.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Dan Williams <dan.j.williams@intel.com>, <oliver.sang@intel.com>
Subject: Re: [PATCH v6 1/2] kernfs: sysfs: support custom llseek method for sysfs entries
Date: Tue, 5 Sep 2023 15:02:53 +0800 [thread overview]
Message-ID: <202309051442.bd6f9879-oliver.sang@intel.com> (raw)
In-Reply-To: <20230902155038.1661970-1-valesini@yandex-team.ru>
Hello,
kernel test robot noticed "WARNING:at_fs/kernfs/file.c:#kernfs_ops" on:
commit: c6eefad61209dab3de7446cf8151d38e70440484 ("[PATCH v6 1/2] kernfs: sysfs: support custom llseek method for sysfs entries")
url: https://github.com/intel-lab-lkp/linux/commits/Valentine-Sinitsyn/PCI-Implement-custom-llseek-for-sysfs-resource-entries/20230902-235234
patch link: https://lore.kernel.org/all/20230902155038.1661970-1-valesini@yandex-team.ru/
patch subject: [PATCH v6 1/2] kernfs: sysfs: support custom llseek method for sysfs entries
in testcase: boot
compiler: clang-16
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/202309051442.bd6f9879-oliver.sang@intel.com
[ 96.320907][ T252] ------------[ cut here ]------------
[ 96.321715][ T252] WARNING: CPU: 1 PID: 252 at fs/kernfs/file.c:109 kernfs_ops (fs/kernfs/file.c:109)
[ 96.322853][ T252] Modules linked in:
[ 96.323438][ T252] CPU: 1 PID: 252 Comm: systemd-logind Not tainted 6.5.0-10888-gc6eefad61209 #1
[ 96.324966][ T252] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 96.326330][ T252] RIP: 0010:kernfs_ops (fs/kernfs/file.c:109)
[ 96.327026][ T252] Code: 48 83 c3 68 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 de f3 e2 ff 48 8b 03 5b 41 5e 41 5f 31 c9 31 ff 31 f6 c3 cc <0f> 0b eb d2 44 89 f1 80 e1 07 fe c1 38 c1 7c 91 4c 89 f7 e8 76 f3
All code
========
0: 48 83 c3 68 add $0x68,%rbx
4: 48 89 d8 mov %rbx,%rax
7: 48 c1 e8 03 shr $0x3,%rax
b: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1)
10: 74 08 je 0x1a
12: 48 89 df mov %rbx,%rdi
15: e8 de f3 e2 ff call 0xffffffffffe2f3f8
1a: 48 8b 03 mov (%rbx),%rax
1d: 5b pop %rbx
1e: 41 5e pop %r14
20: 41 5f pop %r15
22: 31 c9 xor %ecx,%ecx
24: 31 ff xor %edi,%edi
26: 31 f6 xor %esi,%esi
28: c3 ret
29: cc int3
2a:* 0f 0b ud2 <-- trapping instruction
2c: eb d2 jmp 0x0
2e: 44 89 f1 mov %r14d,%ecx
31: 80 e1 07 and $0x7,%cl
34: fe c1 inc %cl
36: 38 c1 cmp %al,%cl
38: 7c 91 jl 0xffffffffffffffcb
3a: 4c 89 f7 mov %r14,%rdi
3d: e8 .byte 0xe8
3e: 76 f3 jbe 0x33
Code starting with the faulting instruction
===========================================
0: 0f 0b ud2
2: eb d2 jmp 0xffffffffffffffd6
4: 44 89 f1 mov %r14d,%ecx
7: 80 e1 07 and $0x7,%cl
a: fe c1 inc %cl
c: 38 c1 cmp %al,%cl
e: 7c 91 jl 0xffffffffffffffa1
10: 4c 89 f7 mov %r14,%rdi
13: e8 .byte 0xe8
14: 76 f3 jbe 0x9
[ 96.329439][ T252] RSP: 0018:ffff8881638e7ea0 EFLAGS: 00010246
[ 96.330261][ T252] RAX: 0000000000000000 RBX: ffff888111e4a2b8 RCX: 0000000000000000
[ 96.331346][ T252] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 96.332425][ T252] RBP: dffffc0000000000 R08: 0000000000000000 R09: 0000000000000000
[ 96.333503][ T252] R10: 0000000000000000 R11: ffffffff8184fd65 R12: ffff8881538a5c00
[ 96.334649][ T252] R13: ffff888161bc5ec0 R14: ffff888111e4a350 R15: dffffc0000000000
[ 96.335717][ T252] FS: 00007f2d9c6a8980(0000) GS:ffff8883aeb00000(0000) knlGS:0000000000000000
[ 96.336833][ T252] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 96.337593][ T252] CR2: 00005600c8ef1595 CR3: 0000000162f96000 CR4: 00000000000406a0
[ 96.338544][ T252] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 96.339487][ T252] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 96.340472][ T252] Call Trace:
[ 96.340983][ T252] <TASK>
[ 96.341447][ T252] ? __warn (kernel/panic.c:673)
[ 96.342078][ T252] ? kernfs_ops (fs/kernfs/file.c:109)
[ 96.342740][ T252] ? kernfs_ops (fs/kernfs/file.c:109)
[ 96.343391][ T252] ? report_bug (lib/bug.c:?)
[ 96.344046][ T252] ? find_held_lock (kernel/locking/lockdep.c:?)
[ 96.344738][ T252] ? handle_bug (arch/x86/kernel/traps.c:237)
[ 96.345314][ T252] ? exc_invalid_op (arch/x86/kernel/traps.c:258)
[ 96.345963][ T252] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:568)
[ 96.346694][ T252] ? __cfi_kernfs_fop_llseek (fs/kernfs/file.c:907)
[ 96.347473][ T252] ? kernfs_ops (fs/kernfs/file.c:109)
[ 96.348135][ T252] kernfs_fop_llseek (fs/kernfs/file.c:911)
[ 96.348869][ T252] ksys_lseek (fs/read_write.c:289)
[ 96.349497][ T252] do_syscall_64 (arch/x86/entry/common.c:?)
[ 96.350141][ T252] entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120)
[ 96.350952][ T252] RIP: 0033:0x7f2d9cf82fc7
[ 96.351602][ T252] Code: c7 c0 ff ff ff ff c3 0f 1f 40 00 48 8b 15 c1 ee 0c 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb ba 0f 1f 00 b8 08 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 99 ee 0c 00 f7 d8 64 89 02 48
All code
========
0: c7 c0 ff ff ff ff mov $0xffffffff,%eax
6: c3 ret
7: 0f 1f 40 00 nopl 0x0(%rax)
b: 48 8b 15 c1 ee 0c 00 mov 0xceec1(%rip),%rdx # 0xceed3
12: f7 d8 neg %eax
14: 64 89 02 mov %eax,%fs:(%rdx)
17: 48 c7 c0 ff ff ff ff mov $0xffffffffffffffff,%rax
1e: eb ba jmp 0xffffffffffffffda
20: 0f 1f 00 nopl (%rax)
23: b8 08 00 00 00 mov $0x8,%eax
28: 0f 05 syscall
2a:* 48 3d 00 f0 ff ff cmp $0xfffffffffffff000,%rax <-- trapping instruction
30: 77 01 ja 0x33
32: c3 ret
33: 48 8b 15 99 ee 0c 00 mov 0xcee99(%rip),%rdx # 0xceed3
3a: f7 d8 neg %eax
3c: 64 89 02 mov %eax,%fs:(%rdx)
3f: 48 rex.W
Code starting with the faulting instruction
===========================================
0: 48 3d 00 f0 ff ff cmp $0xfffffffffffff000,%rax
6: 77 01 ja 0x9
8: c3 ret
9: 48 8b 15 99 ee 0c 00 mov 0xcee99(%rip),%rdx # 0xceea9
10: f7 d8 neg %eax
12: 64 89 02 mov %eax,%fs:(%rdx)
15: 48 rex.W
[ 96.357571][ T252] RSP: 002b:00007fff4e4c3fc8 EFLAGS: 00000246 ORIG_RAX: 0000000000000008
[ 96.358740][ T252] RAX: ffffffffffffffda RBX: 0000563f1ffa0a80 RCX: 00007f2d9cf82fc7
[ 96.359842][ T252] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000007
[ 96.360873][ T252] RBP: 0000563f1ffa0a80 R08: 00007fff4e4c3fc0 R09: 0000000000000000
[ 96.361934][ T252] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
[ 96.363024][ T252] R13: 0000000000000000 R14: 00007fff4e4c4188 R15: 00007fff4e4c41a0
[ 96.364155][ T252] </TASK>
[ 96.364719][ T252] irq event stamp: 64209
[ 96.365341][ T252] hardirqs last enabled at (64219): __up_console_sem (arch/x86/include/asm/irqflags.h:26 arch/x86/include/asm/irqflags.h:67 arch/x86/include/asm/irqflags.h:127 kernel/printk/printk.c:347)
[ 96.366558][ T252] hardirqs last disabled at (64228): __up_console_sem (kernel/printk/printk.c:345)
[ 96.367774][ T252] softirqs last enabled at (64128): __do_softirq (arch/x86/include/asm/preempt.h:27 kernel/softirq.c:400 kernel/softirq.c:582)
[ 96.368971][ T252] softirqs last disabled at (64119): __irq_exit_rcu (kernel/softirq.c:612)
[ 96.370158][ T252] ---[ end trace 0000000000000000 ]---
Starting LKP bootstrap...
Starting /etc/rc.local Compatibility...
Starting OpenBSD Secure Shell server...
Starting Permit User Sessions...
[FAILED] Failed to start LSB: OpenIPMI Driver init script.
See 'systemctl status openipmi.service' for details.
[ OK ] Started User Login Management.
[ OK ] Started LKP bootstrap.
[ OK ] Started LSB: Load kernel image with kexec.
LKP: ttyS0: 296: skip deploy intel ucode as no ucode is specified
[ OK ] Finished Permit User Sessions.
[ OK ] Started OpenBSD Secure Shell server.
LKP: ttyS0: 296: Kernel tests: Boot OK!
LKP: ttyS0: 296: HOSTNAME vm-snb, MAC 52:54:00:12:34:56, kernel 6.5.0-10888-gc6eefad61209 1
LKP: ttyS0: 296: /lkp/lkp/src/bin/run-lkp /lkp/jobs/scheduled/vm-meta-300/boot-1-debian-11.1-x86_64-20220510.cgz-x86_64-randconfig-071-20230903-c6eefad61209-20230903-11038-o17p1l-0.yaml
[ 104.602900][ T165] kmemleak: Automatic memory scanning thread ended
[ OK ] Started System Logging Service.
[ 106.970306][ T310] is_virt=true
[ 106.970347][ T310]
[ 108.079565][ T310] lkp: kernel tainted state: 512
[ 108.079600][ T310]
[ 108.704632][ T310] LKP: stdout: 296: Kernel tests: Boot OK!
[ 108.704672][ T310]
[ 112.730026][ T310] LKP: stdout: 296: HOSTNAME vm-snb, MAC 52:54:00:12:34:56, kernel 6.5.0-10888-gc6eefad61209 1
[ 112.730070][ T310]
[ 112.732401][ T310] NO_NETWORK=
[ 112.732437][ T310]
[ 118.521298][ T310] LKP: stdout: 296: /lkp/lkp/src/bin/run-lkp /lkp/jobs/scheduled/vm-meta-300/boot-1-debian-11.1-x86_64-20220510.cgz-x86_64-randconfig-071-20230903-c6eefad61209-20230903-11038-o17p1l-0.yaml
[ 118.521368][ T310]
[ 118.537313][ T310] RESULT_ROOT=/result/boot/1/vm-snb/debian-11.1-x86_64-20220510.cgz/x86_64-randconfig-071-20230903/clang-16/c6eefad61209dab3de7446cf8151d38e70440484/0
[ 118.537382][ T310]
[ 118.542693][ T310] job=/lkp/jobs/scheduled/vm-meta-300/boot-1-debian-11.1-x86_64-20220510.cgz-x86_64-randconfig-071-20230903-c6eefad61209-20230903-11038-o17p1l-0.yaml
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230905/202309051442.bd6f9879-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-05 16:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 19:08 [PATCH] kernfs: implement custom llseek method to fix userspace regression Valentine Sinitsyn
2023-08-14 20:01 ` Dan Williams
2023-08-15 8:25 ` Valentin Sinitsyn
2023-08-15 15:48 ` Dan Williams
2023-08-17 18:53 ` Valentin Sinitsyn
2023-08-21 7:29 ` [RESEND PATCH v2 1/2] kernfs: sysfs: support custom llseek method for sysfs entries Valentine Sinitsyn
2023-08-21 7:29 ` [RESEND PATCH v2 2/2] PCI: implement custom llseek method for PCI resource entries in sysfs Valentine Sinitsyn
2023-08-21 19:55 ` Bjorn Helgaas
2023-08-22 7:51 ` [PATCH v3 1/2] kernfs: sysfs: support custom llseek method for sysfs entries Valentine Sinitsyn
2023-08-22 7:51 ` [PATCH v3 2/2] PCI: Implement custom llseek for sysfs resource entries Valentine Sinitsyn
2023-08-22 11:54 ` [PATCH v4 1/2] kernfs: sysfs: support custom llseek method for sysfs entries Valentine Sinitsyn
2023-08-22 11:54 ` [PATCH v4 2/2] PCI: Implement custom llseek for sysfs resource entries Valentine Sinitsyn
2023-08-22 17:43 ` kernel test robot
2023-08-23 12:58 ` [PATCH v5 1/2] kernfs: sysfs: support custom llseek method for sysfs entries Valentine Sinitsyn
2023-08-23 14:37 ` Greg Kroah-Hartman
2023-08-23 14:39 ` Greg Kroah-Hartman
2023-08-23 20:11 ` Valentin Sinitsyn
2023-08-23 12:58 ` [PATCH v5 2/2] PCI: Implement custom llseek for sysfs resource entries Valentine Sinitsyn
2023-08-25 14:10 ` kernel test robot
2023-08-28 7:22 ` Valentin Sinitsyn
2023-08-29 20:02 ` Bjorn Helgaas
2023-08-29 20:26 ` Bjorn Helgaas
2023-09-02 15:50 ` [PATCH v6 1/2] kernfs: sysfs: support custom llseek method for sysfs entries Valentine Sinitsyn
2023-09-05 7:02 ` kernel test robot [this message]
2023-09-08 13:49 ` [PATCH v7 " Valentine Sinitsyn
2023-09-08 13:49 ` [PATCH v7 2/2] PCI: Implement custom llseek for sysfs resource entries Valentine Sinitsyn
2023-09-08 13:56 ` [PATCH v8 1/2] kernfs: sysfs: support custom llseek method for sysfs entries Valentine Sinitsyn
2023-09-08 13:56 ` [PATCH v8 2/2] PCI: Implement custom llseek for sysfs resource entries Valentine Sinitsyn
2023-09-02 15:50 ` [PATCH v6 " Valentine Sinitsyn
2023-08-21 23:15 ` [RESEND PATCH v2 2/2] PCI: implement custom llseek method for PCI resource entries in sysfs kernel test robot
2023-08-22 8:09 ` Valentin Sinitsyn
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=202309051442.bd6f9879-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=tj@kernel.org \
--cc=valesini@yandex-team.ru \
/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