linux-kernel - Re: [linus:master] [block] 245618f8e4: stress-ng.fpunch.fail

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aDe9y3Ef+TEacRr3@xsang-OptiPlex-9020>
Date: Thu, 29 May 2025 09:52:11 +0800
From: Oliver Sang <oliver.sang@...el.com>
To: Nilay Shroff <nilay@...ux.ibm.com>
CC: <oe-lkp@...ts.linux.dev>, <lkp@...el.com>, <linux-kernel@...r.kernel.org>,
	Jens Axboe <axboe@...nel.dk>, Christoph Hellwig <hch@....de>, Hannes Reinecke
	<hare@...e.de>, Ming Lei <ming.lei@...hat.com>, <cgroups@...r.kernel.org>,
	<linux-block@...r.kernel.org>, <oliver.sang@...el.com>
Subject: Re: [linus:master] [block] 245618f8e4: stress-ng.fpunch.fail

hi, Nilay,

sorry for late.

On Thu, May 22, 2025 at 06:07:21PM +0530, Nilay Shroff wrote:
> 

[...]

> > 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/202505221030.760980df-lkp@intel.com
> > 
> > 2025-03-20 08:33:52 mkdir -p /mnt/stress-ng
> > 2025-03-20 08:33:52 mount /dev/sdc1 /mnt/stress-ng
> > 2025-03-20 08:33:52 cd /mnt/stress-ng
> >   File: "/mnt/stress-ng"
> >     ID: 82100000000 Namelen: 255     Type: xfs
> > Block size: 4096       Fundamental block size: 4096
> > Blocks: Total: 78604800   Free: 78518242   Available: 78518242
> > Inodes: Total: 157286400  Free: 157286397
> > 2025-03-20 08:33:52 stress-ng --timeout 60 --times --verify --metrics --no-rand-seed --fpunch 128
> > stress-ng: info:  [4680] setting to a 1 min run per stressor
> > stress-ng: info:  [4680] dispatching hogs: 128 fpunch
> > stress-ng: info:  [4680] note: /proc/sys/kernel/sched_autogroup_enabled is 1 and this can impact scheduling throughput for processes not attached to a tty. Setting this to 0 may improve performance metrics
> > stress-ng: warn:  [4680] metrics-check: all bogo-op counters are zero, data may be incorrect
> > stress-ng: metrc: [4680] stressor       bogo ops real time  usr time  sys time   bogo ops/s     bogo ops/s CPU used per       RSS Max
> > stress-ng: metrc: [4680]                           (secs)    (secs)    (secs)   (real time) (usr+sys time) instance (%)          (KB)
> > stress-ng: metrc: [4680] fpunch                0    557.92      0.40     19.56         0.00           0.00         0.03          3180
> > stress-ng: metrc: [4680] miscellaneous metrics:
> > stress-ng: metrc: [4680] fpunch              2049.12 extents per file (geometric mean of 128 instances)
> > stress-ng: info:  [4680] for a 620.45s run time:
> > stress-ng: info:  [4680]   79418.05s available CPU time
> > stress-ng: info:  [4680]       0.40s user time   (  0.00%)
> > stress-ng: info:  [4680]      19.59s system time (  0.02%)
> > stress-ng: info:  [4680]      19.99s total time  (  0.03%)
> > stress-ng: info:  [4680] load average: 250.69 349.62 213.80
> > stress-ng: info:  [4680] skipped: 0
> > stress-ng: info:  [4680] passed: 128: fpunch (128)
> > stress-ng: info:  [4680] failed: 0
> > stress-ng: info:  [4680] metrics untrustworthy: 0
> > stress-ng: info:  [4680] successful run completed in 10 mins, 20.45 secs
> > 

[...]

> > 
> > The kernel config and materials to reproduce are available at:
> > https://download.01.org/0day-ci/archive/20250522/202505221030.760980df-lkp@intel.com
> > 
> 
> I tried reproducing this issue but I couldn't recreate it. Is it possible
> for you to run this test on your setup using stress-ng option "--iostat 1"
> as shown below ?
> 
> # stress-ng --timeout 60 --times --verify --metrics --no-rand-seed --fpunch 128 --iostat 1
> 
> If you can run test with above option then please collect logs and share it.
> That might help to further debug this.

the log is attached as stress-ng-245618f8e4.
also attached the dmesg-245618f8e4.xz.

another log from parent is attached as stress-ng-3efe7571c3.

> 
> Thanks,
> --Nilay
> 

View attachment "stress-ng-3efe7571c3" of type "text/plain" (7901 bytes)

View attachment "stress-ng-245618f8e4" of type "text/plain" (63111 bytes)

Download attachment "dmesg-245618f8e4.xz" of type "application/x-xz" (37124 bytes)