From: kernel test robot <oliver.sang@intel.com>
To: MottiKumar Babu <mottikumarbabu@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-xfs@vger.kernel.org>, <cem@kernel.org>,
<djwong@kernel.org>, <chandanbabu@kernel.org>,
<dchinner@redhat.com>, <zhangjiachen.jaycee@bytedance.com>,
<linux-kernel@vger.kernel.org>,
<linux-kernel-mentees@lists.linux.dev>, <anupnewsmail@gmail.com>,
<skhan@linuxfoundation.org>, <oliver.sang@intel.com>
Subject: Re: [PATCH] Fix out-of-bounds access in xfs_bmapi_allocate by validating whichfork
Date: Fri, 1 Nov 2024 11:36:12 +0800 [thread overview]
Message-ID: <202411011120.8d4b756-oliver.sang@intel.com> (raw)
In-Reply-To: <20241027193541.14212-1-mottikumarbabu@gmail.com>
Hello,
kernel test robot noticed "xfstests.xfs.221.fail" on:
commit: fc3ce21bdce1661bf1b4af5579a7c72c483b0856 ("[PATCH] Fix out-of-bounds access in xfs_bmapi_allocate by validating whichfork")
url: https://github.com/intel-lab-lkp/linux/commits/MottiKumar-Babu/Fix-out-of-bounds-access-in-xfs_bmapi_allocate-by-validating-whichfork/20241028-033645
base: https://git.kernel.org/cgit/fs/xfs/xfs-linux.git for-next
patch link: https://lore.kernel.org/all/20241027193541.14212-1-mottikumarbabu@gmail.com/
patch subject: [PATCH] Fix out-of-bounds access in xfs_bmapi_allocate by validating whichfork
in testcase: xfstests
version: xfstests-x86_64-891f4995-1_20241028
with following parameters:
disk: 4HDD
fs: xfs
test: xfs-221
config: x86_64-rhel-8.3-func
compiler: gcc-12
test machine: 4 threads Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz (Skylake) with 16G 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/202411011120.8d4b756-oliver.sang@intel.com
2024-10-31 14:35:22 export TEST_DIR=/fs/sda1
2024-10-31 14:35:22 export TEST_DEV=/dev/sda1
2024-10-31 14:35:22 export FSTYP=xfs
2024-10-31 14:35:22 export SCRATCH_MNT=/fs/scratch
2024-10-31 14:35:22 mkdir /fs/scratch -p
2024-10-31 14:35:22 export SCRATCH_DEV=/dev/sda4
2024-10-31 14:35:22 export SCRATCH_LOGDEV=/dev/sda2
2024-10-31 14:35:22 export SCRATCH_XFS_LIST_METADATA_FIELDS=u3.sfdir3.hdr.parent.i4
2024-10-31 14:35:22 export SCRATCH_XFS_LIST_FUZZ_VERBS=random
2024-10-31 14:35:22 export MKFS_OPTIONS="-mreflink=1 "
2024-10-31 14:35:22 echo xfs/221
2024-10-31 14:35:22 ./check xfs/221
FSTYP -- xfs (debug)
PLATFORM -- Linux/x86_64 lkp-skl-d06 6.12.0-rc2-00034-gfc3ce21bdce1 #1 SMP PREEMPT_DYNAMIC Mon Oct 28 04:16:50 CST 2024
MKFS_OPTIONS -- -f -mreflink=1 /dev/sda4
MOUNT_OPTIONS -- /dev/sda4 /fs/scratch
xfs/221 - output mismatch (see /lkp/benchmarks/xfstests/results//xfs/221.out.bad)
--- tests/xfs/221.out 2024-10-28 16:28:46.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//xfs/221.out.bad 2024-10-31 14:35:30.136173763 +0000
@@ -8,6 +8,6 @@
CoW across the transition
Compare files
bdbcf02ee0aa977795a79d25fcfdccb1 SCRATCH_MNT/test-221/file1
-09101629908f9bdd5d178e7ce20bb1bb SCRATCH_MNT/test-221/file3
+fa50dba51826899c372464a153cb2117 SCRATCH_MNT/test-221/file3
09101629908f9bdd5d178e7ce20bb1bb SCRATCH_MNT/test-221/file3.chk
Check extent counts
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/xfs/221.out /lkp/benchmarks/xfstests/results//xfs/221.out.bad' to see the entire diff)
Ran: xfs/221
Failures: xfs/221
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241101/202411011120.8d4b756-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-11-01 3:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 19:35 [PATCH] Fix out-of-bounds access in xfs_bmapi_allocate by validating whichfork MottiKumar Babu
2024-10-27 20:32 ` [PATCH] Follow-up on Submitted Patch: Fix out-of-bounds access in xfs_bmapi_allocate MottiKumar Babu
2024-10-27 22:53 ` [PATCH] Fix out-of-bounds access in xfs_bmapi_allocate by validating whichfork Dave Chinner
2024-10-28 8:46 ` Christoph Hellwig
2024-11-01 3:36 ` 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=202411011120.8d4b756-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=anupnewsmail@gmail.com \
--cc=cem@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mottikumarbabu@gmail.com \
--cc=oe-lkp@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=zhangjiachen.jaycee@bytedance.com \
/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