[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACGdZY+3=Xraszi47K2e-Bx=3-d45=qKOgMrV3D1U3dbPjBTmg@mail.gmail.com>
Date: Mon, 21 Mar 2022 16:36:02 -0700
From: Khazhy Kumykov <khazhy@...gle.com>
To: Trond Myklebust <trondmy@...merspace.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
Cc: "jack@...e.cz" <jack@...e.cz>,
"amir73il@...il.com" <amir73il@...il.com>,
"bfields@...ldses.org" <bfields@...ldses.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jlayton@...nel.org" <jlayton@...nel.org>,
"chuck.lever@...cle.com" <chuck.lever@...cle.com>
Subject: Re: [PATCH RFC] nfsd: avoid recursive locking through fsnotify
On Mon, Mar 21, 2022 at 3:50 PM Trond Myklebust <trondmy@...merspace.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?
Download attachment "smime.p7s" of type "application/pkcs7-signature" (3999 bytes)
Powered by blists - more mailing lists