linux-kernel - [GIT PULL] Ceph fixes for 2.6.38-rc3

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.1101271358210.24057@cobra.newdream.net>
Date:	Thu, 27 Jan 2011 14:02:24 -0800 (PST)
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.38-rc3

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 is an xattr search/sort fix, a number of clustered MDS fixes (for a 
sync hang, dup flushes, misdirected/lost request), and a fix for the 
norbytes option with lets users avoid EOVERFLOW on 32-bit systems.

Thanks!
sage


Sage Weil (6):
      ceph: fix xattr rbtree search
      ceph: fix cap_wanted_delay_{min,max} mount option initialization
      ceph: fix erroneous cap flush to non-auth mds
      ceph: fix flushing of caps vs cap import
      ceph: avoid immediate cap check after import
      ceph: avoid picking MDS that is not active

Yehuda Sadeh (1):
      ceph: fix getattr on directory when using norbytes

 fs/ceph/caps.c       |   43 +++++++++++++++++++++++++++++++++++++------
 fs/ceph/inode.c      |   10 +++++-----
 fs/ceph/mds_client.c |   10 +++++++---
 fs/ceph/super.c      |    2 ++
 fs/ceph/xattr.c      |    3 +++
 5 files changed, 54 insertions(+), 14 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/