btrfs: make chunk size validation to be simpler
Commit
6ded22c1bfe6 ("btrfs: reduce div64 calls by limiting the number
of stripes of a chunk to u32") introduced a chunk size limit check, but
it is using a wrong result in the comment:
U32_MAX << BTRFS_STRIPE_LEN_SHIFT results 256T, not 256G.
Instead of calculating the size limit, using an immediate number
(SZ_256G).
This has the following benefit:
- Still large enough for future expansion
Although the check is 1024 times more strict, I don't think we will
allow 256G chunk anytime soon.
And we have higher chance (10 more bits) to catch a bitflip in the
high bits.
- Much harder to diverge from the comment
We don't need to calculate the number anymore.
Signed-off-by: Qu Wenruo <wqu@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>