[v5.15] Internal error in __rseq_handle_notify_resume
2 views
Skip to first unread message
syzbot
Aug 12, 2025, 6:10:28 AM8/12/25
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=145415a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=b435439693ca168abb6f
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b43543...@syzkaller.appspotmail.com
Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4220 Comm: syz.3.23 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : rseq_get_rseq_cs_ptr_val kernel/rseq.c:131 [inline]
pc : rseq_get_rseq_cs kernel/rseq.c:153 [inline]
pc : rseq_ip_fixup kernel/rseq.c:266 [inline]
pc : __rseq_handle_notify_resume+0x264/0x1604 kernel/rseq.c:314
lr : rseq_get_rseq_cs_ptr_val kernel/rseq.c:131 [inline]
lr : rseq_get_rseq_cs kernel/rseq.c:153 [inline]
lr : rseq_ip_fixup kernel/rseq.c:266 [inline]
lr : __rseq_handle_notify_resume+0x240/0x1604 kernel/rseq.c:314
sp : ffff80001fd37ac0
x29: ffff80001fd37b80 x28: ffff700003fa6f60 x27: dfff800000000000
x26: 00000000fffffff2 x25: 0000000000000000 x24: ffff0000d905afa8
x23: ffff80001fd37b00 x22: 000000200004c800 x21: ffff0000d9059b64
x20: ffff0000d9059b40 x19: 1fffe0001b20b36c x18: 0000000000000000
x17: ffff800016d04000 x16: ffff8000086580cc x15: ffff8000088e21dc
x14: 00000000111b85b8 x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000000000000000 x10: 00000000200004c8 x9 : 0000ffffffffffff
x8 : 00000000200004c8 x7 : ffff800008750ed4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
rseq_get_rseq_cs_ptr_val kernel/rseq.c:131 [inline]
rseq_get_rseq_cs kernel/rseq.c:153 [inline]
rseq_ip_fixup kernel/rseq.c:266 [inline]
__rseq_handle_notify_resume+0x264/0x1604 kernel/rseq.c:314
rseq_handle_notify_resume include/linux/sched.h:2202 [inline]
tracehook_notify_resume include/linux/tracehook.h:201 [inline]
do_notify_resume+0x21f8/0x3128 arch/arm64/kernel/signal.c:949
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
el0_svc+0xf0/0x1e0 arch/arm64/kernel/entry-common.c:609
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: d503229f 2a1f03fa 2a1f03e0 f8400959 (2a1a03e1)
---[ end trace c056b811f2128ff1 ]---
----------------
Code disassembly (best guess):
0: d503229f csdb
4: 2a1f03fa mov w26, wzr
8: 2a1f03e0 mov w0, wzr
c: f8400959 ldtr x25, [x10]
* 10: 2a1a03e1 mov w1, w26 <-- trapping instruction
---
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 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: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=145415a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=b435439693ca168abb6f
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b43543...@syzkaller.appspotmail.com
Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4220 Comm: syz.3.23 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : rseq_get_rseq_cs_ptr_val kernel/rseq.c:131 [inline]
pc : rseq_get_rseq_cs kernel/rseq.c:153 [inline]
pc : rseq_ip_fixup kernel/rseq.c:266 [inline]
pc : __rseq_handle_notify_resume+0x264/0x1604 kernel/rseq.c:314
lr : rseq_get_rseq_cs_ptr_val kernel/rseq.c:131 [inline]
lr : rseq_get_rseq_cs kernel/rseq.c:153 [inline]
lr : rseq_ip_fixup kernel/rseq.c:266 [inline]
lr : __rseq_handle_notify_resume+0x240/0x1604 kernel/rseq.c:314
sp : ffff80001fd37ac0
x29: ffff80001fd37b80 x28: ffff700003fa6f60 x27: dfff800000000000
x26: 00000000fffffff2 x25: 0000000000000000 x24: ffff0000d905afa8
x23: ffff80001fd37b00 x22: 000000200004c800 x21: ffff0000d9059b64
x20: ffff0000d9059b40 x19: 1fffe0001b20b36c x18: 0000000000000000
x17: ffff800016d04000 x16: ffff8000086580cc x15: ffff8000088e21dc
x14: 00000000111b85b8 x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000000000000000 x10: 00000000200004c8 x9 : 0000ffffffffffff
x8 : 00000000200004c8 x7 : ffff800008750ed4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
rseq_get_rseq_cs_ptr_val kernel/rseq.c:131 [inline]
rseq_get_rseq_cs kernel/rseq.c:153 [inline]
rseq_ip_fixup kernel/rseq.c:266 [inline]
__rseq_handle_notify_resume+0x264/0x1604 kernel/rseq.c:314
rseq_handle_notify_resume include/linux/sched.h:2202 [inline]
tracehook_notify_resume include/linux/tracehook.h:201 [inline]
do_notify_resume+0x21f8/0x3128 arch/arm64/kernel/signal.c:949
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
el0_svc+0xf0/0x1e0 arch/arm64/kernel/entry-common.c:609
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: d503229f 2a1f03fa 2a1f03e0 f8400959 (2a1a03e1)
---[ end trace c056b811f2128ff1 ]---
----------------
Code disassembly (best guess):
0: d503229f csdb
4: 2a1f03fa mov w26, wzr
8: 2a1f03e0 mov w0, wzr
c: f8400959 ldtr x25, [x10]
* 10: 2a1a03e1 mov w1, w26 <-- trapping instruction
---
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 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
Aug 15, 2025, 7:07:29 PM8/15/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=114f93a2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b43543...@syzkaller.appspotmail.com
Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4242 Comm: syz.0.17 Not tainted 5.15.189-syzkaller #0
pc : rseq_ip_fixup kernel/rseq.c:276 [inline]
pc : __rseq_handle_notify_resume+0x89c/0x1604 kernel/rseq.c:314
lr : __uaccess_mask_ptr arch/arm64/include/asm/uaccess.h:244 [inline]
lr : clear_rseq_cs kernel/rseq.c:242 [inline]
lr : rseq_ip_fixup kernel/rseq.c:276 [inline]
lr : __rseq_handle_notify_resume+0x87c/0x1604 kernel/rseq.c:314
sp : ffff80001fde7ac0
x29: ffff80001fde7b80 x28: ffff700003fbcf60 x27: dfff800000000000
x26: 0000ffffb03c0f28 x25: 00000000fffffff2 x24: 0000002000004800
x23: 0000000020000048 x22: 0000000000000001 x21: ffff0000d4efd1e4
x20: ffff0000d4efd1c0 x19: 1fffe0001a9dfa3c x18: 0000000000000000
x17: 0000000000000000 x16: ffff800008658704 x15: 0000000000000000
x14: 0000000000000000 x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000000020000048 x10: 0000ffffffffffff x9 : 0000000020000048
x8 : 0000000000000000 x7 : ffff800008750ed4 x6 : 0000000000000000
rseq_ip_fixup kernel/rseq.c:276 [inline]
__rseq_handle_notify_resume+0x89c/0x1604 kernel/rseq.c:314
---[ end trace a3769c2da66744e1 ]---
4: d503229f csdb
8: aa1f03e8 mov x8, xzr
c: f8000968 sttr x8, [x11]
* 10: 14000105 b 0x424 <-- trapping instruction
---
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.
HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=b435439693ca168abb6f
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137d2234580000
dashboard link: https://syzkaller.appspot.com/bug?extid=b435439693ca168abb6f
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b43543...@syzkaller.appspotmail.com
Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : clear_rseq_cs kernel/rseq.c:-1 [inline]
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : rseq_ip_fixup kernel/rseq.c:276 [inline]
pc : __rseq_handle_notify_resume+0x89c/0x1604 kernel/rseq.c:314
lr : __uaccess_mask_ptr arch/arm64/include/asm/uaccess.h:244 [inline]
lr : clear_rseq_cs kernel/rseq.c:242 [inline]
lr : rseq_ip_fixup kernel/rseq.c:276 [inline]
lr : __rseq_handle_notify_resume+0x87c/0x1604 kernel/rseq.c:314
sp : ffff80001fde7ac0
x29: ffff80001fde7b80 x28: ffff700003fbcf60 x27: dfff800000000000
x26: 0000ffffb03c0f28 x25: 00000000fffffff2 x24: 0000002000004800
x23: 0000000020000048 x22: 0000000000000001 x21: ffff0000d4efd1e4
x20: ffff0000d4efd1c0 x19: 1fffe0001a9dfa3c x18: 0000000000000000
x17: 0000000000000000 x16: ffff800008658704 x15: 0000000000000000
x14: 0000000000000000 x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000000020000048 x10: 0000ffffffffffff x9 : 0000000020000048
x8 : 0000000000000000 x7 : ffff800008750ed4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
clear_rseq_cs kernel/rseq.c:242 [inline]
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
rseq_ip_fixup kernel/rseq.c:276 [inline]
__rseq_handle_notify_resume+0x89c/0x1604 kernel/rseq.c:314
rseq_handle_notify_resume include/linux/sched.h:2202 [inline]
tracehook_notify_resume include/linux/tracehook.h:201 [inline]
do_notify_resume+0x21f8/0x3128 arch/arm64/kernel/signal.c:949
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
el0_svc+0xf0/0x1e0 arch/arm64/kernel/entry-common.c:609
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 9a9f02eb d503229f aa1f03e8 f8000968 (14000105)
tracehook_notify_resume include/linux/tracehook.h:201 [inline]
do_notify_resume+0x21f8/0x3128 arch/arm64/kernel/signal.c:949
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
el0_svc+0xf0/0x1e0 arch/arm64/kernel/entry-common.c:609
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
---[ end trace a3769c2da66744e1 ]---
----------------
Code disassembly (best guess):
0: 9a9f02eb csel x11, x23, xzr, eq // eq = none
Code disassembly (best guess):
4: d503229f csdb
8: aa1f03e8 mov x8, xzr
c: f8000968 sttr x8, [x11]
* 10: 14000105 b 0x424 <-- trapping instruction
---
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.
syzbot
Aug 15, 2025, 10:00:33 PM8/15/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=120a53a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=121f2234580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b43543...@syzkaller.appspotmail.com
Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4264 Comm: syz.0.17 Not tainted 5.15.189-syzkaller #0
x29: ffff8000204c7b80 x28: ffff700004098f60 x27: dfff800000000000
x26: 0000ffffab1dff28 x25: 00000000fffffff2 x24: 0000002000004800
x23: 0000000020000048 x22: 0000000000000001 x21: ffff0000d18136a4
x20: ffff0000d1813680 x19: 1fffe0001a3026d4 x18: 0000000000000000
x17: 0000000000000000 x16: ffff800008658704 x15: 0000000000000000
x14: 0000000000000000 x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000000020000048 x10: 0000ffffffffffff x9 : 0000000020000048
x8 : 0000000000000000 x7 : ffff800008750ed4 x6 : 0000000000000000
HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=b435439693ca168abb6f
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=160a53a2580000
dashboard link: https://syzkaller.appspot.com/bug?extid=b435439693ca168abb6f
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=121f2234580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b43543...@syzkaller.appspotmail.com
Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : clear_rseq_cs kernel/rseq.c:-1 [inline]
pc : rseq_ip_fixup kernel/rseq.c:276 [inline]
pc : __rseq_handle_notify_resume+0x89c/0x1604 kernel/rseq.c:314
lr : __uaccess_mask_ptr arch/arm64/include/asm/uaccess.h:244 [inline]
lr : clear_rseq_cs kernel/rseq.c:242 [inline]
lr : rseq_ip_fixup kernel/rseq.c:276 [inline]
lr : __rseq_handle_notify_resume+0x87c/0x1604 kernel/rseq.c:314
sp : ffff8000204c7ac0
pc : rseq_ip_fixup kernel/rseq.c:276 [inline]
pc : __rseq_handle_notify_resume+0x89c/0x1604 kernel/rseq.c:314
lr : __uaccess_mask_ptr arch/arm64/include/asm/uaccess.h:244 [inline]
lr : clear_rseq_cs kernel/rseq.c:242 [inline]
lr : rseq_ip_fixup kernel/rseq.c:276 [inline]
lr : __rseq_handle_notify_resume+0x87c/0x1604 kernel/rseq.c:314
x29: ffff8000204c7b80 x28: ffff700004098f60 x27: dfff800000000000
x26: 0000ffffab1dff28 x25: 00000000fffffff2 x24: 0000002000004800
x23: 0000000020000048 x22: 0000000000000001 x21: ffff0000d18136a4
x20: ffff0000d1813680 x19: 1fffe0001a3026d4 x18: 0000000000000000
x17: 0000000000000000 x16: ffff800008658704 x15: 0000000000000000
x14: 0000000000000000 x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000000020000048 x10: 0000ffffffffffff x9 : 0000000020000048
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
clear_rseq_cs kernel/rseq.c:242 [inline]
rseq_ip_fixup kernel/rseq.c:276 [inline]
__rseq_handle_notify_resume+0x89c/0x1604 kernel/rseq.c:314
rseq_ip_fixup kernel/rseq.c:276 [inline]
rseq_handle_notify_resume include/linux/sched.h:2202 [inline]
tracehook_notify_resume include/linux/tracehook.h:201 [inline]
do_notify_resume+0x21f8/0x3128 arch/arm64/kernel/signal.c:949
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
el0_svc+0xf0/0x1e0 arch/arm64/kernel/entry-common.c:609
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
tracehook_notify_resume include/linux/tracehook.h:201 [inline]
do_notify_resume+0x21f8/0x3128 arch/arm64/kernel/signal.c:949
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
el0_svc+0xf0/0x1e0 arch/arm64/kernel/entry-common.c:609
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 9a9f02eb d503229f aa1f03e8 f8000968 (14000105)
---[ end trace af8d6d5235b80817 ]---
----------------
Code disassembly (best guess):
Code disassembly (best guess):
Reply all
Reply to author
Forward
0 new messages