public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Alex Lyakas <alex@zadara.com>
Cc: chuck.lever@oracle.com, linux-nfs@vger.kernel.org,
	Shyam Kaushik <shyam@zadara.com>
Subject: Re: [RFC-PATCH] nfsd: when unhashing openowners, increment openowner's refcount
Date: Mon, 26 Aug 2019 10:38:16 -0400	[thread overview]
Message-ID: <20190826143816.GD22759@fieldses.org> (raw)
In-Reply-To: <20190826133951.GC22759@fieldses.org>

On Mon, Aug 26, 2019 at 09:39:51AM -0400, J. Bruce Fields wrote:
> On Sun, Aug 25, 2019 at 01:12:34PM +0300, Alex Lyakas wrote:
> > You are listed as maintainers of nfsd. Can you please take a look at
> > the below patch?
> 
> Thanks!
> 
> I take it this was found by some kind of code analysis or fuzzing, not
> use in production?
> 
> Asking because I've been considering just deprecating it, so:

So, unless someone objects I'd like to queue this up for 5.4.

--b.

commit 9d60d93198c6
Author: J. Bruce Fields <bfields@redhat.com>
Date:   Mon Aug 26 10:28:58 2019 -0400

    Deprecate nfsd fault injection
    
    This is only useful for client testing.  I haven't really maintained it,
    and reference counting and locking are wrong at this point.  You can get
    some of the same functionality now from nfsd/clients/.
    
    It was a good idea but I think its time has passed.
    
    In the unlikely event of users, hopefully the BROKEN dependency will
    prompt them to speak up.  Otherwise I expect to remove it soon.
    
    Reported-by: Alex Lyakas <alex@zadara.com>
    Signed-off-by: J. Bruce Fields <bfields@redhat.com>

diff --git a/fs/nfsd/Kconfig b/fs/nfsd/Kconfig
index bff8456220e0..10cefb0c07c7 100644
--- a/fs/nfsd/Kconfig
+++ b/fs/nfsd/Kconfig
@@ -148,7 +148,7 @@ config NFSD_V4_SECURITY_LABEL
 
 config NFSD_FAULT_INJECTION
 	bool "NFS server manual fault injection"
-	depends on NFSD_V4 && DEBUG_KERNEL && DEBUG_FS
+	depends on NFSD_V4 && DEBUG_KERNEL && DEBUG_FS && BROKEN
 	help
 	  This option enables support for manually injecting faults
 	  into the NFS server.  This is intended to be used for

  reply	other threads:[~2019-08-26 14:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21 16:49 [RFC-PATCH] nfsd: when unhashing openowners, increment openowner's refcount Alex Lyakas
2019-08-25 10:12 ` Alex Lyakas
2019-08-26 13:39   ` J. Bruce Fields
2019-08-26 14:38     ` J. Bruce Fields [this message]
2019-08-27  9:05     ` Alex Lyakas
2019-08-27 20:51       ` J. Bruce Fields
2019-08-28 15:20         ` Alex Lyakas
2019-08-28 16:54           ` J. Bruce Fields
2019-08-29 18:12             ` Alex Lyakas
2019-08-30 19:08               ` J. Bruce Fields
2019-09-03 13:47                 ` Alex Lyakas
2019-08-30 19:54               ` J. Bruce Fields
2019-09-03 13:48                 ` Alex Lyakas

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=20190826143816.GD22759@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=alex@zadara.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=shyam@zadara.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