linux-kernel - Re: [linus:master] [bcachefs] cd3cdb1ef7: last

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] [day] [month] [year] [list]

Message-ID: <uab4hrzt77vunesxicyovjpqvoegqo6tozsb4lndj4c2udcq5f@dbicbg2jyw2i>
Date: Wed, 28 May 2025 03:05:01 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: kernel test robot <oliver.sang@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com, linux-kernel@...r.kernel.org, 
	linux-bcachefs@...r.kernel.org
Subject: Re: [linus:master] [bcachefs]  cd3cdb1ef7: last_state.incomplete

On Wed, May 28, 2025 at 02:31:37PM +0800, kernel test robot wrote:
> 
> 
> Hello,
> 
> 
> for this change, we reported
> "[koverstreet-bcachefs:bcachefs-put-folio-assert] [bcachefs] 0718bafa21: last_state.incomplete"
> in
> https://lore.kernel.org/all/202505081551.92a07edd-lkp@intel.com/ [1]
> upon Ice Lake.
> 
> now we notice the commit is in mainline, and we captured similar issue on
> another platform.
> 
> below full report FYI.
> 
> 
> kernel test robot noticed "last_state.incomplete" on:
> 
> commit: cd3cdb1ef706a1ac725194d81858d58375739b25 ("bcachefs: Single err message for btree node reads")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> 
> [test failed on linus/master      914873bc7df913db988284876c16257e6ab772c6]
> [test failed on linux-next/master fefff2755f2aa4125dce2a1edfe7e545c7c621f2]
> 
> in testcase: xfstests
> version: xfstests-x86_64-e161fc34-1_20250526
> with following parameters:
> 
> 	disk: 4HDD
> 	fs: bcachefs
> 	test: generic-group-67
> 
> 
> 
> config: x86_64-rhel-9.4-func
> compiler: gcc-12
> test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (Kaby Lake) with 32G memory
> 
> (please refer to attached dmesg/kmsg for entire log/backtrace)
> 
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <oliver.sang@...el.com>
> | Closes: https://lore.kernel.org/oe-lkp/202505281410.cca50993-lkp@intel.com
> 
> 
> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20250528/202505281410.cca50993-lkp@intel.com
> 
> 
> similar as report [1], from the dmesg in above link, we still didn't see any
> Call Trace, but below informations
> 
> 
> [   41.372233][ T1447] bcachefs (sda1): starting version 1.13: inode_has_child_snapshots
> [   41.372233][ T1447]   allowing incompatible features above 0.0: (unknown version)
> [   41.387511][ T1447] bcachefs (sda1): recovering from clean shutdown, journal seq 20
> [   41.395125][ T1447] bcachefs (sda1): Doing compatible version upgrade from 1.13: inode_has_child_snapshots to 1.25: extent_flags
> [   41.395125][ T1447]   running recovery passes: check_allocations,check_extents_to_backpointers
> [   41.418989][  T335] LKP: stdout: 307: Kernel tests: Boot OK!
> [   41.418998][  T335] 
> [   41.494922][ T1447] bcachefs (sda1): error reading btree root btree=accounting level=0: btree_node_read_error, fixing
> [   41.505517][ T1447] bcachefs (sda1): bch2_fs_recovery(): error btree_node_read_error
> [   41.513201][ T1447] bcachefs (sda1): bch2_fs_start(): error starting filesystem btree_node_read_error
> [   41.874130][ T1447] bcachefs: bch2_fs_get_tree() error: btree_node_read_error
> [   46.990004][  T335] LKP: stdout: 307: HOSTNAME lkp-kbl-d01, MAC 48:4d:7e:be:54:6f, kernel 6.15.0-rc4-00141-gcd3cdb1ef706 1
> [   46.990016][  T335] 
> [   47.103180][  T337] mount: /fs/sda1: can't read superblock on /dev/sda1.
> [   47.103189][  T337] 
> [   49.036739][  T337]        dmesg(1) may have more information after failed mount system call.
> [   49.036751][  T337] 

Err, what is this?

Is this a fuzz test, something from a test suite I've never heard of?
The log certainly doesn't give any useful context.