<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>b261d222 - lib/crc: remove CONFIG_LIBCRC32C</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#b261d222</link>
        <description>lib/crc: remove CONFIG_LIBCRC32CNow that LIBCRC32C does nothing besides select CRC32, make every optionthat selects LIBCRC32C instead select CRC32 directly.  Then removeLIBCRC32C.Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: &quot;Martin K. Petersen&quot; &lt;martin.petersen@oracle.com&gt;Acked-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;Link: https://lore.kernel.org/r/20250401221600.24878-8-ebiggers@kernel.orgSigned-off-by: Eric Biggers &lt;ebiggers@google.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Tue, 01 Apr 2025 22:16:00 +0000</pubDate>
        <dc:creator>Eric Biggers &lt;ebiggers@google.com&gt;</dc:creator>
    </item>
<item>
        <title>67cd3f22 - btrfs: split out CONFIG_BTRFS_EXPERIMENTAL from CONFIG_BTRFS_DEBUG</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#67cd3f22</link>
        <description>btrfs: split out CONFIG_BTRFS_EXPERIMENTAL from CONFIG_BTRFS_DEBUGCurrently CONFIG_BTRFS_EXPERIMENTAL is not only for the extra debuggingoutput, but also for experimental features.This is not ideal to distinguish planned but not yet stable featuresfrom those purely designed for debugging.This patch splits the following features into CONFIG_BTRFS_EXPERIMENTAL:- Extent map shrinker  This seems to be the first one to exit experimental.- Extent tree v2  This seems to be the last one to graduate from experimental.- Raid stripe tree- Csum offload mode- Send protocol v3Reviewed-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Signed-off-by: Qu Wenruo &lt;wqu@suse.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Mon, 16 Sep 2024 08:48:25 +0000</pubDate>
        <dc:creator>Qu Wenruo &lt;wqu@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>732fab95 - btrfs: check-integrity: remove CONFIG_BTRFS_FS_CHECK_INTEGRITY option</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#732fab95</link>
        <description>btrfs: check-integrity: remove CONFIG_BTRFS_FS_CHECK_INTEGRITY optionSince all check-integrity entry points have been removed, let&apos;s alsoremove the config and all related code relying on that.And since we have removed the mount option for check-integrity, we alsoneed to re-number all the BTRFS_MOUNT_* enums.Signed-off-by: Qu Wenruo &lt;wqu@suse.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Fri, 08 Sep 2023 06:42:17 +0000</pubDate>
        <dc:creator>Qu Wenruo &lt;wqu@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>5facccc9 - MAINTAINERS: remove links to obsolete btrfs.wiki.kernel.org</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#5facccc9</link>
        <description>MAINTAINERS: remove links to obsolete btrfs.wiki.kernel.orgThe wiki has been archived and is not updated anymore. Remove or replacethe links in files that contain it (MAINTAINERS, Kconfig, docs).Signed-off-by: Bhaskar Chowdhury &lt;unixbhaskar@gmail.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Tue, 22 Aug 2023 21:47:47 +0000</pubDate>
        <dc:creator>Bhaskar Chowdhury &lt;unixbhaskar@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>16c3a476 - btrfs: deprecate integrity checker feature</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#16c3a476</link>
        <description>btrfs: deprecate integrity checker featureThe integrity checker feature needs to be enabled at compile time(BTRFS_FS_CHECK_INTEGRITY) and then enabled by mount options check_int*.Although it provides some unique features which can not be provided byany other sanity checks like tree-checker, it does not only have highCPU and memory overhead, but is also a maintenance burden.For example, it&apos;s the only caller of btrfs_map_block() with@need_raid_map = 0.Considering most btrfs developers are not even testing this feature, I&apos;mhere to propose deprecation of this feature.For now only warning messages will be printed, the feature itself wouldstill work.Removal time has been set to 6.7 release.Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Signed-off-by: Qu Wenruo &lt;wqu@suse.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Mon, 26 Jun 2023 09:55:25 +0000</pubDate>
        <dc:creator>Qu Wenruo &lt;wqu@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>2c275afe - block: make blkcg_punt_bio_submit optional</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#2c275afe</link>
        <description>block: make blkcg_punt_bio_submit optionalGuard all the code to punt bios to a per-cgroup submission helper by anew CONFIG_BLK_CGROUP_PUNT_BIO symbol that is selected by btrfs.This way non-btrfs kernel builds don&apos;t need to have this code.Reviewed-by: Jens Axboe &lt;axboe@kernel.dk&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Mon, 27 Mar 2023 00:49:53 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>cfa71bb2 - fs/btrfs: Remove &quot;select SRCU&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#cfa71bb2</link>
        <description>fs/btrfs: Remove &quot;select SRCU&quot;Now that the SRCU Kconfig option is unconditionally selected, there isno longer any point in selecting it.  Therefore, remove the &quot;select SRCU&quot;Kconfig statements.Signed-off-by: Paul E. McKenney &lt;paulmck@kernel.org&gt;Cc: Chris Mason &lt;clm@fb.com&gt;Cc: Josef Bacik &lt;josef@toxicpanda.com&gt;Cc: David Sterba &lt;dsterba@suse.com&gt;Cc: &lt;linux-btrfs@vger.kernel.org&gt;Acked-by: David Sterba &lt;dsterba@suse.com&gt;Reviewed-by: Qu Wenruo &lt;wqu@suse.com&gt;Reviewed-by: John Ogness &lt;john.ogness@linutronix.de&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Wed, 23 Nov 2022 01:49:29 +0000</pubDate>
        <dc:creator>Paul E. McKenney &lt;paulmck@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>e9009095 - btrfs: use generic Kconfig option for 256kB page size limit</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#e9009095</link>
        <description>btrfs: use generic Kconfig option for 256kB page size limitUse the newly introduced CONFIG_PAGE_SIZE_LESS_THAN_256KB to describethe dependency introduced by commit b05fbcc36be1 (&quot;btrfs: disable buildon platforms having page size 256K&quot;).Link: https://lkml.kernel.org/r/20211129230141.228085-3-nathan@kernel.orgSigned-off-by: Nathan Chancellor &lt;nathan@kernel.org&gt;Acked-by: David Sterba &lt;dsterba@suse.com&gt;Cc: Chris Mason &lt;clm@fb.com&gt;Cc: Josef Bacik &lt;josef@toxicpanda.com&gt;Cc: kernel test robot &lt;lkp@intel.com&gt;Cc: Luis Chamberlain &lt;mcgrof@kernel.org&gt;Cc: Nick Desaulniers &lt;ndesaulniers@google.com&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Thu, 20 Jan 2022 02:10:25 +0000</pubDate>
        <dc:creator>Nathan Chancellor &lt;nathan@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>b05fbcc3 - btrfs: disable build on platforms having page size 256K</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#b05fbcc3</link>
        <description>btrfs: disable build on platforms having page size 256KWith a config having PAGE_SIZE set to 256K, BTRFS build failswith the following message  include/linux/compiler_types.h:326:38: error: call to  &apos;__compiletime_assert_791&apos; declared with attribute error:  BUILD_BUG_ON failed: (BTRFS_MAX_COMPRESSED % PAGE_SIZE) != 0BTRFS_MAX_COMPRESSED being 128K, BTRFS cannot support platforms with256K pages at the time being.There are two platforms that can select 256K pages: - hexagon - powerpcDisable BTRFS when 256K page size is selected. Supporting this wouldrequire changes to the subpage mode that&apos;s currently being developed.Given that 256K is many times larger than page sizes commonly used andfor what the algorithms and structures have been tuned, it&apos;s out ofscope and disabling build is a reasonable option.Reported-by: kernel test robot &lt;lkp@intel.com&gt;Signed-off-by: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;[ update changelog ]Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Thu, 10 Jun 2021 05:23:02 +0000</pubDate>
        <dc:creator>Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;</dc:creator>
    </item>
<item>
        <title>f85781fb - btrfs: switch to iomap for direct IO</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#f85781fb</link>
        <description>btrfs: switch to iomap for direct IOWe&apos;re using direct io implementation based on buffer heads. This patchswitches to the new iomap infrastructure.Switch from __blockdev_direct_IO() to iomap_dio_rw().  Renamebtrfs_get_blocks_direct() to btrfs_dio_iomap_begin() and use it asiomap_begin() for iomap direct I/O functions. This function allocatesand locks all the blocks required for the I/O.  btrfs_submit_direct() isused as the submit_io() hook for direct I/O ops.Since we need direct I/O reads to go through iomap_dio_rw(), we changefile_operations.read_iter() to a btrfs_file_read_iter() which callsbtrfs_direct_IO() for direct reads and falls back togeneric_file_buffered_read() for incomplete reads and buffered reads.We don&apos;t need address_space.direct_IO() anymore: set it to noop.Similarly, we don&apos;t need flags used in __blockdev_direct_IO(). iomap iscapable of direct I/O reads from a hole, so we don&apos;t need to return-ENOENT.Btrfs direct I/O is now done under i_rwsem, shared in case of reads andexclusive in case of writes. This guards against simultaneous truncates.Use iomap-&gt;iomap_end() to check for failed or incomplete direct I/O:  - for writes, call __endio_write_update_ordered()  - for reads, unlock extentsbtrfs_dio_data is now hooked in iomap-&gt;private and notcurrent-&gt;journal_info. It carries the reservation variable and theamount of data submitted, so we can calculate the amount of data to call__endio_write_update_ordered in case of an error.This patch removes last use of struct buffer_head from btrfs.Reviewed-by: Josef Bacik &lt;josef@toxicpanda.com&gt;Signed-off-by: Goldwyn Rodrigues &lt;rgoldwyn@suse.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Mon, 17 Aug 2020 16:18:21 +0000</pubDate>
        <dc:creator>Goldwyn Rodrigues &lt;rgoldwyn@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>55e20bd1 - Revert &quot;btrfs: switch to iomap_dio_rw() for dio&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#55e20bd1</link>
        <description>Revert &quot;btrfs: switch to iomap_dio_rw() for dio&quot;This reverts commit a43a67a2d715540c1368b9501a22b0373b5874c0.This patch reverts the main part of switching direct io implementationto iomap infrastructure. There&apos;s a problem in invalidate page thatcouldn&apos;t be solved as regression in this development cycle.The problem occurs when buffered and direct io are mixed, and the rangesoverlap. Although this is not recommended, filesystems implementmeasures or fallbacks to make it somehow work. In this case, fallback tobuffered IO would be an option for btrfs (this already happens whendirect io is done on compressed data), but the change would be needed inthe iomap code, bringing new semantics to other filesystems.Another problem arises when again the buffered and direct ios are mixed,invalidation fails, then -EIO is set on the mapping and fsync will fail,though there&apos;s no real error.There have been discussions how to fix that, but revert seems to be theleast intrusive option.Link: https://lore.kernel.org/linux-btrfs/20200528192103.xm45qoxqmkw7i5yl@fiona/Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Tue, 09 Jun 2020 17:56:06 +0000</pubDate>
        <dc:creator>David Sterba &lt;dsterba@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>a43a67a2 - btrfs: switch to iomap_dio_rw() for dio</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#a43a67a2</link>
        <description>btrfs: switch to iomap_dio_rw() for dioSwitch from __blockdev_direct_IO() to iomap_dio_rw().Rename btrfs_get_blocks_direct() to btrfs_dio_iomap_begin() and use itas iomap_begin() for iomap direct I/O functions. This functionallocates and locks all the blocks required for the I/O.btrfs_submit_direct() is used as the submit_io() hook for direct I/Oops.Since we need direct I/O reads to go through iomap_dio_rw(), we changefile_operations.read_iter() to a btrfs_file_read_iter() which callsbtrfs_direct_IO() for direct reads and falls back togeneric_file_buffered_read() for incomplete reads and buffered reads.We don&apos;t need address_space.direct_IO() anymore so set it to noop.Similarly, we don&apos;t need flags used in __blockdev_direct_IO(). iomap iscapable of direct I/O reads from a hole, so we don&apos;t need to return-ENOENT.BTRFS direct I/O is now done under i_rwsem, shared in case of reads andexclusive in case of writes. This guards against simultaneous truncates.Use iomap-&gt;iomap_end() to check for failed or incomplete direct I/O: - for writes, call __endio_write_update_ordered() - for reads, unlock extentsbtrfs_dio_data is now hooked in iomap-&gt;private and notcurrent-&gt;journal_info. It carries the reservation variable and theamount of data submitted, so we can calculate the amount of data to call__endio_write_update_ordered in case of an error.This patch removes last use of struct buffer_head from btrfs.Signed-off-by: Goldwyn Rodrigues &lt;rgoldwyn@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Tue, 19 May 2020 14:14:18 +0000</pubDate>
        <dc:creator>Goldwyn Rodrigues &lt;rgoldwyn@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>78f926f7 - btrfs: add Kconfig dependency for BLAKE2B</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#78f926f7</link>
        <description>btrfs: add Kconfig dependency for BLAKE2BBecause the BLAKE2B code went through a different tree, it was notavailable at the time the btrfs part was merged. Now that the Kconfigsymbol exists, add it to the list.Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Thu, 28 Nov 2019 12:02:32 +0000</pubDate>
        <dc:creator>David Sterba &lt;dsterba@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>3831bf00 - btrfs: add sha256 to checksumming algorithm</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#3831bf00</link>
        <description>btrfs: add sha256 to checksumming algorithmAdd sha256 to the list of possible checksumming algorithms used by BTRFS.Signed-off-by: Johannes Thumshirn &lt;jthumshirn@suse.de&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Mon, 07 Oct 2019 09:11:02 +0000</pubDate>
        <dc:creator>Johannes Thumshirn &lt;jthumshirn@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>3951e7f0 - btrfs: add xxhash64 to checksumming algorithms</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#3951e7f0</link>
        <description>btrfs: add xxhash64 to checksumming algorithmsAdd xxhash64 to the list of possible checksumming algorithms used byBTRFS.Signed-off-by: Johannes Thumshirn &lt;jthumshirn@suse.de&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Mon, 07 Oct 2019 09:11:01 +0000</pubDate>
        <dc:creator>Johannes Thumshirn &lt;jthumshirn@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>314c4cd6 - btrfs: Fix build error while LIBCRC32C is module</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#314c4cd6</link>
        <description>btrfs: Fix build error while LIBCRC32C is moduleIf CONFIG_BTRFS_FS is y and CONFIG_LIBCRC32C is m,building fails:  fs/btrfs/super.o: In function `btrfs_mount_root&apos;:  super.c:(.text+0xb7f9): undefined reference to `crc32c_impl&apos;  fs/btrfs/super.o: In function `init_btrfs_fs&apos;:  super.c:(.init.text+0x3465): undefined reference to `crc32c_impl&apos;  fs/btrfs/extent-tree.o: In function `hash_extent_data_ref&apos;:  extent-tree.c:(.text+0xe60): undefined reference to `crc32c&apos;  extent-tree.c:(.text+0xe78): undefined reference to `crc32c&apos;  extent-tree.c:(.text+0xe8b): undefined reference to `crc32c&apos;  fs/btrfs/dir-item.o: In function `btrfs_insert_xattr_item&apos;:  dir-item.c:(.text+0x291): undefined reference to `crc32c&apos;  fs/btrfs/dir-item.o: In function `btrfs_insert_dir_item&apos;:  dir-item.c:(.text+0x429): undefined reference to `crc32c&apos;Select LIBCRC32C to fix it.Reported-by: Hulk Robot &lt;hulkci@huawei.com&gt;Fixes: d5178578bcd4 (&quot;btrfs: directly call into crypto framework for checksumming&quot;)Reviewed-by: Johannes Thumshirn &lt;jthumshirn@suse.de&gt;Signed-off-by: YueHaibing &lt;yuehaibing@huawei.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Tue, 02 Jul 2019 14:39:03 +0000</pubDate>
        <dc:creator>YueHaibing &lt;yuehaibing@huawei.com&gt;</dc:creator>
    </item>
<item>
        <title>d5178578 - btrfs: directly call into crypto framework for checksumming</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#d5178578</link>
        <description>btrfs: directly call into crypto framework for checksummingCurrently btrfs_csum_data() relied on the crc32c() wrapper around thecrypto framework for calculating the CRCs.As we have our own crypto_shash structure in the fs_info now, we candirectly call into the crypto framework without going trough the wrapper.This way we can even remove the btrfs_csum_data() and btrfs_csum_final()wrappers.The module dependency on crc32c is preserved via MODULE_SOFTDEP(&quot;pre:crc32c&quot;), which was previously provided by LIBCRC32C config option doingthe same.Signed-off-by: Johannes Thumshirn &lt;jthumshirn@suse.de&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Mon, 03 Jun 2019 14:58:57 +0000</pubDate>
        <dc:creator>Johannes Thumshirn &lt;jthumshirn@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>852eb3ae - btrfs: add SPDX header to Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#852eb3ae</link>
        <description>btrfs: add SPDX header to KconfigSigned-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Tue, 03 Apr 2018 17:23:33 +0000</pubDate>
        <dc:creator>David Sterba &lt;dsterba@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>9678c543 - btrfs: Remove custom crc32c init code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#9678c543</link>
        <description>btrfs: Remove custom crc32c init codeThe custom crc32 init code was introduced in14a958e678cd (&quot;Btrfs: fix btrfs boot when compiled as built-in&quot;) toenable using btrfs as a built-in. However, later as pointed out by60efa5eb2e88 (&quot;Btrfs: use late_initcall instead of module_init&quot;) thiswasn&apos;t enough and finally btrfs was switched to late_initcall whichcomes after the generic crc32c implementation is initiliased. Thelatter commit superseeded the former. Now that we don&apos;t have tomaintain our own code let&apos;s just remove it and switch to using thegeneric implementation.Despite touching a lot of files the patch is really simple. Here is the gist ofthe changes:1. Select LIBCRC32C rather than the low-level modules.2. s/btrfs_crc32c/crc32c/g3. replace hash.h with linux/crc32c.h4. Move the btrfs namehash funcs to ctree.h and change the tree accordingly.I&apos;ve tested this with btrfs being both a module and a built-in and xfstestdoesn&apos;t complain.Does seem to fix the longstanding problem of not automatically selectiongthe crc32c module when btrfs is used. Possibly there is a workaround indracut.The modinfo confirms that now all the module dependencies are there:before:depends:        zstd_compress,zstd_decompress,raid6_pq,xor,zlib_deflateafter:depends:        libcrc32c,zstd_compress,zstd_decompress,raid6_pq,xor,zlib_deflateSigned-off-by: Nikolay Borisov &lt;nborisov@suse.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;[ add more info to changelog from mails ]Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Mon, 08 Jan 2018 09:45:05 +0000</pubDate>
        <dc:creator>Nikolay Borisov &lt;nborisov@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>91581e4c - fs/*/Kconfig: drop links to 404-compliant http://acl.bestbits.at</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Kconfig#91581e4c</link>
        <description>fs/*/Kconfig: drop links to 404-compliant http://acl.bestbits.atThis link is replicated in most filesystems&apos; config stanzas.  Referringto an archived version of that site is pointless as it mostly deals withpatches; user documentation is available elsewhere.Signed-off-by: Adam Borowski &lt;kilobyte@angband.pl&gt;CC: Alexander Viro &lt;viro@zeniv.linux.org.uk&gt;Reviewed-by: Darrick J. Wong &lt;darrick.wong@oracle.com&gt;Acked-by: Jan Kara &lt;jack@suse.cz&gt;Acked-by: Dave Kleikamp &lt;dave.kleikamp@oracle.com&gt;Acked-by: David Sterba &lt;dsterba@suse.com&gt;Acked-by: &quot;Yan, Zheng&quot; &lt;zyan@redhat.com&gt;Acked-by: Chao Yu &lt;yuchao0@huawei.com&gt;Acked-by: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;Acked-by: Steve French &lt;smfrench@gmail.com&gt;Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/fs/btrfs/Kconfig</description>
        <pubDate>Wed, 20 Dec 2017 13:58:52 +0000</pubDate>
        <dc:creator>Adam Borowski &lt;kilobyte@angband.pl&gt;</dc:creator>
    </item>
</channel>
</rss>
