[0/4] btrfs: remove check-integrity functionality

Message

Qu Wenruo Sept. 8, 2023, 6:42 a.m. UTC

Check-integrity is already marked deprecated, and is going to be removed
in v6.7.

Since we're already at v6.6 cycle, let's finish the cleanup.

This patchset can be fetched from github repo, just in case some patches
are too large for the mailing list.

The removal is based on the 3 entrance functions, and the final one to
cleanup the remaining pieces.
The entrance functions removal is large, but doesn't touch other files.

The last one is the complete opposite, it touches quite some files but
nothing to do with check-integrity.[ch].

Qu Wenruo (4):
  btrfs: remove btrfsic_check_bio() function
  btrfs: remove btrfsic_mount() function
  btrfs: remove btrfsic_unmount() function
  btrfs: remove CONFIG_BTRFS_FS_CHECK_INTEGRITY macro

 fs/btrfs/Kconfig           |   21 -
 fs/btrfs/Makefile          |    1 -
 fs/btrfs/bio.c             |    5 -
 fs/btrfs/check-integrity.c | 2871 ------------------------------------
 fs/btrfs/check-integrity.h |   20 -
 fs/btrfs/dev-replace.c     |    1 -
 fs/btrfs/disk-io.c         |   50 -
 fs/btrfs/extent_io.c       |    1 -
 fs/btrfs/fs.h              |   27 +-
 fs/btrfs/scrub.c           |    1 -
 fs/btrfs/super.c           |   56 -
 11 files changed, 11 insertions(+), 3043 deletions(-)
 delete mode 100644 fs/btrfs/check-integrity.c
 delete mode 100644 fs/btrfs/check-integrity.h

Comments

David Sterba Sept. 8, 2023, 9:49 p.m. UTC | #1

On Fri, Sep 08, 2023 at 02:42:13PM +0800, Qu Wenruo wrote:
> Check-integrity is already marked deprecated, and is going to be removed
> in v6.7.
> 
> Since we're already at v6.6 cycle, let's finish the cleanup.
> 
> This patchset can be fetched from github repo, just in case some patches
> are too large for the mailing list.
> 
> The removal is based on the 3 entrance functions, and the final one to
> cleanup the remaining pieces.
> The entrance functions removal is large, but doesn't touch other files.
> 
> The last one is the complete opposite, it touches quite some files but
> nothing to do with check-integrity.[ch].

I did a quick grep for 'integrity' and there's one more cleanup to do,
btrfs_map_block() can get rid of the parameter need_raid_map as it was
just for the integrity checker and all calls now pass 1. Otherwise,
patches added to misc-next, doing in smaller steps by the entry
functions is fine.  Thanks.