From: yangerkun <yangerkun@huawei.com>
To: <viro@zeniv.linux.org.uk>, <jlayton@kernel.org>, <neilb@suse.com>
Cc: <linux-fsdevel@vger.kernel.org>
Subject: [PATCH] locks: add locks_move_blocks in posix_lock_inode
Date: Mon, 1 Jun 2020 17:16:16 +0800 [thread overview]
Message-ID: <20200601091616.34137-1-yangerkun@huawei.com> (raw)
We forget to call locks_move_blocks in posix_lock_inode when try to
process same owner and different types.
Signed-off-by: yangerkun <yangerkun@huawei.com>
---
fs/locks.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/locks.c b/fs/locks.c
index b8a31c1c4fff..36bd2c221786 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -1282,6 +1282,7 @@ static int posix_lock_inode(struct inode *inode, struct file_lock *request,
if (!new_fl)
goto out;
locks_copy_lock(new_fl, request);
+ locks_move_blocks(new_fl, request);
request = new_fl;
new_fl = NULL;
locks_insert_lock_ctx(request, &fl->fl_list);
--
2.21.3
next reply other threads:[~2020-06-01 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 9:16 yangerkun [this message]
2020-06-01 23:10 ` [PATCH] locks: add locks_move_blocks in posix_lock_inode NeilBrown
2020-06-02 13:49 ` yangerkun
2020-06-02 15:56 ` Jeff Layton
2020-06-03 1:22 ` yangerkun
2020-06-03 10:34 ` Jeff Layton
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=20200601091616.34137-1-yangerkun@huawei.com \
--to=yangerkun@huawei.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@suse.com \
--cc=viro@zeniv.linux.org.uk \
/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).