linux-kernel - linux-next: manual merge of the btrfs tree with the btrfs-fixes tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <aMvsbkR_l3ZHwP0O@sirena.org.uk>
Date: Thu, 18 Sep 2025 12:26:38 +0100
From: Mark Brown <broonie@...nel.org>
To: David Sterba <dsterba@...e.cz>
Cc: David Sterba <dsterba@...e.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>,
	Qu Wenruo <wqu@...e.com>
Subject: linux-next: manual merge of the btrfs tree with the btrfs-fixes tree

Hi all,

Today's linux-next merge of the btrfs tree got a conflict in:

  fs/btrfs/compression.c

between commit:

  4b63a8a8330e2 ("btrfs: reject invalid compression level")

from the btrfs-fixes tree and commit:

  6e8a10e90f2d4 ("btrfs: reject invalid compression level")

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 --cc fs/btrfs/compression.c
index 5329712d5dfb0,c865e0f2a7e87..0000000000000
--- a/fs/btrfs/compression.c
+++ b/fs/btrfs/compression.c

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)