From: Ilya Dryomov <idryomov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Ceph fixes for 5.4-rc7
Date: Fri, 8 Nov 2019 16:58:53 +0100 [thread overview]
Message-ID: <20191108155853.23314-1-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit d6d5df1db6e9d7f8f76d2911707f7d5877251b02:
Linux 5.4-rc5 (2019-10-27 13:19:19 -0400)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-5.4-rc7
for you to fetch changes up to ff29fde84d1fc82f233c7da0daa3574a3942bec7:
ceph: return -EINVAL if given fsc mount option on kernel w/o support (2019-11-07 18:03:23 +0100)
----------------------------------------------------------------
Some late-breaking dentry handling fixes from Al and Jeff, a patch to
further restrict copy_file_range() to avoid potential data corruption
from Luis and a fix for !CONFIG_CEPH_FSCACHE kernels. Everything but
the fscache fix is marked for stable.
----------------------------------------------------------------
Al Viro (2):
ceph: fix RCU case handling in ceph_d_revalidate()
ceph: add missing check in d_revalidate snapdir handling
Jeff Layton (2):
ceph: don't try to handle hashed dentries in non-O_CREAT atomic_open
ceph: return -EINVAL if given fsc mount option on kernel w/o support
Luis Henriques (2):
ceph: fix use-after-free in __ceph_remove_cap()
ceph: don't allow copy_file_range when stripe_count != 1
fs/ceph/caps.c | 10 +++++-----
fs/ceph/dir.c | 15 ++++++++-------
fs/ceph/file.c | 15 +++++++++++++--
fs/ceph/inode.c | 1 +
fs/ceph/super.c | 11 ++++++++++-
5 files changed, 37 insertions(+), 15 deletions(-)
next reply other threads:[~2019-11-08 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 15:58 Ilya Dryomov [this message]
2019-11-08 21:50 ` pr-tracker-bot
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=20191108155853.23314-1-idryomov@gmail.com \
--to=idryomov@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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®