From: Dave Jones <davej@redhat.com>
To: Sage Weil <sage@inktank.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
ceph-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [GIT PULL] Ceph updates for -rc1
Date: Tue, 28 Jan 2014 16:10:21 -0500 [thread overview]
Message-ID: <20140128211021.GB1377@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1401281032560.16427@cobra.newdream.net>
On Tue, Jan 28, 2014 at 10:40:16AM -0800, Sage Weil wrote:
> Hi Linus,
>
> Please pull the following Ceph updates from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus
>
> This is a big batch. From Ilya we have:
>
> - rbd support for more than ~250 mapped devices (now uses same scheme
> that SCSI does for device major/minor numbering)
> - crush updates for new mapping behaviors (will be needed for coming
> erasure coding support, among other things)
> - preliminary support for tiered storage pools
>
> There is also a big series fixing a pile cephfs bugs with clustered MDSs
> from Yan Zheng, ACL support for cephfs from Guangliang Zhao, ceph fscache
> improvements from Li Wang, improved behavior when we get ENOSPC from Josh
> Durgin, some readv/writev improvements from Majianpeng, and the usual mix
> of small cleanups.
This breaks the build for me.
fs/ceph/acl.c: In function ‘ceph_init_acl’:
fs/ceph/acl.c:216:3: warning: passing argument 1 of ‘posix_acl_create’ from incompatible pointer type [enabled by default]
ret = posix_acl_create(&acl, GFP_NOFS, &inode->i_mode);
^
In file included from include/linux/posix_acl_xattr.h:12:0,
from fs/ceph/acl.c:25:
include/linux/posix_acl.h:96:12: note: expected ‘struct inode *’ but argument is of type ‘struct posix_acl **’
extern int posix_acl_create(struct inode *, umode_t *, struct posix_acl **,
^
fs/ceph/acl.c:216:3: warning: passing argument 2 of ‘posix_acl_create’ makes pointer from integer without a cast [enabled by default]
ret = posix_acl_create(&acl, GFP_NOFS, &inode->i_mode);
^
In file included from include/linux/posix_acl_xattr.h:12:0,
from fs/ceph/acl.c:25:
include/linux/posix_acl.h:96:12: note: expected ‘umode_t *’ but argument is of type ‘unsigned int’
extern int posix_acl_create(struct inode *, umode_t *, struct posix_acl **,
^
fs/ceph/acl.c:216:3: warning: passing argument 3 of ‘posix_acl_create’ from incompatible pointer type [enabled by default]
ret = posix_acl_create(&acl, GFP_NOFS, &inode->i_mode);
^
In file included from include/linux/posix_acl_xattr.h:12:0,
from fs/ceph/acl.c:25:
include/linux/posix_acl.h:96:12: note: expected ‘struct posix_acl **’ but argument is of type ‘umode_t *’
extern int posix_acl_create(struct inode *, umode_t *, struct posix_acl **,
^
fs/ceph/acl.c:216:3: error: too few arguments to function ‘posix_acl_create’
ret = posix_acl_create(&acl, GFP_NOFS, &inode->i_mode);
^
In file included from include/linux/posix_acl_xattr.h:12:0,
from fs/ceph/acl.c:25:
include/linux/posix_acl.h:96:12: note: declared here
extern int posix_acl_create(struct inode *, umode_t *, struct posix_acl **,
^
fs/ceph/acl.c: In function ‘ceph_acl_chmod’:
fs/ceph/acl.c:252:2: warning: passing argument 1 of ‘posix_acl_chmod’ from incompatible pointer type [enabled by default]
ret = posix_acl_chmod(&acl, GFP_KERNEL, inode->i_mode);
^
In file included from include/linux/posix_acl_xattr.h:12:0,
from fs/ceph/acl.c:25:
include/linux/posix_acl.h:95:12: note: expected ‘struct inode *’ but argument is of type ‘struct posix_acl **’
extern int posix_acl_chmod(struct inode *, umode_t);
^
fs/ceph/acl.c:252:2: error: too many arguments to function ‘posix_acl_chmod’
ret = posix_acl_chmod(&acl, GFP_KERNEL, inode->i_mode);
^
In file included from include/linux/posix_acl_xattr.h:12:0,
from fs/ceph/acl.c:25:
include/linux/posix_acl.h:95:12: note: declared here
extern int posix_acl_chmod(struct inode *, umode_t);
next prev parent reply other threads:[~2014-01-28 21:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 18:40 [GIT PULL] Ceph updates for -rc1 Sage Weil
2014-01-28 21:10 ` Dave Jones [this message]
2014-01-28 21:48 ` Linus Torvalds
2014-01-29 6:08 ` Sage Weil
2014-01-29 14:30 ` Sage Weil
2014-01-29 16:36 ` Ilya Dryomov
2014-01-29 16:37 ` [PATCH v2] ceph: fix posix ACL hooks Ilya Dryomov
2014-01-29 19:09 ` Linus Torvalds
2014-01-30 7:54 ` Christoph Hellwig
2014-01-30 22:01 ` Linus Torvalds
2014-01-31 0:14 ` Sage Weil
2014-02-03 10:29 ` Christoph Hellwig
2014-02-03 11:13 ` Al Viro
2014-02-03 21:03 ` Linus Torvalds
2014-02-03 21:19 ` Al Viro
2014-02-03 21:24 ` Christoph Hellwig
2014-02-03 21:31 ` Al Viro
2014-02-03 21:36 ` Christoph Hellwig
2014-02-03 21:37 ` Linus Torvalds
2014-02-03 21:42 ` Al Viro
2014-02-03 21:31 ` Linus Torvalds
2014-02-03 21:39 ` Al Viro
2014-02-03 21:43 ` Al Viro
2014-02-03 21:44 ` Linus Torvalds
2014-02-03 22:31 ` Al Viro
2014-02-06 20:51 ` Jeremy Allison
2014-02-03 21:23 ` Christoph Hellwig
2014-02-03 21:59 ` Al Viro
2014-02-03 22:12 ` Linus Torvalds
2014-02-03 22:40 ` Al Viro
2014-02-03 22:55 ` Linus Torvalds
2014-02-04 11:33 ` Steven Whitehouse
2014-02-04 15:57 ` Christoph Hellwig
2014-02-04 16:17 ` Linus Torvalds
2014-02-03 21:59 ` Linus Torvalds
2014-01-29 20:43 ` Ilya Dryomov
2014-01-30 10:46 ` [GIT PULL] Ceph updates for -rc1 Christoph Hellwig
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=20140128211021.GB1377@redhat.com \
--to=davej@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@inktank.com \
--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;
as well as URLs for NNTP newsgroup(s).