search for: deref_stack_reg

...? dev_set_rx_mode+0x30/0x30 > [ 7.275857] ? do_raw_spin_unlock+0x54/0x220 > [ 7.275866] __dev_change_flags+0x3a9/0x4f0 > [ 7.275873] ? dev_set_allmulti+0x10/0x10 > [ 7.275889] dev_change_flags+0x7a/0x150 > [ 7.275900] do_setlink+0x9fe/0x2e40 > [ 7.275910] ? deref_stack_reg+0xad/0xe0 > [ 7.275917] ? __read_once_size_nocheck.constprop.6+0x10/0x10 > [ 7.275922] ? find_held_lock+0x32/0x1c0 > [ 7.275929] ? rtnetlink_put_metrics+0x460/0x460 > [ 7.275935] ? virtqueue_add_sgs+0x9e2/0xde0 > [ 7.275953] ? virtscsi_add_cmd+0x454/0x780 > [...

...ile-priva Not tainted 5.5.0-rc5+ #194 [ 98.859206] Hardware name: ASUS X299-A/PRIME X299-A, BIOS 1401 05/21/2018 [ 98.866030] Call Trace: [ 98.868493] dump_stack+0x96/0xe0 [ 98.871835] check_noncircular+0x2a0/0x2e0 [ 98.875954] ? print_circular_bug.isra.36+0x100/0x100 [ 98.881022] ? deref_stack_reg+0x8d/0xd0 [ 98.884958] ? rcu_read_lock_held_common+0x3e/0x90 [ 98.889784] ? stack_access_ok+0x35/0x80 [ 98.893727] ? mark_lock+0xac/0x9f0 [ 98.897221] ? rcu_read_lock_sched_held+0x5f/0xd0 [ 98.901962] __lock_acquire+0x1696/0x21a0 [ 98.906001] ? ftrace_caller_op_ptr+0xe/0xe [ 98....

...x,%rax,1) So in most scenarios, there's a mismatch between what vmlinux shows and the actual runtime code. This mismatch hurts debuggability and makes the assembly code harder to understand. It also causes the ORC unwinder to produce KASAN warnings like: BUG: KASAN: stack-out-of-bounds in deref_stack_reg+0x123/0x140 This warning is due to the fact that objtool doesn't know about parainstructions, so it doesn't know about the "pushfq; pop %rax" sequence above. Prepare to fix both of these issues (debuggability and ORC KASAN warnings) by adding a paravirt alternatives infrastructu...

This fixes the extra issues I discovered upstream after the introduction of my rework of the atomic VCPI helpers that occur during suspend/resume. This time around, we use a slightly different but much less complicated approach for fixing said issues. Cc: Daniel Vetter <daniel at ffwll.ch> Lyude Paul (4): drm/dp_mst: Fix unbalanced malloc ref in drm_dp_mst_deallocate_vcpi()

This fixes the extra issues I discovered upstream after the introduction of my rework of the atomic VCPI helpers that occur during suspend/resume. This time around, we use a slightly different but much less complicated approach for fixing said issues. Cc: Daniel Vetter <daniel at ffwll.ch> Lyude Paul (4): drm/dp_mst: Fix unbalanced malloc ref in drm_dp_mst_deallocate_vcpi()

This changes the pv ops code generation to more closely match reality. For example, instead of: callq *0xffffffff81e3a400 (pv_irq_ops.save_fl) vmlinux will now show: pushfq pop %rax nop nop nop nop nop which is what the runtime version of the code will show in most cases. This idea was suggested by Andy Lutomirski. The benefits are: - For the most common runtime cases

This changes the pv ops code generation to more closely match reality. For example, instead of: callq *0xffffffff81e3a400 (pv_irq_ops.save_fl) vmlinux will now show: pushfq pop %rax nop nop nop nop nop which is what the runtime version of the code will show in most cases. This idea was suggested by Andy Lutomirski. The benefits are: - For the most common runtime cases