From: syzbot <syzbot+8cbdf9aa6c281a4e6bbe@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: [PATCH] Fix warning empty list in svc_destroy
Date: Sun, 08 Nov 2026 06:08:21 -0800 [thread overview]
Message-ID: <6af08255.5a668245.1aceb6.000e.GAE@google.com> (raw)
In-Reply-To: <6aee17c4.8be4ead1.3b45e1.0199.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: [PATCH] Fix warning empty list in svc_destroy
Author: drifabdelmalekmohamedsaid@gmail.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
diff --git a/fs/nfs/callback.c b/fs/nfs/callback.c
index bc282b744f34..ebcca3dd1269 100644
--- a/fs/nfs/callback.c
+++ b/fs/nfs/callback.c
@@ -60,8 +60,15 @@ static int nfs4_callback_up_net(struct svc_serv *serv, struct net *net)
nn->nfs_callback_tcpport6 = ret;
dprintk("NFS: Callback listener port = %u (af %u, net %x)\n",
nn->nfs_callback_tcpport6, PF_INET6, net->ns.inum);
- } else if (ret != -EAFNOSUPPORT)
+ } else if (ret != -EAFNOSUPPORT) {
+ struct svc_xprt *xprt = svc_find_xprt(serv, "tcp", net, PF_INET,
+ nn->nfs_callback_tcpport);
+ if (xprt) {
+ svc_xprt_close(xprt);
+ svc_xprt_put(xprt);
+ }
goto out_err;
+ }
return 0;
out_err:
--
2.47.3
next prev parent reply other threads:[~2026-11-08 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 18:09 [syzbot] [net?] [nfs?] WARNING in svc_destroy syzbot
2026-11-08 5:52 ` [syzbot] [nfs?] [net?] " syzbot
2026-11-08 14:08 ` Forwarded: [PATCH] Fix warning empty list " syzbot
2026-11-08 14:08 ` syzbot [this message]
2026-11-08 18:42 ` Forwarded: Re: [syzbot] [net?] [nfs?] WARNING " 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=6af08255.5a668245.1aceb6.000e.GAE@google.com \
--to=syzbot+8cbdf9aa6c281a4e6bbe@syzkaller.appspotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.