linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Anand Jain <anand.jain@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: fix endianness compatibility during the SB RW
Date: Tue, 13 Feb 2018 18:39:49 +0800	[thread overview]
Message-ID: <752e8ca3-7996-14cf-733e-a03d4ca10acf@gmx.com> (raw)
In-Reply-To: <500c44b5-0c99-100f-6a70-a79d3ad8a388@oracle.com>


[-- Attachment #1.1: Type: text/plain, Size: 3986 bytes --]



On 2018年02月13日 18:27, Anand Jain wrote:
> 
> 
> On 02/13/2018 05:01 PM, Qu Wenruo wrote:
>>
>>
>> On 2018年02月13日 11:00, Anand Jain wrote:
>>> Fixes the endianness bug in the fs_info::super_copy by using its
>>> btrfs_set_super...() function to set values in the SB, as these
>>> functions manage the endianness compatibility nicely.
>>>
>>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>>
>> Also went through all btrfs_super_block SETGET functions, greping using
>> \><member name>, seems that there are still some left here:
>>
>> fs/btrfs/sysfs.c:
>> In both btrfs_sectorsize_show() and btrfs_clone_alignment_show():
>>     return snprintf(buf, PAGE_SIZE, "%u\n",
>>             fs_info->super_copy->sectorsize);
>>
>> In btrfs_nodesize_show():
>>     return snprintf(buf, PAGE_SIZE, "%u\n",
>> fs_info->super_copy->nodesize);
> 
>  Oh. Thanks. Will fix. Maybe it's a good idea to add sysfs fixes
>  into a new patch.
> 
>> And what about cc this to stable kernel?
>> IIRC it's a very critical problem for btrfs.
>>
>> Maybe cc: stable@vger.kernel.org # v3.2+?
> 
>  Thanks for the suggestion. Will do. Any idea what if the patch which
>  applied on mainline ends up conflict on LTS, so write a separate patch
>  to stable?

In fact I'm not sure about this either.

But considering much of the offending code doesn't change since 2009, it
wouldn't cause much conflict IIRC.

Thanks,
Qu

> 
> Thanks, Anand
> 
> 
>> Thanks,
>> Qu
>>
>>> ---
>>> v1->v2: Update change log. Update $Subject.
>>>          Old:
>>>          [PATCH] btrfs: use set functions to update latest refs to
>>> the SB
>>>   fs/btrfs/transaction.c | 20 ++++++++++++--------
>>>   1 file changed, 12 insertions(+), 8 deletions(-)
>>>
>>> diff --git a/fs/btrfs/transaction.c b/fs/btrfs/transaction.c
>>> index 04f07144b45c..9220f004001c 100644
>>> --- a/fs/btrfs/transaction.c
>>> +++ b/fs/btrfs/transaction.c
>>> @@ -1722,19 +1722,23 @@ static void update_super_roots(struct
>>> btrfs_fs_info *fs_info)
>>>         super = fs_info->super_copy;
>>>   +    /* update latest btrfs_super_block::chunk_root refs */
>>>       root_item = &fs_info->chunk_root->root_item;
>>> -    super->chunk_root = root_item->bytenr;
>>> -    super->chunk_root_generation = root_item->generation;
>>> -    super->chunk_root_level = root_item->level;
>>> +    btrfs_set_super_chunk_root(super, root_item->bytenr);
>>> +    btrfs_set_super_chunk_root_generation(super,
>>> root_item->generation);
>>> +    btrfs_set_super_chunk_root_level(super, root_item->level);
>>>   +    /* update latest btrfs_super_block::root refs */
>>>       root_item = &fs_info->tree_root->root_item;
>>> -    super->root = root_item->bytenr;
>>> -    super->generation = root_item->generation;
>>> -    super->root_level = root_item->level;
>>> +    btrfs_set_super_root(super, root_item->bytenr);
>>> +    btrfs_set_super_generation(super, root_item->generation);
>>> +    btrfs_set_super_root_level(super, root_item->level);
>>> +
>>>       if (btrfs_test_opt(fs_info, SPACE_CACHE))
>>> -        super->cache_generation = root_item->generation;
>>> +        btrfs_set_super_cache_generation(super, root_item->generation);
>>>       if (test_bit(BTRFS_FS_UPDATE_UUID_TREE_GEN, &fs_info->flags))
>>> -        super->uuid_tree_generation = root_item->generation;
>>> +        btrfs_set_super_uuid_tree_generation(super,
>>> +                             root_item->generation);
>>>   }
>>>     int btrfs_transaction_in_commit(struct btrfs_fs_info *info)
>>>
>>
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]

  reply	other threads:[~2018-02-13 10:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 15:37 [PATCH] btrfs: use set functions to update latest refs to the SB Anand Jain
2018-02-12 16:34 ` David Sterba
2018-02-13  2:56   ` Anand Jain
2018-02-13  3:00 ` [PATCH v2] btrfs: fix endianness compatibility during the SB RW Anand Jain
2018-02-13  7:04   ` Nikolay Borisov
2018-02-13  9:01   ` Qu Wenruo
2018-02-13 10:27     ` Anand Jain
2018-02-13 10:39       ` Qu Wenruo [this message]
2018-02-13 17:55       ` David Sterba
2018-02-14 14:53         ` Anand Jain
2018-02-15 16:49           ` David Sterba
2018-02-20 17:16   ` Liu Bo

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=752e8ca3-7996-14cf-733e-a03d4ca10acf@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=anand.jain@oracle.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 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).