From: kernel test robot <yi1.lai@intel.com>
To: Haoran Wang <haoranwangsec@gmail.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-f2fs-devel@lists.sourceforge.net, ltp@lists.linux.it,
jaegeuk@kernel.org, chao@kernel.org,
linux-kernel@vger.kernel.org, haoranwangsec@gmail.com,
yi1.lai@intel.com
Subject: Re: [PATCH] f2fs: verify inode data-block ownership at mount
Date: Tue, 27 Oct 2026 10:14:46 +0800 [thread overview]
Message-ID: <202610262143.a92547a9-lkp@intel.com> (raw)
In-Reply-To: <6ad2359d.0083e9c2.97e0f.79de@mx.google.com>
Hello,
kernel test robot noticed "last_state.incomplete/bootup failure" on:
commit: 612a9db3132785844663564c15691d5feac8a259 ("[PATCH] f2fs: verify inode data-block ownership at mount")
url: https://github.com/intel-lab-lkp/linux/commits/Haoran-Wang/f2fs-verify-inode-data-block-ownership-at-mount/20261016-223258
base: v7.3-rc7
patch link: https://lore.kernel.org/all/6ad2359d.0083e9c2.97e0f.79de@mx.google.com/
patch subject: [PATCH] f2fs: verify inode data-block ownership at mount
in testcase: ltp
version: ltp-x86_64-af1ad307f-1_20261024 with following parameters:
disk: 1HDD
fs: f2fs
test: ltp-aiodio.part2-02
config: x86_64-rhel-9.4-ltp
compiler: gcc-14
test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (Ivy Bridge) with 8G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
[ +3.766884] [ T594] mount: /fs/sda1: fsconfig() failed: Structure needs cleaning.
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 <yi1.lai@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202610262143.a92547a9-lkp@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20261026/202610262143.a92547a9-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-10-27 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 14:32 Haoran Wang
2026-10-27 2:14 ` kernel test robot [this message]
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=202610262143.a92547a9-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=chao@kernel.org \
--cc=haoranwangsec@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®