linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: Chris Mason <clm@fb.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PULL] Btrfs cleanups for 4.11, part 2
Date: Wed, 1 Mar 2017 14:26:57 +0100	[thread overview]
Message-ID: <20170301132657.GC4662@suse.cz> (raw)
In-Reply-To: <319756cf-e9f8-d904-dbf1-6b6fdceca291@suse.com>

On Wed, Mar 01, 2017 at 09:36:38AM +0200, Nikolay Borisov wrote:
> Kbuild reported the following warning: 
> 
>  fs/btrfs/scrub.c: In function 'check_extent_to_block':
> >> fs/btrfs/scrub.c:4259:24: error: passing argument 1 of 'btrfs_get_extent' from incompatible pointer type [-Werror=incompatible-pointer-types]
>      em = btrfs_get_extent(inode, NULL, 0, start, len, 0);
>                            ^~~~~
>    In file included from fs/btrfs/scrub.c:21:0:
>    fs/btrfs/ctree.h:3169:20: note: expected 'struct inode *' but argument is of type 'struct btrfs_inode *'
>     struct extent_map *btrfs_get_extent(struct inode *inode, struct page *page,
>                        ^~~~~~~~~~~~~~~~
>    cc1: some warnings being treated as errors
> 
> vim +/btrfs_get_extent +4259 fs/btrfs/scrub.c
> 
> 32159242 Gui Hecheng 2014-11-10  4253  	if (ordered) {
> 32159242 Gui Hecheng 2014-11-10  4254  		btrfs_put_ordered_extent(ordered);
> 32159242 Gui Hecheng 2014-11-10  4255  		ret = 1;
> 32159242 Gui Hecheng 2014-11-10  4256  		goto out_unlock;
> 32159242 Gui Hecheng 2014-11-10  4257  	}
> 32159242 Gui Hecheng 2014-11-10  4258  
> 32159242 Gui Hecheng 2014-11-10 @4259  	em = btrfs_get_extent(inode, NULL, 0, start, len, 0);
> 32159242 Gui Hecheng 2014-11-10  4260  	if (IS_ERR(em)) {
> 32159242 Gui Hecheng 2014-11-10  4261  		ret = PTR_ERR(em);
> 32159242 Gui Hecheng 2014-11-10  4262  		goto out_unlock;
> 
> I guess changing the definition of btrfs_get_extent in ctree.h got missed to 
> being converted to struct btrfs_inode. Could you be able to fix it up?

Seems the problem got fixed by some following patch. The exact commit
1c8c9c5216295711c79 fails to build but the whole branch is ok. As it's a
minor annoyance I'd rather skip redoing the pull request.

      reply	other threads:[~2017-03-01 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 15:09 [PULL] Btrfs cleanups for 4.11, part 2 David Sterba
2017-02-28 22:35 ` Chris Mason
2017-03-01  7:36   ` Nikolay Borisov
2017-03-01 13:26     ` David Sterba [this message]

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=20170301132657.GC4662@suse.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    /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).