From: Andrea Amorosi <andrea.amorosi76@gmail.com>
To: lists@sapience.com
Cc: dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
linux-kernel@vger.kernel.org, lucas.demarchi@intel.com,
regressions@lists.linux.dev, rostedt@goodmis.org,
stable@vger.kernel.org, thomas.hellstrom@linux.intel.com
Subject: [REGRESSION][BISECTED] Re: 6.12.7 stable new error: event xe_bo_move has unsafe dereference of argument 4
Date: Sat, 4 Jan 2025 18:43:09 +0100 [thread overview]
Message-ID: <73129e45-cf51-4e8d-95e8-49bc39ebc246@gmail.com> (raw)
In-Reply-To: <9dee19b6185d325d0e6fa5f7cbba81d007d99166.camel@sapience.com>
Hi to all,
I've just updated my archlinux to |6.12.8-arch1-1 and I still get the
same issue:|
|gen 04 18:01:34 D9330 kernel: ------------[ cut here ]------------
gen 04 18:01:34 D9330 kernel: WARNING: CPU: 2 PID: 209 at
kernel/trace/trace_events.c:577 trace_event_raw_init+0x159/0x660
gen 04 18:01:34 D9330 kernel: Modules linked in: xe(+) drm_ttm_helper
gpu_sched drm_suballoc_helper drm_gpuvm drm_exec uas usb_storage i915
i2c_algo_bit drm_buddy ttm serio_raw atkbd intel>
gen 04 18:01:34 D9330 kernel: CPU: 2 UID: 0 PID: 209 Comm: (udev-worker)
Not tainted 6.12.8-arch1-1 #1 099de49ddaebb26408f097c48b36e50b2c8e21c9
gen 04 18:01:34 D9330 kernel: Hardware name: Dell Inc. Latitude
9330/0RN079, BIOS 1.25.0 11/12/2024
gen 04 18:01:34 D9330 kernel: RIP: 0010:trace_event_raw_init+0x159/0x660
gen 04 18:01:34 D9330 kernel: Code: 89 ea 0f 83 3b 04 00 00 e8 44 db ff
ff 84 c0 74 10 8b 0c 24 48 c7 c0 fe ff ff ff 48 d3 c0 49 21 c6 4d 85 f6
0f 84 d6 fe ff ff <0f> 0b bb 01 00 00 00 41 >
gen 04 18:01:34 D9330 kernel: RSP: 0018:ffffa9b940987730 EFLAGS: 00010206
gen 04 18:01:34 D9330 kernel: RAX: ffffffffffffffdf RBX:
ffffffffc0ca4731 RCX: 0000000000000005
gen 04 18:01:34 D9330 kernel: RDX: 0000000000000002 RSI:
0000000000000001 RDI: ffffffffc0ca4727
gen 04 18:01:34 D9330 kernel: RBP: ffffffffc0ca4640 R08:
0000000000000039 R09: 0000000000000000
gen 04 18:01:34 D9330 kernel: R10: 0000000000000076 R11:
000000000000004e R12: 00000000000000f2
gen 04 18:01:34 D9330 kernel: R13: ffffffffc0ca5760 R14:
0000000000000018 R15: 0000000000000000
gen 04 18:01:34 D9330 kernel: FS: 00007ba0e9fe9880(0000)
GS:ffff9d957f500000(0000) knlGS:0000000000000000
gen 04 18:01:34 D9330 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
gen 04 18:01:34 D9330 kernel: CR2: 00007ba0e9dac000 CR3:
00000001019ac000 CR4: 0000000000f50ef0
gen 04 18:01:34 D9330 kernel: PKRU: 55555554
gen 04 18:01:34 D9330 kernel: Call Trace:
gen 04 18:01:34 D9330 kernel: <TASK>
gen 04 18:01:34 D9330 kernel: ? trace_event_raw_init+0x159/0x660
gen 04 18:01:34 D9330 kernel: ? __warn.cold+0x93/0xf6
gen 04 18:01:34 D9330 kernel: ? trace_event_raw_init+0x159/0x660
gen 04 18:01:34 D9330 kernel: ? report_bug+0xff/0x140
gen 04 18:01:34 D9330 kernel: ? handle_bug+0x58/0x90
gen 04 18:01:34 D9330 kernel: ? exc_invalid_op+0x17/0x70
gen 04 18:01:34 D9330 kernel: ? asm_exc_invalid_op+0x1a/0x20
gen 04 18:01:34 D9330 kernel: ? trace_event_raw_init+0x159/0x660
gen 04 18:01:34 D9330 kernel: event_init+0x28/0x70
gen 04 18:01:34 D9330 kernel: trace_module_notify+0x1a4/0x260
gen 04 18:01:34 D9330 kernel: notifier_call_chain+0x5a/0xd0
gen 04 18:01:34 D9330 kernel: blocking_notifier_call_chain_robust+0x65/0xc0
gen 04 18:01:34 D9330 kernel: load_module+0x1822/0x1cf0
gen 04 18:01:34 D9330 kernel: ? vmap+0x83/0xe0
gen 04 18:01:34 D9330 kernel: ? __vunmap_range_noflush+0x325/0x470
gen 04 18:01:34 D9330 kernel: ? init_module_from_file+0x89/0xe0
gen 04 18:01:34 D9330 kernel: init_module_from_file+0x89/0xe0
gen 04 18:01:34 D9330 kernel: idempotent_init_module+0x11e/0x310
gen 04 18:01:34 D9330 kernel: __x64_sys_finit_module+0x5e/0xb0
gen 04 18:01:34 D9330 kernel: do_syscall_64+0x82/0x190
gen 04 18:01:34 D9330 kernel: ? vfs_read+0x299/0x370
gen 04 18:01:34 D9330 kernel: ? syscall_exit_to_user_mode+0x37/0x1c0
gen 04 18:01:34 D9330 kernel: ? do_syscall_64+0x8e/0x190
gen 04 18:01:34 D9330 kernel: ? terminate_walk+0xee/0x100
gen 04 18:01:34 D9330 kernel: ? path_openat+0x495/0x12e0
gen 04 18:01:34 D9330 kernel: ? syscall_exit_to_user_mode+0x37/0x1c0
gen 04 18:01:34 D9330 kernel: ? do_syscall_64+0x8e/0x190
gen 04 18:01:34 D9330 kernel: ? do_filp_open+0xc4/0x170
gen 04 18:01:34 D9330 kernel: ? __pfx_page_put_link+0x10/0x10
gen 04 18:01:34 D9330 kernel: ? do_sys_openat2+0x9c/0xe0
gen 04 18:01:34 D9330 kernel: ? syscall_exit_to_user_mode+0x37/0x1c0
gen 04 18:01:34 D9330 kernel: ? do_syscall_64+0x8e/0x190
gen 04 18:01:34 D9330 kernel: ? do_syscall_64+0x8e/0x190
gen 04 18:01:34 D9330 kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e
gen 04 18:01:34 D9330 kernel: RIP: 0033:0x7ba0ea7e01fd
gen 04 18:01:34 D9330 kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00
90 f3 0f 1e fa 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 73 01 >
gen 04 18:01:34 D9330 kernel: RSP: 002b:00007ffe5dee8d58 EFLAGS:
00000246 ORIG_RAX: 0000000000000139
gen 04 18:01:34 D9330 kernel: RAX: ffffffffffffffda RBX:
00005f717b3029c0 RCX: 00007ba0ea7e01fd
gen 04 18:01:34 D9330 kernel: RDX: 0000000000000004 RSI:
00007ba0e9fe305d RDI: 0000000000000031
gen 04 18:01:34 D9330 kernel: RBP: 00007ffe5dee8e10 R08:
0000000000000001 R09: 00007ffe5dee8da0
gen 04 18:01:34 D9330 kernel: R10: 0000000000000040 R11:
0000000000000246 R12: 00007ba0e9fe305d
gen 04 18:01:34 D9330 kernel: R13: 0000000000020000 R14:
00005f717b303600 R15: 00005f717b304360
gen 04 18:01:34 D9330 kernel: </TASK>
gen 04 18:01:34 D9330 kernel: ---[ end trace 0000000000000000 ]---
gen 04 18:01:34 D9330 kernel: event xe_bo_move has unsafe dereference of
argument 4
gen 04 18:01:34 D9330 kernel: print_fmt: "move_lacks_source:%s, migrate
object %p [size %zu] from %s to %s device_id:%s", REC->move_lacks_source
? "yes" : "no", REC->bo, REC->size, xe_mem_>|
|
|
|Later I get this other one which I do not know if it is related to the
previous one or not:|
|gen 04 18:01:45 D9330 kernel: ------------[ cut here ]------------
gen 04 18:01:45 D9330 kernel: WARNING: CPU: 7 PID: 139 at
drivers/usb/typec/ucsi/ucsi.c:1361 ucsi_reset_ppm+0x1b4/0x1c0 [typec_ucsi]
gen 04 18:01:45 D9330 kernel: Modules linked in: fat kvm_intel
snd_soc_core mei_vsc snd_compress spi_pxa2xx_platform intel_ishtp_hid
iwlmvm dell_rbtn hid_multitouch dw_dmac ac97_bus moused>
gen 04 18:01:45 D9330 kernel: processor_thermal_rapl cfg80211 ucsi_acpi
soundcore mei_me intel_rapl_common intel_lpss_pci i2c_mux typec_ucsi
thunderbolt intel_lpss mei processor_thermal_w>
gen 04 18:01:45 D9330 kernel: video cec spi_intel nvme_auth i8042 wmi serio
gen 04 18:01:45 D9330 kernel: CPU: 7 UID: 0 PID: 139 Comm: kworker/7:1
Tainted: G W OE 6.12.8-arch1-1 #1
099de49ddaebb26408f097c48b36e50b2c8e21c9
gen 04 18:01:45 D9330 kernel: Tainted: [W]=WARN, [O]=OOT_MODULE,
[E]=UNSIGNED_MODULE
gen 04 18:01:45 D9330 kernel: Hardware name: Dell Inc. Latitude
9330/0RN079, BIOS 1.25.0 11/12/2024
gen 04 18:01:45 D9330 kernel: Workqueue: events_long ucsi_init_work
[typec_ucsi]
gen 04 18:01:45 D9330 kernel: RIP: 0010:ucsi_reset_ppm+0x1b4/0x1c0
[typec_ucsi]
gen 04 18:01:45 D9330 kernel: Code: 8b 44 24 04 a9 00 00 00 08 0f 85 36
ff ff ff 4c 89 74 24 10 48 8b 05 cb be 59 cf 49 39 c5 79 8f bb 92 ff ff
ff e9 1b ff ff ff <0f> 0b e9 50 ff ff ff e8 >
gen 04 18:01:45 D9330 kernel: RSP: 0018:ffffa9b9407bfda8 EFLAGS: 00010206
gen 04 18:01:45 D9330 kernel: RAX: 0000000008000000 RBX:
0000000000000000 RCX: 0000000000000002
gen 04 18:01:45 D9330 kernel: RDX: 00000000fffeaba3 RSI:
ffffa9b9407bfdac RDI: ffff9d92089d7800
gen 04 18:01:45 D9330 kernel: RBP: ffff9d92089d7800 R08:
0000000000000000 R09: 0000000000000014
gen 04 18:01:45 D9330 kernel: R10: 0000000000000001 R11:
0000000000000000 R12: ffffa9b9407bfdac
gen 04 18:01:45 D9330 kernel: R13: 00000000fffeaba0 R14:
ffff9d92089d7860 R15: ffff9d92089d78c0
gen 04 18:01:45 D9330 kernel: FS: 0000000000000000(0000)
GS:ffff9d957f780000(0000) knlGS:0000000000000000
gen 04 18:01:45 D9330 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
gen 04 18:01:45 D9330 kernel: CR2: 0000585143bba648 CR3:
000000023a822000 CR4: 0000000000f50ef0
gen 04 18:01:45 D9330 kernel: PKRU: 55555554
gen 04 18:01:45 D9330 kernel: Call Trace:
gen 04 18:01:45 D9330 kernel: <TASK>
gen 04 18:01:45 D9330 kernel: ? ucsi_reset_ppm+0x1b4/0x1c0 [typec_ucsi
97866a6a8562a088cda45de0ae83658868b451bb]
gen 04 18:01:45 D9330 kernel: ? __warn.cold+0x93/0xf6
gen 04 18:01:45 D9330 kernel: ? ucsi_reset_ppm+0x1b4/0x1c0 [typec_ucsi
97866a6a8562a088cda45de0ae83658868b451bb]
gen 04 18:01:45 D9330 kernel: ? report_bug+0xff/0x140
gen 04 18:01:45 D9330 kernel: ? handle_bug+0x58/0x90
gen 04 18:01:45 D9330 kernel: ? exc_invalid_op+0x17/0x70
gen 04 18:01:45 D9330 kernel: ? asm_exc_invalid_op+0x1a/0x20
gen 04 18:01:45 D9330 kernel: ? ucsi_reset_ppm+0x1b4/0x1c0 [typec_ucsi
97866a6a8562a088cda45de0ae83658868b451bb]
gen 04 18:01:45 D9330 kernel: ? ucsi_reset_ppm+0xc6/0x1c0 [typec_ucsi
97866a6a8562a088cda45de0ae83658868b451bb]
gen 04 18:01:45 D9330 kernel: ucsi_init_work+0x3c/0xac0 [typec_ucsi
97866a6a8562a088cda45de0ae83658868b451bb]
gen 04 18:01:45 D9330 kernel: process_one_work+0x17b/0x330
gen 04 18:01:45 D9330 kernel: worker_thread+0x2ce/0x3f0
gen 04 18:01:45 D9330 kernel: ? __pfx_worker_thread+0x10/0x10
gen 04 18:01:45 D9330 kernel: kthread+0xcf/0x100
gen 04 18:01:45 D9330 kernel: ? __pfx_kthread+0x10/0x10
gen 04 18:01:45 D9330 kernel: ret_from_fork+0x31/0x50
gen 04 18:01:45 D9330 kernel: ? __pfx_kthread+0x10/0x10
gen 04 18:01:45 D9330 kernel: ret_from_fork_asm+0x1a/0x30
gen 04 18:01:45 D9330 kernel: </TASK>
gen 04 18:01:45 D9330 kernel: ---[ end trace 0000000000000000 ]---
|
|
|
|
|
next prev parent reply other threads:[~2025-01-04 17:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 16:15 6.12.7 stable new error: event xe_bo_move has unsafe dereference of argument 4 Genes Lists
2024-12-30 18:55 ` [REGRESSION][BISECTED] " Genes Lists
2024-12-30 19:13 ` Steven Rostedt
2024-12-30 19:50 ` Steven Rostedt
2024-12-30 20:20 ` Genes Lists
2024-12-30 20:52 ` Genes Lists
2024-12-30 21:03 ` Steven Rostedt
2024-12-30 21:07 ` Genes Lists
2025-01-01 20:55 ` Thomas Hellström
2025-01-02 1:49 ` Steven Rostedt
2025-01-04 17:43 ` Andrea Amorosi [this message]
2025-01-04 20:09 ` Genes Lists
2025-01-06 19:41 ` Steven Rostedt
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=73129e45-cf51-4e8d-95e8-49bc39ebc246@gmail.com \
--to=andrea.amorosi76@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@sapience.com \
--cc=lucas.demarchi@intel.com \
--cc=regressions@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=thomas.hellstrom@linux.intel.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