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.3-rc6
Date: Fri, 23 Aug 2019 14:27:26 +0200 [thread overview]
Message-ID: <20190823122726.15050-1-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit d1abaeb3be7b5fa6d7a1fbbd2e14e3310005c4c1:
Linux 5.3-rc5 (2019-08-18 14:31:08 -0700)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-5.3-rc6
for you to fetch changes up to a561372405cf6bc6f14239b3a9e57bb39f2788b0:
libceph: fix PG split vs OSD (re)connect race (2019-08-22 10:47:41 +0200)
----------------------------------------------------------------
Three important fixes tagged for stable (an indefinite hang, a crash on
an assert and a NULL pointer dereference) plus a small series from Luis
fixing instances of vfree() under spinlock.
----------------------------------------------------------------
Erqi Chen (1):
ceph: clear page dirty before invalidate page
Ilya Dryomov (1):
libceph: fix PG split vs OSD (re)connect race
Jeff Layton (1):
ceph: don't try fill file_lock on unsuccessful GETFILELOCK reply
Luis Henriques (4):
libceph: allow ceph_buffer_put() to receive a NULL ceph_buffer
ceph: fix buffer free while holding i_ceph_lock in __ceph_setxattr()
ceph: fix buffer free while holding i_ceph_lock in __ceph_build_xattrs_blob()
ceph: fix buffer free while holding i_ceph_lock in fill_inode()
fs/ceph/addr.c | 5 +++--
fs/ceph/caps.c | 5 ++++-
fs/ceph/inode.c | 7 ++++---
fs/ceph/locks.c | 3 +--
fs/ceph/snap.c | 4 +++-
fs/ceph/super.h | 2 +-
fs/ceph/xattr.c | 19 ++++++++++++++-----
include/linux/ceph/buffer.h | 3 ++-
net/ceph/osd_client.c | 9 ++++-----
9 files changed, 36 insertions(+), 21 deletions(-)
next reply other threads:[~2019-08-23 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 12:27 Ilya Dryomov [this message]
2019-08-23 16:45 ` 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=20190823122726.15050-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®