From: Mark Brown <broonie@kernel.org>
To: David Sterba <dsterba@suse.cz>
Cc: David Sterba <dsterba@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Qu Wenruo <wqu@suse.com>
Subject: linux-next: manual merge of the btrfs tree with the btrfs-fixes tree
Date: Tue, 17 Mar 2026 13:48:10 +0000 [thread overview]
Message-ID: <ablbmhRJcTwgE7k3@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2357 bytes --]
Hi all,
Today's linux-next merge of the btrfs tree got a conflict in:
fs/btrfs/compression.c
between commits:
65ee6061388b3 ("btrfs: fix a bug that makes encoded write bio larger than expected")
3adf8f14152fb ("btrfs: do not touch page cache for encoded writes")
from the btrfs-fixes tree and commits:
c18bcdc0422e9 ("btrfs: reduce the size of compressed_bio")
d634a62ed907c ("btrfs: do not touch page cache for encoded writes")
bd2e495aacd58 ("btrfs: fix a bug that makes encoded write bio larger than expected")
from the btrfs tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --combined fs/btrfs/compression.c
index 85199944c1ebe,192f133d9eb58..0000000000000
--- a/fs/btrfs/compression.c
+++ b/fs/btrfs/compression.c
@@@ -224,7 -224,6 +224,6 @@@ void btrfs_free_compr_folio(struct foli
return;
free:
- ASSERT(folio_ref_count(folio) == 1);
folio_put(folio);
}
@@@ -292,7 -291,7 +291,7 @@@ static void end_bbio_compressed_write(s
struct compressed_bio *cb = to_compressed_bio(bbio);
struct folio_iter fi;
- btrfs_finish_ordered_extent(cb->bbio.ordered, NULL, cb->start, cb->len,
+ btrfs_finish_ordered_extent(cb->bbio.ordered, cb->start, cb->len,
cb->bbio.bio.bi_status == BLK_STS_OK);
if (cb->writeback)
@@@ -330,7 -329,6 +329,6 @@@ void btrfs_submit_compressed_write(stru
cb->start = ordered->file_offset;
cb->len = ordered->num_bytes;
ASSERT(cb->bbio.bio.bi_iter.bi_size == ordered->disk_num_bytes);
- cb->compressed_len = ordered->disk_num_bytes;
cb->bbio.bio.bi_iter.bi_sector = ordered->disk_bytenr >> SECTOR_SHIFT;
cb->bbio.ordered = ordered;
@@@ -560,7 -558,6 +558,6 @@@ void btrfs_submit_compressed_read(struc
em_start = em->start;
cb->len = bbio->bio.bi_iter.bi_size;
- cb->compressed_len = compressed_len;
cb->compress_type = btrfs_extent_map_compression(em);
cb->orig_bbio = bbio;
cb->bbio.csum_search_commit_root = bbio->csum_search_commit_root;
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-03-17 13:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 13:48 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-24 13:25 linux-next: manual merge of the btrfs tree with the btrfs-fixes tree Mark Brown
2026-03-24 13:25 Mark Brown
2026-03-17 13:48 Mark Brown
2026-03-17 13:48 Mark Brown
2025-09-18 11:26 Mark Brown
2024-06-06 22:55 Stephen Rothwell
2024-06-06 23:12 ` Qu Wenruo
2023-10-04 23:09 Stephen Rothwell
2022-10-31 23:28 Stephen Rothwell
2022-09-05 23:50 Stephen Rothwell
2022-09-06 0:15 ` Stephen Rothwell
2022-09-06 19:41 ` David Sterba
2022-03-24 23:48 Stephen Rothwell
2022-02-24 13:44 broonie
2022-02-25 11:59 ` David Sterba
2021-01-10 22:29 Stephen Rothwell
2020-05-01 0:28 Stephen Rothwell
2020-05-03 21:40 ` David Sterba
2020-05-01 0:24 Stephen Rothwell
2020-05-01 1:05 ` Stephen Rothwell
2020-05-01 2:06 ` Qu Wenruo
2020-01-08 22:14 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ablbmhRJcTwgE7k3@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=wqu@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox