All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>, <linux-bcachefs@vger.kernel.org>,
	<oliver.sang@intel.com>
Subject: [linus:master] [bcachefs]  cd3cdb1ef7: last_state.incomplete
Date: Wed, 28 May 2025 14:31:37 +0800	[thread overview]
Message-ID: <202505281410.cca50993-lkp@intel.com> (raw)



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@intel.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] 

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


             reply	other threads:[~2025-05-28  6:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28  6:31 kernel test robot [this message]
2025-05-28  7:05 ` [linus:master] [bcachefs] cd3cdb1ef7: last_state.incomplete Kent Overstreet

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=202505281410.cca50993-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.