mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Rajeev Mishra <rajeevm@hpe.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-block@vger.kernel.org>, <axboe@kernel.dk>,
	<linux-kernel@vger.kernel.org>, Rajeev Mishra <rajeevm@hpe.com>,
	<oliver.sang@intel.com>
Subject: Re: [PATCH 1/1] loop: sync filesystem cache before getting file size in get_size()
Date: Fri, 15 Aug 2025 11:25:53 +0800	[thread overview]
Message-ID: <202508150425.33b5498e-lkp@intel.com> (raw)
In-Reply-To: <20250807232522.192898-1-rajeevm@hpe.com>



Hello,

kernel test robot noticed "blktests.loop/004.fail" on:

commit: 081158bd768a2a4b4fc6108abc3d4ee51bfdbf6e ("[PATCH 1/1] loop: sync filesystem cache before getting file size in get_size()")
url: https://github.com/intel-lab-lkp/linux/commits/Rajeev-Mishra/loop-sync-filesystem-cache-before-getting-file-size-in-get_size/20250808-073617
base: https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-block.git for-next
patch link: https://lore.kernel.org/all/20250807232522.192898-1-rajeevm@hpe.com/
patch subject: [PATCH 1/1] loop: sync filesystem cache before getting file size in get_size()

in testcase: blktests
version: blktests-x86_64-a08678c-1_20250813
with following parameters:

	test: loop-004



config: x86_64-rhel-9.4-func
compiler: gcc-12
test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) 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/202508150425.33b5498e-lkp@intel.com

2025-08-14 08:21:17 echo loop/004
2025-08-14 08:21:17 ./check loop/004
loop/004 (combine loop direct I/O mode and a custom block size)
loop/004 (combine loop direct I/O mode and a custom block size) [failed]
    runtime    ...  0.668s
    --- tests/loop/004.out	2025-08-13 07:46:30.000000000 +0000
    +++ /lkp/benchmarks/blktests/results/nodev/loop/004.out.bad	2025-08-14 08:21:18.595234684 +0000
    @@ -1,4 +1,5 @@
     Running loop/004
     1
    -769bd186841c10e5b1106b55986206c0e87fc05a7f565fdee01b5abcaff6ae78  -
    +pwrite: No space left on device
    +e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855  -
     Test complete



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250815/202508150425.33b5498e-lkp@intel.com



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


  parent reply	other threads:[~2025-08-15  3:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-07 23:25 Rajeev Mishra
2025-08-08  2:47 ` Yu Kuai
     [not found]   ` <PH7PR84MB2079A6A4EFE799BCA7E5738CAA2FA@PH7PR84MB2079.NAMPRD84.PROD.OUTLOOK.COM>
2025-08-11  1:20     ` Yu Kuai
2025-08-10 15:15 ` Christoph Hellwig
2025-08-15  3:25 ` kernel test robot [this message]
2025-08-08 18:59 Cloud User
2025-08-08 19:03 Cloud User

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=202508150425.33b5498e-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=rajeevm@hpe.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

all inboxes | Powered by JetHome®