mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 4.13-rc2
Date: Wed, 19 Jul 2017 17:04:45 +0200	[thread overview]
Message-ID: <1500476685-4843-1-git-send-email-idryomov@gmail.com> (raw)

Hi Linus,

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:

  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)

are available in the git repository at:

  https://github.com/ceph/ceph-client.git tags/ceph-for-4.13-rc2

for you to fetch changes up to 7c40b22f6f84c98a1d36e6d0a4346e58f05e45d8:

  libceph: potential NULL dereference in ceph_msg_data_create() (2017-07-17 14:54:59 +0200)

----------------------------------------------------------------
A number of small fixes for -rc1 Luminous changes plus a readdir race
fix, marked for stable.

----------------------------------------------------------------
Arnd Bergmann (1):
      libceph: fix old style declaration warnings

Dan Carpenter (2):
      libceph: NULL deref on osdmap_apply_incremental() error path
      libceph: potential NULL dereference in ceph_msg_data_create()

Ilya Dryomov (3):
      libceph: set -EINVAL in one place in crush_decode()
      libceph: use alloc_pg_mapping() in __decode_pg_upmap_items()
      libceph: don't call encode_request_finish() on MOSDBackoff messages

Yan, Zheng (1):
      ceph: fix race in concurrent readdir

 fs/ceph/dir.c                      |  5 +++++
 include/linux/ceph/ceph_features.h |  8 ++++----
 net/ceph/messenger.c               |  6 ++++--
 net/ceph/osd_client.c              |  5 ++++-
 net/ceph/osdmap.c                  | 31 ++++++++++++++++---------------
 5 files changed, 33 insertions(+), 22 deletions(-)

                 reply	other threads:[~2017-07-19 15:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1500476685-4843-1-git-send-email-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®