From: Trond Myklebust <trondmy@hammerspace.com>
To: "khazhy@google.com" <khazhy@google.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "jack@suse.cz" <jack@suse.cz>,
"chuck.lever@oracle.com" <chuck.lever@oracle.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"bfields@fieldses.org" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"amir73il@gmail.com" <amir73il@gmail.com>
Subject: Re: [PATCH RFC] nfsd: avoid recursive locking through fsnotify
Date: Mon, 21 Mar 2022 23:50:35 +0000 [thread overview]
Message-ID: <a9cf9bcd72a187127b73042a9369e17bd5a0e93d.camel@hammerspace.com> (raw)
In-Reply-To: <CACGdZY+3=Xraszi47K2e-Bx=3-d45=qKOgMrV3D1U3dbPjBTmg@mail.gmail.com>
On Mon, 2022-03-21 at 16:36 -0700, Khazhy Kumykov wrote:
> On Mon, Mar 21, 2022 at 3:50 PM Trond Myklebust
> <trondmy@hammerspace.com> wrote:
> >
> > As has already been reported, the problem was fixed in Linux 5.5 by
> > the
> > garbage collector rewrite, and so this is no longer an issue.
> >
> 9542e6a643fc ("nfsd: Containerise filecache laundrette"),
> 36ebbdb96b69
> ("nfsd: cleanup nfsd_file_lru_dispose()") apply cleanly to 5.4.y for
> me, which is still LTS. Since this should fix a real deadlock, would
> it be appropriate to include them for the 5.4 stable?
That would be OK with me. I'm not aware of any side-effects that might
be a problem for 5.4.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2022-03-21 23:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 0:16 Khazhismel Kumykov
2022-03-19 0:36 ` Trond Myklebust
2022-03-19 1:45 ` Khazhy Kumykov
2022-03-19 9:36 ` Amir Goldstein
2022-03-21 11:23 ` Jan Kara
2022-03-21 11:56 ` Amir Goldstein
2022-03-21 14:51 ` Jan Kara
2022-03-21 22:50 ` Trond Myklebust
2022-03-21 23:36 ` Khazhy Kumykov
2022-03-21 23:50 ` Trond Myklebust [this message]
2022-03-22 10:37 ` Jan Kara
2022-03-21 17:06 ` Khazhy Kumykov
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=a9cf9bcd72a187127b73042a9369e17bd5a0e93d.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=amir73il@gmail.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=khazhy@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
/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®