From: xiubli@redhat.com
To: jlayton@kernel.org, idryomov@gmail.com, ceph-devel@vger.kernel.org
Cc: mchangir@redhat.com, lhenriques@suse.de, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Xiubo Li <xiubli@redhat.com>
Subject: [PATCH v4 0/2] ceph: fix the use-after-free bug for file_lock
Date: Tue, 13 Dec 2022 20:11:01 +0800 [thread overview]
Message-ID: <20221213121103.213631-1-xiubli@redhat.com> (raw)
From: Xiubo Li <xiubli@redhat.com>
Changed in V4:
- repeat the afs in fs.h instead of adding ceph specific header file
Changed in V3:
- switched to vfs_inode_has_locks() helper to fix another ceph file lock
bug, thanks Jeff!
- this patch series is based on Jeff's previous VFS lock patch:
https://patchwork.kernel.org/project/ceph-devel/list/?series=695950
Changed in V2:
- switch to file_lock.fl_u to fix the race bug
- and the most code will be in the ceph layer
Xiubo Li (2):
ceph: switch to vfs_inode_has_locks() to fix file lock bug
ceph: add ceph specific member support for file_lock
fs/ceph/caps.c | 2 +-
fs/ceph/locks.c | 24 ++++++++++++++++++------
fs/ceph/super.h | 1 -
include/linux/fs.h | 3 +++
4 files changed, 22 insertions(+), 8 deletions(-)
--
2.31.1
next reply other threads:[~2022-12-13 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 12:11 xiubli [this message]
2022-12-13 12:11 ` [PATCH v4 1/2] ceph: switch to vfs_inode_has_locks() to fix file lock bug xiubli
2022-12-13 12:11 ` [PATCH v4 2/2] ceph: add ceph specific member support for file_lock xiubli
2022-12-13 18:05 ` Ilya Dryomov
2022-12-14 2:03 ` Xiubo Li
2022-12-13 12:47 ` [PATCH v4 0/2] ceph: fix the use-after-free bug " 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=20221213121103.213631-1-xiubli@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=lhenriques@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchangir@redhat.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
all inboxes | Powered by JetHome®