From: syzbot <syzbot+8cbdf9aa6c281a4e6bbe@syzkaller.appspotmail.com>
To: drifabdelmalekmohamedsaid@gmail.com,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nfs?] [net?] WARNING in svc_destroy
Date: Sun, 08 Nov 2026 06:39:02 -0800 [thread overview]
Message-ID: <6af08986.5a668245.1aceb6.000f.GAE@google.com> (raw)
In-Reply-To: <20261108140754.1057-1-drifabdelmalekmohamedsaid@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in svc_destroy
NFS: callback service start failed
------------[ cut here ]------------
SVC: permsocks remain for NFSv4 callback
WARNING: net/sunrpc/svc.c:532 at svc_destroy+0x299/0x330 net/sunrpc/svc.c:532, CPU#1: syz-executor246/6020
Modules linked in:
CPU: 1 UID: 0 PID: 6020 Comm: syz-executor246 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
RIP: 0010:svc_destroy+0x29d/0x330 net/sunrpc/svc.c:532
Code: 48 b8 00 00 00 00 00 fc ff df 49 8b 5d 00 48 8d 7b 18 48 89 fa 48 c1 ea 03 80 3c 02 00 75 67 48 8d 3d 07 5e 77 07 48 8b 73 18 <67> 48 0f b9 3a e9 d0 fd ff ff 48 8b 7c 24 08 e8 8f 2c 85 f7 e9 a5
RSP: 0018:ffffc9000327f858 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffffffff9040bf80 RCX: 0000000000000000
RDX: 1ffffffff20817f3 RSI: ffffffff8c37ebc0 RDI: ffffffff927b0770
RBP: 0000000000000000 R08: 00000000ffffffff R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffff888020732000
R13: ffff88802e69dc00 R14: ffff888038dc4000 R15: ffffffff9cd624c0
FS: 000055556db93400(0000) GS:ffff888122575000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055cc9adb7968 CR3: 000000005b735000 CR4: 00000000003526f0
Call Trace:
<TASK>
nfs_callback_up+0x511/0xb50 fs/nfs/callback.c:243
nfs4_init_callback fs/nfs/nfs4client.c:327 [inline]
nfs4_init_client_minor_version fs/nfs/nfs4client.c:379 [inline]
nfs4_init_client+0x236/0x420 fs/nfs/nfs4client.c:429
nfs_get_client+0xf38/0x1230 fs/nfs/client.c:467
nfs4_set_client+0x3f6/0x640 fs/nfs/nfs4client.c:763
nfs4_init_server.isra.0+0x5be/0xf80 fs/nfs/nfs4client.c:1014
nfs4_create_server+0x185/0x2b0 fs/nfs/nfs4client.c:1063
nfs4_try_get_tree+0x93/0x140 fs/nfs/nfs4super.c:228
nfs_get_tree+0xa61/0x1440 fs/nfs/fs_context.c:1621
vfs_get_tree+0x92/0x320 fs/super.c:1881
fc_mount fs/namespace.c:1282 [inline]
do_new_mount_fc fs/namespace.c:3910 [inline]
do_new_mount fs/namespace.c:3986 [inline]
path_mount+0x7d0/0x2850 fs/namespace.c:4337
do_mount fs/namespace.c:4350 [inline]
__do_sys_mount fs/namespace.c:4565 [inline]
__se_sys_mount fs/namespace.c:4542 [inline]
__x64_sys_mount+0x293/0x310 fs/namespace.c:4542
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f89d50d5f1a
Code: 48 c7 c2 d8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 d8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe2b5c7a48 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f89d50d5f1a
RDX: 00007f89d513403f RSI: 00007f89d5133ffe RDI: 00007f89d5134044
RBP: 0000000000000004 R08: 00007ffe2b5c7ac0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f89d5133ffe
R13: 0000000000001785 R14: 0000000000000801 R15: 00007ffe2b5c7ac0
</TASK>
----------------
Code disassembly (best guess):
0: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
7: fc ff df
a: 49 8b 5d 00 mov 0x0(%r13),%rbx
e: 48 8d 7b 18 lea 0x18(%rbx),%rdi
12: 48 89 fa mov %rdi,%rdx
15: 48 c1 ea 03 shr $0x3,%rdx
19: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1)
1d: 75 67 jne 0x86
1f: 48 8d 3d 07 5e 77 07 lea 0x7775e07(%rip),%rdi # 0x7775e2d
26: 48 8b 73 18 mov 0x18(%rbx),%rsi
* 2a: 67 48 0f b9 3a ud1 (%edx),%rdi <-- trapping instruction
2f: e9 d0 fd ff ff jmp 0xfffffe04
34: 48 8b 7c 24 08 mov 0x8(%rsp),%rdi
39: e8 8f 2c 85 f7 call 0xf7852ccd
3e: e9 .byte 0xe9
3f: a5 movsl %ds:(%rsi),%es:(%rdi)
Tested on:
commit: fa4ad798 Merge tag 'for-7.4-rc1-tag' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15b11409580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1cf189394a856f11
dashboard link: https://syzkaller.appspot.com/bug?extid=8cbdf9aa6c281a4e6bbe
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=10e11409580000
next parent reply other threads:[~2026-11-08 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261108140754.1057-1-drifabdelmalekmohamedsaid@gmail.com>
2026-11-08 14:39 ` syzbot [this message]
[not found] <20261108140816.1083-1-drifabdelmalekmohamedsaid@gmail.com>
2026-11-08 15:00 ` syzbot
2026-11-06 18:09 [syzbot] [net?] [nfs?] " syzbot
2026-11-08 5:52 ` [syzbot] [nfs?] [net?] " syzbot
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=6af08986.5a668245.1aceb6.000f.GAE@google.com \
--to=syzbot+8cbdf9aa6c281a4e6bbe@syzkaller.appspotmail.com \
--cc=drifabdelmalekmohamedsaid@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®