diff options
| author | Omar Sandoval <osandov@fb.com> | 2022-03-17 20:25:38 +0300 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2022-07-25 18:45:32 +0300 |
| commit | 54cab6aff811d328c5add37e0faf32f6328741ea (patch) | |
| tree | 6217601c6178ee3cdf4381232e54a0491058aa4b /Kbuild | |
| parent | ca182acc53df2ab795354c535dfd966d0fa2ae8b (diff) | |
| download | linux-54cab6aff811d328c5add37e0faf32f6328741ea.tar.xz | |
btrfs: send: explicitly number commands and attributes
Commit e77fbf990316 ("btrfs: send: prepare for v2 protocol") added
_BTRFS_SEND_C_MAX_V* macros equal to the maximum command number for the
version plus 1, but as written this creates gaps in the number space.
The maximum command number is currently 22, and __BTRFS_SEND_C_MAX_V1 is
accordingly 23. But then __BTRFS_SEND_C_MAX_V2 is 24, suggesting that v2
has a command numbered 23, and __BTRFS_SEND_C_MAX is 25, suggesting that
23 and 24 are valid commands.
Instead, let's explicitly number all of the commands, attributes, and
sentinel MAX constants.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions