From: Jeff Layton <jlayton@kernel.org>
To: Maninder Singh <maninder1.s@samsung.com>,
chuck.lever@oracle.com, neilb@suse.de, okorniev@redhat.com,
Dai.Ngo@oracle.com, tom@talpey.com, lorenzo@kernel.org
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
chungki0201.woo@samsung.com
Subject: Re: [PATCH 1/2] NFSD: unregister filesystem in case genl_register_family() fails
Date: Fri, 07 Mar 2025 06:07:47 -0500 [thread overview]
Message-ID: <77acf3fbd9946522d1b18a6e8a05000465b72f40.camel@kernel.org> (raw)
In-Reply-To: <20250306092007.1419237-1-maninder1.s@samsung.com>
On Thu, 2025-03-06 at 14:50 +0530, Maninder Singh wrote:
> With rpc_status netlink support, unregister of register_filesystem()
> was missed in case of genl_register_family() fails.
>
> Correcting it by making new label.
>
> Fixes: bd9d6a3efa97 ("NFSD: add rpc_status netlink support")
> Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
> ---
> fs/nfsd/nfsctl.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd/nfsctl.c
> index ac265d6fde35..d773481bcf10 100644
> --- a/fs/nfsd/nfsctl.c
> +++ b/fs/nfsd/nfsctl.c
> @@ -2305,7 +2305,7 @@ static int __init init_nfsd(void)
> goto out_free_cld;
> retval = register_filesystem(&nfsd_fs_type);
> if (retval)
> - goto out_free_all;
> + goto out_free_nfsd4;
> retval = genl_register_family(&nfsd_nl_family);
> if (retval)
> goto out_free_all;
> @@ -2313,6 +2313,8 @@ static int __init init_nfsd(void)
>
> return 0;
> out_free_all:
> + unregister_filesystem(&nfsd_fs_type);
> +out_free_nfsd4:
> nfsd4_destroy_laundry_wq();
> out_free_cld:
> unregister_cld_notifier();
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-03-07 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250306092017epcas5p30812b135b484fdea1f96739635df1d79@epcas5p3.samsung.com>
2025-03-06 9:20 ` [PATCH 1/2] NFSD: unregister filesystem in case genl_register_family() fails Maninder Singh
2025-03-06 9:20 ` [PATCH 2/2] NFSD: fix race between nfsd registration and exports_proc Maninder Singh
2025-03-06 12:08 ` Jeff Layton
2025-03-07 3:29 ` Maninder Singh
2025-03-07 11:08 ` Jeff Layton
2025-03-07 11:07 ` Jeff Layton [this message]
2025-03-07 14:09 ` [PATCH 1/2] NFSD: unregister filesystem in case genl_register_family() fails cel
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=77acf3fbd9946522d1b18a6e8a05000465b72f40.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=chungki0201.woo@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=maninder1.s@samsung.com \
--cc=neilb@suse.de \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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