Skip to content

Include link to PR page + more context for WARNING/BUG in emails #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Include link to PR page + more context for WARNING/BUG in emails #1

wants to merge 2 commits into from
+15 −3

Conversation

pv
Copy link
Contributor

@pv pv commented Sep 15, 2025

Add link to test PR page in sent email, so that the full test log can be
found if needed.

Getting kernel BUG:, WARNING: etc is generally no-go, so include more
context already in the email/post test summary.

Sending emails part is hard to test locally, but probably is OK.

IIUC, these changes would have to go to https://github.com/tedd-an/bzcafe to apply to the kernel test bot.

Example output (in case of lots of warnings):

Test Summary:
TestRunner_iso-tester         FAIL      68.56 seconds

Details
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
WARNING: suspicious RCU usage
6.16.0-rc6-01737-gb9b65e1e560f #655 Not tainted
-----------------------------
./include/net/bluetooth/hci_core.h:1540 wrong hci_conn* locking!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
3 locks held by kworker/u5:0/44:
 #0: ffff888002755140 ((wq_completion)hci0#2){+.+.}-{0:0}, at: process_one_work+0xc3b/0x13c0
 #1: ffff8880019afd98 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_one_work+0x78b/0x13c0
 #2: ffff8880020f8da8 (&hdev->req_lock){+.+.}-{4:4}, at: hci_cmd_sync_work+0x117/0x380

stack backtrace:
CPU: 0 UID: 0 PID: 44 Comm: kworker/u5:0 Not tainted 6.16.0-rc6-01737-gb9b65e1e560f #655 PREEMPT(none) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014
Workqueue: hci0 hci_cmd_sync_work
Call Trace:
 <TASK>
 dump_stack_lvl+0x3a/0x60
 lockdep_rcu_suspicious.cold+0x55/0x93
 hci_lookup_le_connect+0x22e/0x310
 hci_update_passive_scan_sync+0x39f/0x730
 hci_cmd_sync_work+0x156/0x380
 process_one_work+0x7ed/0x13c0
 ? __pfx_process_one_work+0x10/0x10
 ? lock_acquire+0xf2/0x2a0
 ? lock_is_held_type+0x84/0xf0
 ? assign_work+0x151/0x390
 worker_thread+0x601/0xff0
 ? __pfx_worker_thread+0x10/0x10
 kthread+0x3a5/0x760
 ? lockdep_hardirqs_on_prepare+0xd0/0x180
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x362/0x4d0
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x19/0x30
WARNING: suspicious RCU usage
6.16.0-rc6-01737-gb9b65e1e560f #655 Not tainted
-----------------------------
./include/net/bluetooth/hci_core.h:1342 wrong hci_conn* locking!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
3 locks held by kworker/u5:0/44:
 #0: ffff888002755140 ((wq_completion)hci0#2){+.+.}-{0:0}, at: process_one_work+0xc3b/0x13c0
 #1: ffff8880019afd98 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_one_work+0x78b/0x13c0
 #2: ffff8880020f8da8 (&hdev->req_lock){+.+.}-{4:4}, at: hci_cmd_sync_work+0x117/0x380

stack backtrace:
CPU: 0 UID: 0 PID: 44 Comm: kworker/u5:0 Not tainted 6.16.0-rc6-01737-gb9b65e1e560f #655 PREEMPT(none) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014
Workqueue: hci0 hci_cmd_sync_work
Call Trace:
 <TASK>
 dump_stack_lvl+0x3a/0x60
 lockdep_rcu_suspicious.cold+0x55/0x93
 set_cig_params_sync+0x304/0xe70
 ? lock_acquire+0xf2/0x2a0
 ? hci_cmd_sync_work+0x117/0x380
 ? __pfx_set_cig_params_sync+0x10/0x10
 ? __pfx___might_resched+0x10/0x10
 ? kasan_quarantine_put+0xcf/0x220
 ? kfree+0xf8/0x320
 hci_cmd_sync_work+0x156/0x380
 process_one_work+0x7ed/0x13c0
 ? __pfx_process_one_work+0x10/0x10
 ? lock_acquire+0xf2/0x2a0
 ? lock_is_held_type+0x84/0xf0
 ? assign_work+0x151/0x390
 worker_thread+0x601/0xff0
 ? __pfx_worker_thread+0x10/0x10
 kthread+0x3a5/0x760
 ? lockdep_hardirqs_on_prepare+0xd0/0x180
 ? __pfx_kthread+0x10/0x10
...
WARNING: suspicious RCU usage
6.16.0-rc6-01737-gb9b65e1e560f #655 Not tainted
-----------------------------
./include/net/bluetooth/hci_core.h:1308 wrong hci_conn* locking!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
3 locks held by kworker/u5:0/44:
 #0: ffff888002755140 ((wq_completion)hci0#2){+.+.}-{0:0}, at: process_one_work+0xc3b/0x13c0
 #1: ffff8880019afd98 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_one_work+0x78b/0x13c0
 #2: ffff8880020f8da8 (&hdev->req_lock){+.+.}-{4:4}, at: hci_cmd_sync_work+0x117/0x380

stack backtrace:
CPU: 0 UID: 0 PID: 44 Comm: kworker/u5:0 Not tainted 6.16.0-rc6-01737-gb9b65e1e560f #655 PREEMPT(none) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014
Workqueue: hci0 hci_cmd_sync_work
Call Trace:
 <TASK>
 dump_stack_lvl+0x3a/0x60
 lockdep_rcu_suspicious.cold+0x55/0x93
 set_cig_params_sync+0xac4/0xe70
 ? __pfx_set_cig_params_sync+0x10/0x10
 ? __pfx___might_resched+0x10/0x10
 ? kasan_quarantine_put+0xcf/0x220
 ? kfree+0xf8/0x320
 hci_cmd_sync_work+0x156/0x380
 process_one_work+0x7ed/0x13c0
 ? __pfx_process_one_work+0x10/0x10
 ? lock_acquire+0xf2/0x2a0
 ? lock_is_held_type+0x84/0xf0
 ? assign_work+0x151/0x390
 worker_thread+0x601/0xff0
 ? __pfx_worker_thread+0x10/0x10
 kthread+0x3a5/0x760
 ? lockdep_hardirqs_on_prepare+0xd0/0x180
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x362/0x4d0
 ? __pfx_kthread+0x10/0x10
...
WARNING: suspicious RCU usage
6.16.0-rc6-01737-gb9b65e1e560f #655 Not tainted
-----------------------------
./include/net/bluetooth/hci_core.h:1117 wrong hci_conn* locking!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
3 locks held by kworker/u5:0/44:
 #0: ffff888002755140 ((wq_completion)hci0#2){+.+.}-{0:0}, at: process_one_work+0xc3b/0x13c0
 #1: ffff8880019afd98 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_one_work+0x78b/0x13c0
 #2: ffff8880020f8da8 (&hdev->req_lock){+.+.}-{4:4}, at: hci_cmd_sync_work+0x117/0x380

stack backtrace:
CPU: 0 UID: 0 PID: 44 Comm: kworker/u5:0 Not tainted 6.16.0-rc6-01737-gb9b65e1e560f #655 PREEMPT(none) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014
Workqueue: hci0 hci_cmd_sync_work
Call Trace:
 <TASK>
 dump_stack_lvl+0x3a/0x60
 lockdep_rcu_suspicious.cold+0x55/0x93
 hci_conn_valid+0x1c1/0x280
 hci_le_create_conn_sync+0x105/0x24b0
 ? lock_acquire+0xf2/0x2a0
 ? __pfx_hci_le_create_conn_sync+0x10/0x10
 ? __pfx___might_resched+0x10/0x10
 ? lockdep_hardirqs_on_prepare+0xd0/0x180
 ? __mutex_lock+0x2aa/0x1830
 ? __lock_acquire+0x47e/0x2610
 ? hci_cmd_sync_work+0x117/0x380
 ? hci_cmd_sync_work+0xd6/0x380
 ? __pfx___mutex_lock+0x10/0x10
 ? __pfx___mutex_unlock_slowpath+0x10/0x10
 hci_cmd_sync_work+0x156/0x380
 process_one_work+0x7ed/0x13c0
 ? process_one_work+0x817/0x13c0
 ? __pfx_process_one_work+0x10/0x10
 ? lock_acquire+0xf2/0x2a0
 ? lock_is_held_type+0x84/0xf0
...
WARNING: suspicious RCU usage
6.16.0-rc6-01737-gb9b65e1e560f #655 Not tainted
-----------------------------
./include/net/bluetooth/hci_core.h:1117 wrong hci_conn* locking!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
3 locks held by kworker/u5:2/46:
 #0: ffff888002755140 ((wq_completion)hci0#2){+.+.}-{0:0}, at: process_one_work+0xc3b/0x13c0
 #1: ffff888001cafd98 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_one_work+0x78b/0x13c0
 #2: ffff8880020f8da8 (&hdev->req_lock){+.+.}-{4:4}, at: hci_cmd_sync_work+0x117/0x380

stack backtrace:
CPU: 0 UID: 0 PID: 46 Comm: kworker/u5:2 Not tainted 6.16.0-rc6-01737-gb9b65e1e560f #655 PREEMPT(none) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014
Workqueue: hci0 hci_cmd_sync_work
Call Trace:
 <TASK>
 dump_stack_lvl+0x3a/0x60
 lockdep_rcu_suspicious.cold+0x55/0x93
 abort_conn_sync+0x201/0x2e0
 hci_cmd_sync_work+0x156/0x380
 process_one_work+0x7ed/0x13c0
 ? process_one_work+0x817/0x13c0
 ? __pfx_process_one_work+0x10/0x10
 ? lock_acquire+0xf2/0x2a0
 ? lock_is_held_type+0x84/0xf0
 ? assign_work+0x151/0x390
 worker_thread+0x601/0xff0
 ? __pfx_worker_thread+0x10/0x10
 ? __kthread_parkme+0x8a/0x2b0
 ? __pfx_worker_thread+0x10/0x10
 ? __pfx_worker_thread+0x10/0x10
 kthread+0x3a5/0x760
 ? lockdep_hardirqs_on_prepare+0xd0/0x180
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x362/0x4d0
 ? __pfx_kthread+0x10/0x10
...
WARNING: suspicious RCU usage
6.16.0-rc6-01737-gb9b65e1e560f #655 Not tainted
-----------------------------
./include/net/bluetooth/hci_core.h:1236 wrong hci_conn* locking!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
2 locks held by kworker/u5:2/188:
 #0: ffff888002755940 ((wq_completion)hci0#2){+.+.}-{0:0}, at: process_one_work+0xc3b/0x13c0
 #1: ffff888001d1fd98 ((work_completion)(&hdev->rx_work)){+.+.}-{0:0}, at: process_one_work+0x78b/0x13c0

stack backtrace:
CPU: 0 UID: 0 PID: 188 Comm: kworker/u5:2 Not tainted 6.16.0-rc6-01737-gb9b65e1e560f #655 PREEMPT(none) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014
Workqueue: hci0 hci_rx_work
Call Trace:
 <TASK>
 dump_stack_lvl+0x3a/0x60
 lockdep_rcu_suspicious.cold+0x55/0x93
 hci_num_comp_pkts_evt+0x484/0xaf0
 hci_event_packet+0x7ba/0xee0
 ? __pfx_hci_num_comp_pkts_evt+0x10/0x10
 ? __pfx_hci_event_packet+0x10/0x10
 ? mark_held_locks+0x40/0x70
 ? trace_hardirqs_on+0x17/0xd0
 hci_rx_work+0x672/0x1510
 ? lock_release+0xcf/0x290
 process_one_work+0x7ed/0x13c0
 ? __pfx_process_one_work+0x10/0x10
 ? lock_acquire+0xf2/0x2a0
 ? lock_is_held_type+0x84/0xf0
 ? assign_work+0x151/0x390
 worker_thread+0x601/0xff0
 ? __pfx_worker_thread+0x10/0x10
 ? __kthread_parkme+0x8a/0x2b0
 ? __pfx_worker_thread+0x10/0x10
 ? __pfx_worker_thread+0x10/0x10
 kthread+0x3a5/0x760
...
WARNING: suspicious RCU usage
6.16.0-rc6-01737-gb9b65e1e560f #655 Not tainted
-----------------------------
./include/net/bluetooth/hci_core.h:1280 wrong hci_conn* locking!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
3 locks held by kworker/u5:0/225:
 #0: ffff888001328140 ((wq_completion)hci0){+.+.}-{0:0}, at: process_one_work+0xc3b/0x13c0
 #1: ffff888001d1fd98 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_one_work+0x78b/0x13c0
 #2: ffff8880023e4da8 (&hdev->req_lock){+.+.}-{4:4}, at: hci_cmd_sync_work+0x117/0x380

stack backtrace:
CPU: 0 UID: 0 PID: 225 Comm: kworker/u5:0 Not tainted 6.16.0-rc6-01737-gb9b65e1e560f #655 PREEMPT(none) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014
Workqueue: hci0 hci_cmd_sync_work
Call Trace:
 <TASK>
 dump_stack_lvl+0x3a/0x60
 lockdep_rcu_suspicious.cold+0x55/0x93
 hci_passive_scan_sync+0x663/0x1b30
 ? __pfx_hci_passive_scan_sync+0x10/0x10
 ? hci_lookup_le_connect+0x31/0x310
 ? find_held_lock+0x2b/0x80
 ? hci_lookup_le_connect+0x16c/0x310
 ? lock_release+0xcf/0x290
 hci_update_passive_scan_sync+0x3bd/0x730
 hci_cmd_sync_work+0x156/0x380
 process_one_work+0x7ed/0x13c0
 ? __pfx_process_one_work+0x10/0x10
 ? lock_acquire+0xf2/0x2a0
 ? lock_is_held_type+0x84/0xf0
 ? assign_work+0x151/0x390
 worker_thread+0x601/0xff0
 ? __pfx_worker_thread+0x10/0x10
 kthread+0x3a5/0x760
 ? lockdep_hardirqs_on_prepare+0xd0/0x180
 ? __pfx_kthread+0x10/0x10
...
WARNING: suspicious RCU usage
6.16.0-rc6-01737-gb9b65e1e560f #655 Not tainted
-----------------------------
./include/net/bluetooth/hci_core.h:1182 wrong hci_conn* locking!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
3 locks held by kworker/u5:0/343:
 #0: ffff888002365940 ((wq_completion)hci0){+.+.}-{0:0}, at: process_one_work+0xc3b/0x13c0
 #1: ffff8880019ffd98 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_one_work+0x78b/0x13c0
 #2: ffff888001ed0da8 (&hdev->req_lock){+.+.}-{4:4}, at: hci_cmd_sync_work+0x117/0x380

stack backtrace:
CPU: 0 UID: 0 PID: 343 Comm: kworker/u5:0 Not tainted 6.16.0-rc6-01737-gb9b65e1e560f #655 PREEMPT(none) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014
Workqueue: hci0 hci_cmd_sync_work
Call Trace:
 <TASK>
 dump_stack_lvl+0x3a/0x60
 lockdep_rcu_suspicious.cold+0x55/0x93
 hci_passive_scan_sync+0x1506/0x1b30
 ? __pfx_hci_passive_scan_sync+0x10/0x10
 ? hci_lookup_le_connect+0x31/0x310
 ? find_held_lock+0x2b/0x80
 ? hci_lookup_le_connect+0x16c/0x310
 ? lock_release+0xcf/0x290
 hci_update_passive_scan_sync+0x3bd/0x730
 hci_le_pa_create_sync+0x12b/0x5c0
 ? __pfx_hci_le_pa_create_sync+0x10/0x10
 hci_cmd_sync_work+0x156/0x380
 process_one_work+0x7ed/0x13c0
 ? __pfx_process_one_work+0x10/0x10
 ? lock_acquire+0xf2/0x2a0
 ? lock_is_held_type+0x84/0xf0
 ? assign_work+0x151/0x390
 worker_thread+0x601/0xff0
 ? __pfx_worker_thread+0x10/0x10
 kthread+0x3a5/0x760
...
Total: 135, Passed: 135 (100.0%), Failed: 0, Not Run: 0

pv added 2 commits September 15, 2025 22:41
@pv
Include link to PR page in emails, for full logs
c10fa11 
Add link to test PR page in sent email, so that the full test log can be
found if needed.
@pv
Include more context for kernel BUG/WARNING/etc
da217e3 
Getting kernel BUG:, WARNING: etc is generally no-go, so include more
context already in the email/post test summary.
@pv pv changed the title Ci improve Include link to PR page + more context for WARNING/BUG in emails Sep 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@pv