From: Jeff Layton <jlayton@kernel.org>
To: NeilBrown <neilb@suse.de>, Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Subject: Re: [PATCH 0/2] nfsd: fix handling of error from unshare_fs_struct()
Date: Mon, 29 Jul 2024 08:44:35 -0400 [thread overview]
Message-ID: <2a4b6699d513d3664a57c76e1aa6da2beb4c6393.camel@kernel.org> (raw)
In-Reply-To: <20240729022126.4450-1-neilb@suse.de>
On Mon, 2024-07-29 at 12:18 +1000, NeilBrown wrote:
> These two patches replace my previous patch:
> [PATCH 07/14] Change unshare_fs_struct() to never fail.
>
> I had explored ways to change kthread_create() to avoid the need for
> GFP_NOFAIL and concluded that we can do everything we need in the
> sunrpc
> layer. So the first patch here is a simple cleanup, and the second
> adds
> simple infrastructure for an svc thread to confirm that it has
> started
> up and to report if it was successful in that.
>
> Thanks,
> NeilBrown
>
>
>
> [PATCH 1/2] sunrpc: merge svc_rqst_alloc() into svc_prepare_thread()
> [PATCH 2/2] sunrpc: allow svc threads to fail initialisation cleanly
I like this solution better:
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2024-07-29 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 2:18 [PATCH 0/2] nfsd: fix handling of error from unshare_fs_struct() NeilBrown
2024-07-29 2:18 ` [PATCH 1/2] sunrpc: merge svc_rqst_alloc() into svc_prepare_thread() NeilBrown
2024-07-29 2:18 ` [PATCH 2/2] sunrpc: allow svc threads to fail initialisation cleanly NeilBrown
2024-07-29 12:44 ` Jeff Layton [this message]
2024-07-29 14:36 ` [PATCH 0/2] nfsd: fix handling of error from unshare_fs_struct() Chuck Lever
2024-07-29 21:07 ` NeilBrown
2024-07-29 21:25 ` Chuck Lever III
2024-07-29 23:17 ` NeilBrown
2024-07-29 22:01 ` Christoph Hellwig
2024-07-30 0:43 ` NeilBrown
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=2a4b6699d513d3664a57c76e1aa6da2beb4c6393.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--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