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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <07476afd-45b0-4b08-a6db-e5c72f128594@sirena.org.uk>
Date: Tue, 20 Jan 2026 12:32:15 +0000
From: Mark Brown <broonie@...nel.org>
To: Johannes Thumshirn <Johannes.Thumshirn@....com>
Cc: David Sterba <dsterba@...e.cz>, Boris Burkov <boris@....io>,
	WenRuo Qu <wqu@...e.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the btrfs-fixes tree

On Tue, Jan 20, 2026 at 12:22:37PM +0000, Johannes Thumshirn wrote:
> On 1/20/26 1:08 PM, Mark Brown wrote:

> > /tmp/next/build/fs/btrfs/free-space-tree.c:1765:33: error: 'path' undeclared (first use in this function)
> >   1765 |         BTRFS_PATH_AUTO_RELEASE(path);
> >        |                                 ^~~~

> This got introduced by

> a08c5941d3ae ("btrfs: add mount time auto fix for orphan fst entries")

> and 'BTRFS_PATH_AUTO_RELEASE()' got introduced by:

> 675af3c0fbd8 ("btrfs: introduce BTRFS_PATH_AUTO_RELEASE() helper")

> which might be missing in for-next or btrfs-fixes?

It's in for-next but not in btrfs-fixes.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ