All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Maggard <jmaggard10@gmail.com>
To: David Sterba <dsterba@suse.com>
Cc: BTRFS <linux-btrfs@vger.kernel.org>, Chris Mason <clm@fb.com>
Subject: Re: Btrfs progs pre-release 4.8.1-rc1
Date: Fri, 7 Oct 2016 12:57:58 -0700	[thread overview]
Message-ID: <CAKgsxVQsy4E0HVUPK3jYum75GyMvuui_sAVOkzDeAAL8f1zUtQ@mail.gmail.com> (raw)
In-Reply-To: <20161007122651.5125-1-dsterba@suse.com>

Hi David,

On Fri, Oct 7, 2016 at 5:26 AM, David Sterba <dsterba@suse.com> wrote:
> Hi,
>
> another pre-release, just in case.  I did a lot of build tests [1] and
> automated a few things so the build failures should not happen again.
>
> ETA for the release is on Sunday (2016-10-09).  Please test and report any new
> problems.
>
> Changes since 4.8:
> - 32bit build works

This is falling over on my 32-bit ARM platform.  Using stock Debian
Jessie armel or armhf, it builds now, but the send ioctl is unhappy:

# btrfs send -p /data/test/.snapshots/1/snapshot/
/data/test/.snapshots/2/snapshot/ > /dev/null
At subvol /data/test/.snapshots/2/snapshot/
ERROR: send ioctl failed with -25: Inappropriate ioctl for device

If I remove the packed attribute from the btrfs_ioctl_send_args struct
and change the BUILD_ASSERT to expect a 72-byte structure, it all
starts working again.  I'm using a 4.1 kernel built with the standard
armhf toolchain from Wheezy (gcc 4.7.2).

-Justin

  reply	other threads:[~2016-10-07 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 12:26 Btrfs progs pre-release 4.8.1-rc1 David Sterba
2016-10-07 19:57 ` Justin Maggard [this message]
2016-10-09 20:40   ` David Sterba

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=CAKgsxVQsy4E0HVUPK3jYum75GyMvuui_sAVOkzDeAAL8f1zUtQ@mail.gmail.com \
    --to=jmaggard10@gmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.