Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: change BTRFS_MOUNT_* flags to 64bits
Date: Mon, 15 Jul 2024 14:31:55 +0200	[thread overview]
Message-ID: <20240715123155.GD8022@twin.jikos.cz> (raw)
In-Reply-To: <0955d2c5675a7fe3146292aaa766755f22bcd94b.1720865683.git.wqu@suse.com>

On Sat, Jul 13, 2024 at 07:45:08PM +0930, Qu Wenruo wrote:
> Currently the BTRFS_MOUNT_* flags is already reaching 32 bits, and with
> the incoming new rescue options, we're going beyond the width of 32
> bits.
> 
> This is going to cause problems as for quite some 32 bit systems,
> 1ULL << 32 would overflow the width of unsigned long.
> 
> Fix the problem by:
> 
> - Migrate all existing BTRFS_MOUNT_* flags to unsigned long long
> - Migrate all mount option related variables to unsigned long long
>   * btrfs_fs_info::mount_opt
>   * btrfs_fs_context::mount_opt
>   * mount_opt parameter of btrfs_check_options()
>   * old_opts parameter of btrfs_remount_begin()
>   * old_opts parameter of btrfs_remount_cleanup()
>   * mount_opt parameter of btrfs_check_mountopts_zoned()
>   * mount_opt and opt parameters of check_ro_option()
> 
> Signed-off-by: Qu Wenruo <wqu@suse.com>
> ---
> The current patch is still based on the latest for-next branch.
> 
> But during merge time I will move this before the new rescue options.

You konw you can't do that right? The branch for 6.11 can't be changed
anymore and it was late last week already. I've forked the changes at
8e7860543a94784d744c7ce34b7 so far it's still subset of for-next if you
change anything below that then it'll cause merge conflicts or would
need manual resolution in another way. Until rc1 it's probably safest to
just append to our for-next.

  reply	other threads:[~2024-07-15 12:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-13 10:15 [PATCH v2] btrfs: change BTRFS_MOUNT_* flags to 64bits Qu Wenruo
2024-07-15 12:31 ` David Sterba [this message]
2024-07-15 22:11   ` Qu Wenruo
2024-07-15 22:41     ` Qu Wenruo
2024-07-16  0:14       ` 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=20240715123155.GD8022@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.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