<?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 Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>2b34879d - btrfs: selftests: add delayed ref self test cases</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#2b34879d</link>
        <description>btrfs: selftests: add delayed ref self test casesThe recent fix for a stupid mistake I made uncovered the fact that wedon&apos;t have adequate testing in the delayed refs code, as it took apretty extensive and long running stress test to uncover something thata unit test would have uncovered right away.Fix this by adding a delayed refs self test suite.  This will validatethat the btrfs_ref transformation does the correct thing, that we do thecorrect thing when merging delayed refs, and that we get the delayedrefs in the order that we expect.  These are all crucial to how thedelayed refs operate.I introduced various bugs (including the original bug) into the delayedrefs code to validate that these tests caught all of the shenanigansthat I could think of.Reviewed-by: Boris Burkov &lt;boris@bur.io&gt;Signed-off-by: Josef Bacik &lt;josef@toxicpanda.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Makefile</description>
        <pubDate>Thu, 14 Nov 2024 15:03:34 +0000</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>506be4d5 - btrfs: tests: add selftests for raid-stripe-tree</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#506be4d5</link>
        <description>btrfs: tests: add selftests for raid-stripe-treeAdd first stash of very basic self tests for the RAID stripe-tree.More test cases will follow exercising the tree.Reviewed-by: Filipe Manana &lt;fdmanana@suse.com&gt;Signed-off-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Makefile</description>
        <pubDate>Wed, 02 Oct 2024 10:11:48 +0000</pubDate>
        <dc:creator>Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;</dc:creator>
    </item>
<item>
        <title>9aa29a20 - btrfs: move the direct IO code into its own file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#9aa29a20</link>
        <description>btrfs: move the direct IO code into its own fileThe direct IO code is over a thousand lines and it&apos;s currently spreadbetween file.c and inode.c, which makes it not easy to locate some partsof it sometimes. Also inode.c is about 11 thousand lines and file.c about4 thousand lines, both too big. So move all the direct IO code into adedicated file, so that it&apos;s easy to locate all its code and reduce thesizes of inode.c and file.c.This is a pure move of code without any other changes except export aa couple functions from inode.c (get_extent_allocation_hint() andcreate_io_em()) because they are used in inode.c and the new direct-io.cfile, and a couple functions from file.c (btrfs_buffered_write() andbtrfs_write_check()) because they are used both in file.c and in the newdirect-io.c file.Reviewed-by: Boris Burkov &lt;boris@bur.io&gt;Reviewed-by: Qu Wenruo &lt;wqu@suse.com&gt;Signed-off-by: Filipe Manana &lt;fdmanana@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Makefile</description>
        <pubDate>Tue, 25 Jun 2024 14:52:28 +0000</pubDate>
        <dc:creator>Filipe Manana &lt;fdmanana@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>8996f61a - btrfs: move fiemap code into its own file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#8996f61a</link>
        <description>btrfs: move fiemap code into its own fileCurrently the core of the fiemap code lives in extent_io.c, which doesnot make any sense because it&apos;s not related to extent IO at all (and itwas not as well before the big rewrite of fiemap I did some time ago).The entry point for fiemap, btrfs_fiemap(), lives in inode.c since it&apos;san inode operation.Since there&apos;s a significant amount of fiemap code, move all of it into adedicated file, including its entry point inode.c:btrfs_fiemap().Reviewed-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Signed-off-by: Filipe Manana &lt;fdmanana@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/Makefile</description>
        <pubDate>Wed, 22 May 2024 14:29:05 +0000</pubDate>
        <dc:creator>Filipe Manana &lt;fdmanana@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>02c372e1 - btrfs: add support for inserting raid stripe extents</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#02c372e1</link>
        <description>btrfs: add support for inserting raid stripe extentsAdd support for inserting stripe extents into the raid stripe tree oncompletion of every write that needs an extra logical-to-physicaltranslation when using RAID.Inserting the stripe extents happens after the data I/O has completed,this is done to  a) support zone-append and  b) rule out the possibility of a RAID-write-hole.Signed-off-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.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/Makefile</description>
        <pubDate>Thu, 14 Sep 2023 16:06:58 +0000</pubDate>
        <dc:creator>Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;</dc:creator>
    </item>
<item>
        <title>fb2a836d - btrfs: check-integrity: remove btrfsic_unmount() function</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#fb2a836d</link>
        <description>btrfs: check-integrity: remove btrfsic_unmount() functionThe function btrfsic_mount() is part of the deprecated check-integrityfunctionality.Now let&apos;s remove the main entry point of check-integrity, and thankfullymost of the check-integrity code is self-contained insidecheck-integrity.c, we can safely remove the function without hugechanges to btrfs code base.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/Makefile</description>
        <pubDate>Fri, 08 Sep 2023 06:42:16 +0000</pubDate>
        <dc:creator>Qu Wenruo &lt;wqu@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>90b90d4a - btrfs: send: genericize the backref cache to allow it to be reused</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#90b90d4a</link>
        <description>btrfs: send: genericize the backref cache to allow it to be reusedThe backref cache is a cache backed by a maple tree and a linked list tokeep track of temporal access to cached entries (the LRU entry always atthe head of the list). This type of caching method is going to be usefulin other scenarios, so make the cache implementation more generic andmove it into its own header and source files.This patch is part of a larger patchset and the changelog of the lastpatch in the series contains a sample performance test and results.The patches that comprise the patchset are the following:  btrfs: send: directly return from did_overwrite_ref() and simplify it  btrfs: send: avoid unnecessary generation search at did_overwrite_ref()  btrfs: send: directly return from will_overwrite_ref() and simplify it  btrfs: send: avoid extra b+tree searches when checking reference overrides  btrfs: send: remove send_progress argument from can_rmdir()  btrfs: send: avoid duplicated orphan dir allocation and initialization  btrfs: send: avoid unnecessary orphan dir rbtree search at can_rmdir()  btrfs: send: reduce searches on parent root when checking if dir can be removed  btrfs: send: iterate waiting dir move rbtree only once when processing refs  btrfs: send: initialize all the red black trees earlier  btrfs: send: genericize the backref cache to allow it to be reused  btrfs: adapt lru cache to allow for 64 bits keys on 32 bits systems  btrfs: send: cache information about created directories  btrfs: allow a generation number to be associated with lru cache entries  btrfs: add an api to delete a specific entry from the lru cache  btrfs: send: use the lru cache to implement the name cache  btrfs: send: update size of roots array for backref cache entries  btrfs: send: cache utimes operations for directories if possibleSigned-off-by: Filipe Manana &lt;fdmanana@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/Makefile</description>
        <pubDate>Wed, 11 Jan 2023 11:36:13 +0000</pubDate>
        <dc:creator>Filipe Manana &lt;fdmanana@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>1ec49744 - btrfs: turn on -Wmaybe-uninitialized</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#1ec49744</link>
        <description>btrfs: turn on -Wmaybe-uninitializedWe had a recent bug that would have been caught by a newer compiler with-Wmaybe-uninitialized and would have saved us a month of failing teststhat I didn&apos;t have time to investigate.Reviewed-by: Qu Wenruo &lt;wqu@suse.com&gt;Signed-off-by: Josef Bacik &lt;josef@toxicpanda.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/Makefile</description>
        <pubDate>Fri, 16 Dec 2022 20:15:58 +0000</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>103c1972 - btrfs: split the bio submission path into a separate file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#103c1972</link>
        <description>btrfs: split the bio submission path into a separate fileThe code used by btrfs_submit_bio only interacts with the rest ofvolumes.c through __btrfs_map_block (which itself is a more genericversion of two exported helpers) and does not really have anythingto do with volumes.c.  Create a new bio.c file and a bio.h headergoing along with it for the btrfs_bio-based storage layer, whichwill grow even more going forward.Also update the file with my copyright notice given that a largepart of the moved code was written or rewritten by me.Reviewed-by: Josef Bacik &lt;josef@toxicpanda.com&gt;Reviewed-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&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/Makefile</description>
        <pubDate>Tue, 15 Nov 2022 09:44:05 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>778dd695 - btrfs: rename tree-defrag.c to defrag.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#778dd695</link>
        <description>btrfs: rename tree-defrag.c to defrag.cThis currently has only one helper in it, and it&apos;s for tree baseddefrag.  We have the various defrag code in 3 different places, sorename this to defrag.c.  Followup patches will move the code into thisnew file.Reviewed-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Signed-off-by: Josef Bacik &lt;josef@toxicpanda.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/Makefile</description>
        <pubDate>Wed, 26 Oct 2022 19:08:22 +0000</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>083bd7e5 - btrfs: move the printk and assert helpers to messages.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#083bd7e5</link>
        <description>btrfs: move the printk and assert helpers to messages.cThese helpers are core to btrfs, and in order to more easily syncvarious parts of the btrfs kernel code into btrfs-progs we need to beable to carry these helpers with us.  However we want to have our ownimplementation for the helpers themselves, currently they&apos;re implementedin different files that we want to sync inside of btrfs-progs itself.Move these into their own C file, this will allow us to contain ouroverrides in btrfs-progs in it&apos;s own file without messing with the restof the codebase.In copying things over I fixed up a few whitespace errors that alreadyexisted.Signed-off-by: Josef Bacik &lt;josef@toxicpanda.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/Makefile</description>
        <pubDate>Wed, 26 Oct 2022 19:08:20 +0000</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>818fe33a - btrfs: rename struct-funcs.c to accessors.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#818fe33a</link>
        <description>btrfs: rename struct-funcs.c to accessors.cRename struct-funcs.c to accessors.c so we can move the item accessorsout of ctree.h. accessors.c is a better description of the code that iscontained in these files.Reviewed-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Reviewed-by: Anand Jain &lt;anand.jain@oracle.com&gt;Signed-off-by: Josef Bacik &lt;josef@toxicpanda.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/Makefile</description>
        <pubDate>Wed, 19 Oct 2022 14:50:58 +0000</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>c7f13d42 - btrfs: move fs wide helpers out of ctree.h</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#c7f13d42</link>
        <description>btrfs: move fs wide helpers out of ctree.hWe have several fs wide related helpers in ctree.h.  The bulk of theseare the incompat flag test helpers, but there are things such asbtrfs_fs_closing() and the read only helpers that also aren&apos;t directlyrelated to the ctree code.  Move these into a fs.h header, which willserve as the location for file system wide related helpers.Reviewed-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Reviewed-by: Anand Jain &lt;anand.jain@oracle.com&gt;Signed-off-by: Josef Bacik &lt;josef@toxicpanda.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/Makefile</description>
        <pubDate>Wed, 19 Oct 2022 14:50:47 +0000</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>83cf709a - btrfs: move extent state init and alloc functions to their own file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#83cf709a</link>
        <description>btrfs: move extent state init and alloc functions to their own fileStart cleaning up extent_io.c by moving the extent state code out of it.This patch starts with the extent state allocation code and theextent_io_tree init code.Signed-off-by: Josef Bacik &lt;josef@toxicpanda.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/Makefile</description>
        <pubDate>Fri, 09 Sep 2022 21:53:21 +0000</pubDate>
        <dc:creator>Josef Bacik &lt;josef@toxicpanda.com&gt;</dc:creator>
    </item>
<item>
        <title>1344794a - Kbuild: add -Wno-shift-negative-value where -Wextra is used</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#1344794a</link>
        <description>Kbuild: add -Wno-shift-negative-value where -Wextra is usedAs a preparation for moving to -std=gnu11, turn off the-Wshift-negative-value option. This warning is enabled by gcc whenbuilding with -Wextra for c99 or higher, but not for c89. Sincethe kernel already relies on well-defined overflow behavior,the warning is not helpful and can simply be disabled inall locations that use -Wextra.Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Acked-by: Jani Nikula &lt;jani.nikula@intel.com&gt;Reviewed-by: Nathan Chancellor &lt;nathan@kernel.org&gt;Tested-by: Sedat Dilek &lt;sedat.dilek@gmail.com&gt; # LLVM/Clang v13.0.0 (x86-64)Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/fs/btrfs/Makefile</description>
        <pubDate>Tue, 08 Mar 2022 21:56:12 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>f26c9238 - btrfs: remove reada infrastructure</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#f26c9238</link>
        <description>btrfs: remove reada infrastructureCurrently there is only one user for btrfs metadata readahead, andthat&apos;s scrub.But even for the single user, it&apos;s not providing the correctfunctionality it needs, as scrub needs reada for commit root, whichcurrent readahead can&apos;t provide. (Although it&apos;s pretty easy to add suchfeature).Despite this, there are some extra problems related to metadatareadahead:- Duplicated feature with btrfs_path::reada- Partly duplicated feature of btrfs_fs_info::buffer_radix  Btrfs already caches its metadata in buffer_radix, while readahead  tries to read the tree block no matter if it&apos;s already cached.- Poor layer separation  Metadata readahead works kinda at device level.  This is definitely not the correct layer it should be, since metadata  is at btrfs logical address space, it should not bother device at all.  This brings extra chance for bugs to sneak in, while brings  unnecessary complexity.- Dead code  In the very beginning of scrub.c we have #undef DEBUG, rendering all  the debug related code useless and unable to test.Thus here I purpose to remove the metadata readahead mechanismcompletely.[BENCHMARK]There is a full benchmark for the scrub performance difference using theold btrfs_reada_add() and btrfs_path::reada.For the worst case (no dirty metadata, slow HDD), there could be a 5%performance drop for scrub.For other cases (even SATA SSD), there is no distinguishable performancedifference.The number is reported scrub speed, in MiB/s.The resolution is limited by the reported duration, which only has aresolution of 1 second.	Old		New		DiffSSD	455.3		466.332		+2.42%HDD	103.927 	98.012		-5.69%Comprehensive test methodology is in the cover letter of the patch.Signed-off-by: Qu Wenruo &lt;wqu@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Makefile</description>
        <pubDate>Tue, 14 Dec 2021 13:01:45 +0000</pubDate>
        <dc:creator>Qu Wenruo &lt;wqu@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>14605409 - btrfs: initial fsverity support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#14605409</link>
        <description>btrfs: initial fsverity supportAdd support for fsverity in btrfs. To support the generic interface infs/verity, we add two new item types in the fs tree for inodes withverity enabled. One stores the per-file verity descriptor and btrfsverity item and the other stores the Merkle tree data itself.Verity checking is done in end_page_read just before a page is markeduptodate. This naturally handles a variety of edge cases like holes,preallocated extents, and inline extents. Some care needs to be taken tonot try to verity pages past the end of the file, which are accessed bythe generic buffered file reading code under some circumstances likereading to the end of the last page and trying to read again. Direct IOon a verity file falls back to buffered reads.Verity relies on PageChecked for the Merkle tree data itself to avoidre-walking up shared paths in the tree. For this reason, we need tocache the Merkle tree data. Since the file is immutable after verity isturned on, we can cache it at an index past EOF.Use the new inode ro_flags to store verity on the inode item, so that wecan enable verity on a file, then rollback to an older kernel and stillmount the file system and read the file. Since we can&apos;t safely write thefile anymore without ruining the invariants of the Merkle tree, we marka ro_compat flag on the file system when a file has verity enabled.Acked-by: Eric Biggers &lt;ebiggers@google.com&gt;Co-developed-by: Chris Mason &lt;clm@fb.com&gt;Signed-off-by: Chris Mason &lt;clm@fb.com&gt;Signed-off-by: Boris Burkov &lt;boris@bur.io&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/Makefile</description>
        <pubDate>Wed, 30 Jun 2021 20:01:49 +0000</pubDate>
        <dc:creator>Boris Burkov &lt;boris@bur.io&gt;</dc:creator>
    </item>
<item>
        <title>f3a84ccd - btrfs: move the tree mod log code into its own file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#f3a84ccd</link>
        <description>btrfs: move the tree mod log code into its own fileThe tree modification log, which records modifications done to btrees, isquite large and currently spread all over ctree.c, which is a huge filealready.To make things better organized, move all that code into its own separatesource and header files. Functions and definitions that are used outsideof the module (mostly by ctree.c) are renamed so that they start with a&quot;btrfs_&quot; prefix. Everything else remains unchanged.This makes it easier to go over the tree modification log code everytime I need to go read it to fix a bug.Reviewed-by: Anand Jain &lt;anand.jain@oracle.com&gt;Signed-off-by: Filipe Manana &lt;fdmanana@suse.com&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;[ minor comment updates ]Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Makefile</description>
        <pubDate>Thu, 11 Mar 2021 14:31:07 +0000</pubDate>
        <dc:creator>Filipe Manana &lt;fdmanana@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>ebd99a6b - btrfs: fix build when using M=fs/btrfs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#ebd99a6b</link>
        <description>btrfs: fix build when using M=fs/btrfsThere are people building the module with M= that&apos;s supposed to be usedfor external modules. This got broken in e9aa7c285d20 (&quot;btrfs: enableW=1 checks for btrfs&quot;).  $ make M=fs/btrfs  scripts/Makefile.lib:10: *** Recursive variable &apos;KBUILD_CFLAGS&apos; references itself (eventually).  Stop.  make: *** [Makefile:1755: modules] Error 2There&apos;s a difference compared to &apos;make fs/btrfs/btrfs.ko&apos; which needsto rebuild a few more things and also the dependency modules need to beavailable. It could fail with eg.  WARNING: Symbol version dump &quot;Module.symvers&quot; is missing.	   Modules may not have dependencies or modversions.In some environments it&apos;s more convenient to rebuild just the btrfsmodule by M= so let&apos;s make it work.The problem is with recursive variable evaluation in += so theconditional C options are stored in a temporary variable to avoid therecursion.Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/fs/btrfs/Makefile</description>
        <pubDate>Wed, 17 Mar 2021 10:43:13 +0000</pubDate>
        <dc:creator>David Sterba &lt;dsterba@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>cac06d84 - btrfs: introduce the skeleton of btrfs_subpage structure</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/btrfs/Makefile#cac06d84</link>
        <description>btrfs: introduce the skeleton of btrfs_subpage structureFor sectorsize &lt; page size support, we need a structure to record extrastatus info for each sector of a page.Introduce the skeleton structure, all subpage related code would go tosubpage.[ch].Reviewed-by: Josef Bacik &lt;josef@toxicpanda.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/Makefile</description>
        <pubDate>Tue, 26 Jan 2021 08:33:47 +0000</pubDate>
        <dc:creator>Qu Wenruo &lt;wqu@suse.com&gt;</dc:creator>
    </item>
</channel>
</rss>
