From: Guenter Roeck <linux@roeck-us.net>
To: Chris Mason <chris.mason@fusionio.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Mark Fasheh <mfasheh@suse.de>, Zach Brown <zab@redhat.com>
Subject: Re: Build failures due to commit 416161db (btrfs: offline dedupe)
Date: Fri, 13 Sep 2013 10:15:31 -0700 [thread overview]
Message-ID: <20130913171531.GB7009@roeck-us.net> (raw)
In-Reply-To: <20130913170022.18785.82013@localhost.localdomain>
On Fri, Sep 13, 2013 at 01:00:22PM -0400, Chris Mason wrote:
> Quoting Guenter Roeck (2013-09-13 12:35:35)
> > On Fri, Sep 13, 2013 at 03:52:43PM +0200, Geert Uytterhoeven wrote:
> > > On Fri, Sep 13, 2013 at 3:33 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> > > > fs/btrfs/ioctl.c: In function 'btrfs_ioctl_file_extent_same':
> > > > fs/btrfs/ioctl.c:2802:3: error: implicit declaration of function '__put_user_unaligned' [-Werror=implicit-function-declaration]
> > > > cc1: some warnings being treated as errors
> > > > make[2]: *** [fs/btrfs/ioctl.o] Error 1
> > > > make[2]: *** Waiting for unfinished jobs....
> > > >
> > > > Seen with alpha:allmodconfig, arm:allmodconfig, m68k:allmodconfig, and
> > > > xtensa:allmodconfig.
> > >
> > > Known issue, cfr. my early warning 10 days ago:
> > >
> > > "Btrfs is the first user of __put_user_unaligned() outside the compat code,
> > > hence now all 32-bit architectures should make sure to implement this, too."
> > >
> > > http://marc.info/?l=linux-arch&m=137820065929216&w=2
> > >
> > > and today's thread https://lkml.org/lkml/2013/9/12/814
> > >
> >
> > It doesn't seem right that a patch breaks the build for several platforms, and
> > the problem is then blamed on the platform code instead of the code that is
> > introducing the problem.
> >
> > Maybe we should add BROKEN to the btrfs dependencies for the affected platforms.
> > After all, it _is_ broken.
>
> I'm happy to fix this with a bigger put of the info struct, just
> let me know the preferred arch-happy solution.
>
Me not either. The only requirement I would have is that it should not break
a build. Of course, it would be even better if it would actually work ;-).
Guenter
next prev parent reply other threads:[~2013-09-13 17:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 13:33 Build failures due to commit 416161db (btrfs: offline dedupe) Guenter Roeck
2013-09-13 13:52 ` Geert Uytterhoeven
2013-09-13 16:35 ` Guenter Roeck
2013-09-13 17:00 ` Chris Mason
2013-09-13 17:15 ` Guenter Roeck [this message]
2013-09-13 17:58 ` Mark Fasheh
2013-09-13 19:33 ` Chris Mason
2013-09-17 22:43 ` Mark Fasheh
2013-09-18 18:40 ` Guenter Roeck
2013-09-18 22:02 ` Mark Fasheh
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=20130913171531.GB7009@roeck-us.net \
--to=linux@roeck-us.net \
--cc=chris.mason@fusionio.com \
--cc=geert@linux-m68k.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.de \
--cc=zab@redhat.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).