All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: <fdmanana@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: fix qgroup rescan to work with skinny metadata
Date: Thu, 23 Jan 2014 18:44:29 -0500	[thread overview]
Message-ID: <52E1A95D.9000903@fb.com> (raw)
In-Reply-To: <CAL3q7H7WGFpYC9AuyhFPhNgudyUAmVA3mgGaqVY+Ay=Z9=0_2Q@mail.gmail.com>


On 01/23/2014 06:42 PM, Filipe David Manana wrote:
> On Thu, Jan 23, 2014 at 9:45 PM, Josef Bacik <jbacik@fb.com> wrote:
>> Could have sworn I fixed this before but apparently not.  This makes us pass
>> btrfs/022 with skinny metadata enabled.  Thanks,
>>
>> Signed-off-by: Josef Bacik <jbacik@fb.com>
>> ---
>>   fs/btrfs/qgroup.c | 18 +++++++++++++-----
>>   1 file changed, 13 insertions(+), 5 deletions(-)
>>
>> diff --git a/fs/btrfs/qgroup.c b/fs/btrfs/qgroup.c
>> index d22e0a1..7d04026 100644
>> --- a/fs/btrfs/qgroup.c
>> +++ b/fs/btrfs/qgroup.c
>> @@ -1897,9 +1897,17 @@ qgroup_rescan_leaf(struct btrfs_fs_info *fs_info, struct btrfs_path *path,
>>          mutex_unlock(&fs_info->qgroup_rescan_lock);
>>
>>          for (; slot < btrfs_header_nritems(scratch_leaf); ++slot) {
>> +               u64 num_bytes;
>> +
>>                  btrfs_item_key_to_cpu(scratch_leaf, &found, slot);
>> -               if (found.type != BTRFS_EXTENT_ITEM_KEY)
>> +               if (found.type != BTRFS_EXTENT_ITEM_KEY ||
>> +                   found.type != BTRFS_METADATA_ITEM_KEY)
>>                          continue;
> Hi Josef,
>
> Shouldn't it be && instead of || ?
>
Yes it should, thanks,

Josef

      reply	other threads:[~2014-01-23 23:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 21:45 [PATCH] Btrfs: fix qgroup rescan to work with skinny metadata Josef Bacik
2014-01-23 23:42 ` Filipe David Manana
2014-01-23 23:44   ` Josef Bacik [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=52E1A95D.9000903@fb.com \
    --to=jbacik@fb.com \
    --cc=fdmanana@gmail.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.