linux-kernel - [GIT PULL] Ceph fixes for 2.6.39-rc7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.1105041316490.748@cobra.newdream.net>
Date:	Wed, 4 May 2011 13:18:34 -0700 (PDT)
From:	Sage Weil <sage@...dream.net>
To:	torvalds@...ux-foundation.org
cc:	linux-kernel@...r.kernel.org, ceph-devel@...r.kernel.org
Subject: [GIT PULL] Ceph fixes for 2.6.39-rc7

Hi Linus,

Please pull the following Ceph fixes from

  git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus

There are some error paths that weren't handling ENOMEM properly, and a 
few more locking fixes that are fallout from Dave's inode_lock->i_lock 
changes.

Thanks!
sage


Henry C Chang (2):
      libceph: fix ceph_msg_new error path
      ceph: handle ceph_osdc_new_request failure in ceph_writepages_start

Sage Weil (3):
      ceph: use ihold() when i_lock is held
      libceph: fix ceph_osdc_alloc_request error checks
      ceph: do not call __mark_dirty_inode under i_lock

 drivers/block/rbd.c   |    4 ++--
 fs/ceph/addr.c        |    7 +++++++
 fs/ceph/caps.c        |   14 +++++++-------
 fs/ceph/file.c        |    5 ++++-
 fs/ceph/inode.c       |    6 +++++-
 fs/ceph/super.h       |    2 +-
 fs/ceph/xattr.c       |   12 ++++++++----
 net/ceph/messenger.c  |   26 +++++++++++++-------------
 net/ceph/osd_client.c |    4 ++--
 9 files changed, 49 insertions(+), 31 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/