From: Andrew Morton <akpm@linux-foundation.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/4] ocfs2: avoid inode removed while nfsd access it
Date: Wed, 17 Jun 2020 13:57:43 -0700 [thread overview]
Message-ID: <20200617135743.18d9a4add21acaac12da23d2@linux-foundation.org> (raw)
In-Reply-To: <b8f64191-74fc-0f15-affc-e8e518b17bd1@linux.alibaba.com>
On Wed, 17 Jun 2020 11:01:12 +0800 Joseph Qi <joseph.qi@linux.alibaba.com> wrote:
> On 2020/6/17 02:38, Junxiao Bi wrote:
> > When nfsd is getting file dentry using handle or parent dentry of some
> > dentry, one cluster lock is used to avoid inode removed from other node,
> > but it still could be removed from local node, so use a rw lock to avoid
> > this.
> >
> > Signed-off-by: Junxiao Bi <junxiao.bi@oracle.com>
>
> Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
Which kernel version(s) do we think need these four patches? 5.9?
5.8? 5.8 and -stable?
next prev parent reply other threads:[~2020-06-17 20:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 18:38 [Ocfs2-devel] [v2] ocfs2: fix nfsd over ocfs2 issues Junxiao Bi
2020-06-16 18:38 ` [Ocfs2-devel] [PATCH 1/4] ocfs2: avoid inode removed while nfsd access it Junxiao Bi
2020-06-17 3:01 ` Joseph Qi
2020-06-17 20:57 ` Andrew Morton [this message]
2020-06-17 22:56 ` Junxiao Bi
2020-06-16 18:38 ` [Ocfs2-devel] [PATCH 2/4] ocfs2: load global_inode_alloc Junxiao Bi
2020-06-17 3:03 ` Joseph Qi
2020-06-16 18:38 ` [Ocfs2-devel] [PATCH 3/4] ocfs2: fix panic on nfs server over ocfs2 Junxiao Bi
2020-06-17 3:10 ` Joseph Qi
2020-06-16 18:38 ` [Ocfs2-devel] [PATCH 4/4] ocfs2: fix value of OCFS2_INVALID_SLOT Junxiao Bi
2020-06-17 3:26 ` Joseph Qi
2020-07-02 8:48 ` Gang He
2020-07-02 14:13 ` Joseph Qi
2020-07-02 17:51 ` Junxiao Bi
2020-07-03 3:41 ` Gang He
2020-07-03 8:41 ` Gang He
2020-07-03 12:03 ` Joseph Qi
2020-07-03 13:12 ` Gang He
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=20200617135743.18d9a4add21acaac12da23d2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ocfs2-devel@oss.oracle.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;
as well as URLs for NNTP newsgroup(s).