mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>, <luke@dashjr.org>
Cc: <luke-jr+git@utopios.org>, <jbacik@fb.com>, <dsterba@suse.com>,
	<stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-btrfs@vger.kernel.org>, <1619918@bugs.launchpad.net>
Subject: Re: [Regression 4.7-rc1] btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in btrfs_ioctl
Date: Fri, 6 Jan 2017 15:46:38 -0500	[thread overview]
Message-ID: <0ea8d8ad-b410-b81b-5732-b5d6beca1d10@fb.com> (raw)
In-Reply-To: <a555bec3-f0c8-b973-52e0-02bc2e3b5b29@canonical.com>

On 01/06/2017 12:22 PM, Joseph Salisbury wrote:
> Hi Luke,
>
> A kernel bug report was opened against Ubuntu [0].  This bug was fixed
> by the following commit in v4.7-rc1:
>
>
> commit 4c63c2454eff996c5e27991221106eb511f7db38
>
> Author: Luke Dashjr <luke@dashjr.org>
> Date:   Thu Oct 29 08:22:21 2015 +0000
>
>     btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in
> btrfs_ioctl
>
>
> However, this commit introduced a new regression.  With this commit
> applied, "btrfs fi show" no longer works and the btrfs snapshot
> functionality breaks.
>
>
>
> I was hoping to get your feedback, since you are the patch author.  Do
> you think gathering any additional data will help diagnose this issue,
> or would it be best to submit a revert request?

This is working for me, could you please include an strace of the problem?

Thanks!

-chris

  parent reply	other threads:[~2017-01-06 20:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 17:22 Joseph Salisbury
2017-01-06 17:38 ` Luke Dashjr
2017-01-06 20:46 ` Chris Mason [this message]
2017-01-09 11:28 ` David Sterba
2017-02-07  0:37   ` Jeff Mahoney

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=0ea8d8ad-b410-b81b-5732-b5d6beca1d10@fb.com \
    --to=clm@fb.com \
    --cc=1619918@bugs.launchpad.net \
    --cc=dsterba@suse.com \
    --cc=jbacik@fb.com \
    --cc=joseph.salisbury@canonical.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke-jr+git@utopios.org \
    --cc=luke@dashjr.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®