[v6.6] WARNING: ODEBUG bug in __sk_destruct
7 views
Skip to first unread message
syzbot
Jul 19, 2025, 12:11:34 AM7/19/25
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d96eb99e2f0e Linux 6.6.99
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15d63d8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bfd82343ac39d3b
dashboard link: https://syzkaller.appspot.com/bug?extid=da929776599376f1eb20
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13d63d8c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17d63d8c580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ed8b69e685f/disk-d96eb99e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bb6aa73497a7/vmlinux-d96eb99e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f864bab34183/bzImage-d96eb99e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+da9297...@syzkaller.appspotmail.com
------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff88805f6d85a0 object type: work_struct hint: kcm_tx_work+0x0/0x180
WARNING: CPU: 1 PID: 6186 at lib/debugobjects.c:518 debug_print_object lib/debugobjects.c:515 [inline]
WARNING: CPU: 1 PID: 6186 at lib/debugobjects.c:518 __debug_check_no_obj_freed lib/debugobjects.c:990 [inline]
WARNING: CPU: 1 PID: 6186 at lib/debugobjects.c:518 debug_check_no_obj_freed+0x446/0x540 lib/debugobjects.c:1020
Modules linked in:
CPU: 1 PID: 6186 Comm: syz.2.60 Not tainted 6.6.99-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:debug_print_object lib/debugobjects.c:515 [inline]
RIP: 0010:__debug_check_no_obj_freed lib/debugobjects.c:990 [inline]
RIP: 0010:debug_check_no_obj_freed+0x446/0x540 lib/debugobjects.c:1020
Code: 4c 8b 4d 00 48 c7 c7 40 70 fc 8a 48 c7 c6 a0 6c fc 8a 48 c7 c2 c0 71 fc 8a 8b 0c 24 4d 89 f8 41 55 e8 0e a5 2a fd 48 83 c4 08 <0f> 0b 4c 8b 6c 24 18 48 b9 00 00 00 00 00 fc ff df ff 05 e3 4b 25
RSP: 0018:ffffc900043afc28 EFLAGS: 00010286
RAX: 35047bfc1a743f00 RBX: ffffffff970e40b8 RCX: ffff888018b15a00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: ffffffff8aa9e760 R08: ffffc900043af827 R09: 1ffff92000875f04
R10: dffffc0000000000 R11: fffff52000875f05 R12: ffff88805f6d86b8
R13: ffffffff899e16b0 R14: ffff88805f6d8000 R15: ffff88805f6d85a0
FS: 00007fc465bbd6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc465bbcf98 CR3: 000000007bdca000 CR4: 00000000003506e0
Call Trace:
<TASK>
slab_free_hook mm/slub.c:1781 [inline]
slab_free_freelist_hook+0xd2/0x1b0 mm/slub.c:1832
slab_free mm/slub.c:3816 [inline]
kmem_cache_free+0xf8/0x280 mm/slub.c:3838
sk_prot_free net/core/sock.c:2128 [inline]
__sk_destruct+0x485/0x620 net/core/sock.c:2222
kcm_release+0x524/0x5b0 net/kcm/kcmsock.c:1738
__sock_release net/socket.c:659 [inline]
sock_close+0xbd/0x230 net/socket.c:1421
__fput+0x234/0x970 fs/file_table.c:384
__do_sys_close fs/open.c:1571 [inline]
__se_sys_close+0x15f/0x220 fs/open.c:1556
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fc465d8e9a9
Code: ff ff 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 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc465bbd038 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: ffffffffffffffda RBX: 00007fc465fb6160 RCX: 00007fc465d8e9a9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000006
RBP: 00007fc465e10d69 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007fc465fb6160 R15: 00007ffd28a1a688
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: d96eb99e2f0e Linux 6.6.99
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15d63d8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bfd82343ac39d3b
dashboard link: https://syzkaller.appspot.com/bug?extid=da929776599376f1eb20
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13d63d8c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17d63d8c580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ed8b69e685f/disk-d96eb99e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bb6aa73497a7/vmlinux-d96eb99e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f864bab34183/bzImage-d96eb99e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+da9297...@syzkaller.appspotmail.com
------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff88805f6d85a0 object type: work_struct hint: kcm_tx_work+0x0/0x180
WARNING: CPU: 1 PID: 6186 at lib/debugobjects.c:518 debug_print_object lib/debugobjects.c:515 [inline]
WARNING: CPU: 1 PID: 6186 at lib/debugobjects.c:518 __debug_check_no_obj_freed lib/debugobjects.c:990 [inline]
WARNING: CPU: 1 PID: 6186 at lib/debugobjects.c:518 debug_check_no_obj_freed+0x446/0x540 lib/debugobjects.c:1020
Modules linked in:
CPU: 1 PID: 6186 Comm: syz.2.60 Not tainted 6.6.99-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:debug_print_object lib/debugobjects.c:515 [inline]
RIP: 0010:__debug_check_no_obj_freed lib/debugobjects.c:990 [inline]
RIP: 0010:debug_check_no_obj_freed+0x446/0x540 lib/debugobjects.c:1020
Code: 4c 8b 4d 00 48 c7 c7 40 70 fc 8a 48 c7 c6 a0 6c fc 8a 48 c7 c2 c0 71 fc 8a 8b 0c 24 4d 89 f8 41 55 e8 0e a5 2a fd 48 83 c4 08 <0f> 0b 4c 8b 6c 24 18 48 b9 00 00 00 00 00 fc ff df ff 05 e3 4b 25
RSP: 0018:ffffc900043afc28 EFLAGS: 00010286
RAX: 35047bfc1a743f00 RBX: ffffffff970e40b8 RCX: ffff888018b15a00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: ffffffff8aa9e760 R08: ffffc900043af827 R09: 1ffff92000875f04
R10: dffffc0000000000 R11: fffff52000875f05 R12: ffff88805f6d86b8
R13: ffffffff899e16b0 R14: ffff88805f6d8000 R15: ffff88805f6d85a0
FS: 00007fc465bbd6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc465bbcf98 CR3: 000000007bdca000 CR4: 00000000003506e0
Call Trace:
<TASK>
slab_free_hook mm/slub.c:1781 [inline]
slab_free_freelist_hook+0xd2/0x1b0 mm/slub.c:1832
slab_free mm/slub.c:3816 [inline]
kmem_cache_free+0xf8/0x280 mm/slub.c:3838
sk_prot_free net/core/sock.c:2128 [inline]
__sk_destruct+0x485/0x620 net/core/sock.c:2222
kcm_release+0x524/0x5b0 net/kcm/kcmsock.c:1738
__sock_release net/socket.c:659 [inline]
sock_close+0xbd/0x230 net/socket.c:1421
__fput+0x234/0x970 fs/file_table.c:384
__do_sys_close fs/open.c:1571 [inline]
__se_sys_close+0x15f/0x220 fs/open.c:1556
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fc465d8e9a9
Code: ff ff 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 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc465bbd038 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: ffffffffffffffda RBX: 00007fc465fb6160 RCX: 00007fc465d8e9a9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000006
RBP: 00007fc465e10d69 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007fc465fb6160 R15: 00007ffd28a1a688
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Jul 23, 2025, 4:40:32 PM7/23/25
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: c79648372d02 Linux 5.15.189
syzbot found the following issue on:
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13bd80a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b1215b3cf4119f
dashboard link: https://syzkaller.appspot.com/bug?extid=b3516f29a6148448df3c
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1772ff22580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17bd80a2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8f7ef907dd63/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c9fa50894c6f/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/78f74ec5a263/bzImage-c7964837.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
------------[ cut here ]------------
ODEBUG: free active (active state 0) object type: work_struct hint: kcm_tx_work+0x0/0x180
WARNING: CPU: 1 PID: 4410 at lib/debugobjects.c:521 debug_print_object lib/debugobjects.c:518 [inline]
WARNING: CPU: 1 PID: 4410 at lib/debugobjects.c:521 __debug_check_no_obj_freed lib/debugobjects.c:973 [inline]
WARNING: CPU: 1 PID: 4410 at lib/debugobjects.c:521 debug_check_no_obj_freed+0x43c/0x530 lib/debugobjects.c:1003
Modules linked in:
CPU: 1 PID: 4410 Comm: syz.0.38 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:debug_print_object lib/debugobjects.c:518 [inline]
RIP: 0010:__debug_check_no_obj_freed lib/debugobjects.c:973 [inline]
RIP: 0010:debug_check_no_obj_freed+0x43c/0x530 lib/debugobjects.c:1003
Code: ef e8 08 54 dd fd 4c 8b 45 00 48 c7 c7 60 9c 59 8a 48 c7 c6 20 99 59 8a 48 c7 c2 c0 9d 59 8a 8b 0c 24 4d 89 e9 e8 74 94 be 05 <0f> 0b 4c 8b 6c 24 18 48 b9 00 00 00 00 00 fc ff df ff 05 d5 ce 8a
RSP: 0018:ffffc900012efbc0 EFLAGS: 00010246
RAX: f7f459898a686700 RBX: ffffffff96349490 RCX: ffff888078563b80
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffffff8a0a45e0 R08: dffffc0000000000 R09: fffff5200025dedd
R10: fffff5200025dedd R11: 1ffff9200025dedc R12: ffff88807a1e2b00
R13: ffffffff88f32a40 R14: ffff88807a1e2000 R15: ffff88807a1e29e8
FS: 00007fc2fcca46c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc2fcca3f98 CR3: 0000000074cac000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
slab_free_hook mm/slub.c:1680 [inline]
slab_free_freelist_hook+0x8b/0x170 mm/slub.c:1731
slab_free mm/slub.c:3499 [inline]
kmem_cache_free+0x8f/0x210 mm/slub.c:3515
sk_prot_free net/core/sock.c:1898 [inline]
__sk_destruct+0x54b/0x820 net/core/sock.c:1986
kcm_release+0x51a/0x5b0 net/kcm/kcmsock.c:1861
__sock_release net/socket.c:649 [inline]
sock_close+0xd5/0x240 net/socket.c:1336
__fput+0x234/0x930 fs/file_table.c:311
task_work_run+0x125/0x1a0 kernel/task_work.c:188
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x10f/0x130 kernel/entry/common.c:181
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fc2fda769a9
Code: ff ff 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 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc2fcca4038 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 00007fc2fdc9e160 RCX: 00007fc2fda769a9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000006
RBP: 00007fc2fdaf8d69 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007fc2fdc9e160 R15: 00007fff737700d8
syzbot
Aug 2, 2025, 2:15:30 PM8/2/25
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 3594f306da12 Linux 6.1.147
syzbot found the following issue on:
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13a89f82580000
kernel config: https://syzkaller.appspot.com/x/.config?x=30b8ca4950f83e04
dashboard link: https://syzkaller.appspot.com/bug?extid=49b2d54a43d3c362f038
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17a89f82580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=111b0aa2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/688153744f3f/disk-3594f306.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bed731de048a/vmlinux-3594f306.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f514506edb44/bzImage-3594f306.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
------------[ cut here ]------------
ODEBUG: free active (active state 0) object type: work_struct hint: kcm_tx_work+0x0/0x180
WARNING: CPU: 1 PID: 4695 at lib/debugobjects.c:518 __debug_check_no_obj_freed lib/debugobjects.c:979 [inline]
WARNING: CPU: 1 PID: 4695 at lib/debugobjects.c:518 debug_check_no_obj_freed+0x43c/0x530 lib/debugobjects.c:1009
Modules linked in:
CPU: 1 PID: 4695 Comm: syz.1.64 Not tainted 6.1.147-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:debug_print_object lib/debugobjects.c:515 [inline]
RIP: 0010:__debug_check_no_obj_freed lib/debugobjects.c:979 [inline]
RIP: 0010:debug_check_no_obj_freed+0x43c/0x530 lib/debugobjects.c:1009
Code: ef e8 e8 fd c5 fd 4c 8b 45 00 48 c7 c7 80 fc de 8a 48 c7 c6 40 f9 de 8a 48 c7 c2 e0 fd de 8a 8b 0c 24 4d 89 e9 e8 84 03 42 fd <0f> 0b 4c 8b 6c 24 18 48 b9 00 00 00 00 00 fc ff df ff 05 d5 9a 14
RSP: 0018:ffffc900045efb50 EFLAGS: 00010246
RAX: 59fe1881d17ddf00 RBX: ffffffff96e3e120 RCX: ffff888026eb9dc0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: ffffffff8a8b3700 R08: dffffc0000000000 R09: fffff520008bdef9
R10: fffff520008bdef9 R11: 1ffff920008bdef8 R12: ffff888024a9c7f8
R13: ffffffff894df300 R14: ffff888024a9c000 R15: ffff888024a9c6e0
FS: 00007f175eba26c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f175eba2d58 CR3: 00000000766e2000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
slab_free_hook mm/slub.c:1699 [inline]
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
slab_free_freelist_hook+0xd2/0x1a0 mm/slub.c:1750
slab_free mm/slub.c:3661 [inline]
kmem_cache_free+0xf7/0x290 mm/slub.c:3683
sk_prot_free net/core/sock.c:2084 [inline]
__sk_destruct+0x48d/0x630 net/core/sock.c:2172
kcm_release+0x520/0x5b0 net/kcm/kcmsock.c:1860
__sock_release net/socket.c:654 [inline]
sock_close+0xd5/0x240 net/socket.c:1400
__fput+0x22c/0x920 fs/file_table.c:320
task_work_run+0x1ca/0x250 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:303
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f175dd8eb69
Code: ff ff 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 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f175eba2038 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 00007f175dfb6160 RCX: 00007f175dd8eb69
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000006
RBP: 00007f175de11df1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f175dfb6160 R15: 00007ffd8c43d628
Reply all
Reply to author
Forward
0 new messages