linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: xiubli@redhat.com
To: ceph-devel@vger.kernel.org, jlayton@kernel.org,
	idryomov@gmail.com, viro@zeniv.linux.org.uk
Cc: lhenriques@suse.de, mchangir@redhat.com,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Xiubo Li <xiubli@redhat.com>
Subject: [PATCH 0/2 v2] ceph: fix the use-after-free bug for file_lock
Date: Mon, 14 Nov 2022 13:18:59 +0800	[thread overview]
Message-ID: <20221114051901.15371-1-xiubli@redhat.com> (raw)

From: Xiubo Li <xiubli@redhat.com>

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: add ceph_lock_info support for file_lock
  ceph: use a xarray to record all the opened files for each inode

 fs/ceph/file.c                  |  9 +++++++++
 fs/ceph/inode.c                 |  4 ++++
 fs/ceph/locks.c                 | 35 +++++++++++++++++++++++++++++----
 fs/ceph/super.h                 |  4 ++++
 include/linux/ceph/ceph_fs_fl.h | 26 ++++++++++++++++++++++++
 include/linux/fs.h              |  2 ++
 6 files changed, 76 insertions(+), 4 deletions(-)
 create mode 100644 include/linux/ceph/ceph_fs_fl.h

-- 
2.31.1


             reply	other threads:[~2022-11-14  5:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14  5:18 xiubli [this message]
2022-11-14  5:19 ` [PATCH 1/2 v2] ceph: add ceph_lock_info support for file_lock xiubli
2022-11-14 11:24   ` Jeff Layton
2022-11-14 13:00     ` Xiubo Li
2022-11-14  5:19 ` [PATCH 2/2 v2] ceph: use a xarray to record all the opened files for each inode xiubli
2022-11-14  8:54   ` kernel test robot
2022-11-14 13:08     ` Xiubo Li
2022-11-14 13:39   ` Jeff Layton
2022-11-14 13:46     ` Xiubo Li

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=20221114051901.15371-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;
as well as URLs for NNTP newsgroup(s).