linux-kernel - Re: stalling IO regression since linux 5.12, through 5.18

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: <568465de-5c3b-4d94-a74b-5b83ce2f942f@www.fastmail.com>
Date:   Wed, 17 Aug 2022 22:30:39 -0400
From:   "Chris Murphy" <lists@...orremedies.com>
To:     "Ming Lei" <ming.lei@...hat.com>
Cc:     "Nikolay Borisov" <nborisov@...e.com>,
        "Jens Axboe" <axboe@...nel.dk>, "Jan Kara" <jack@...e.cz>,
        "Paolo Valente" <paolo.valente@...aro.org>,
        "Btrfs BTRFS" <linux-btrfs@...r.kernel.org>,
        Linux-RAID <linux-raid@...r.kernel.org>,
        linux-block <linux-block@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        "Josef Bacik" <josef@...icpanda.com>
Subject: Re: stalling IO regression since linux 5.12, through 5.18



On Wed, Aug 17, 2022, at 9:03 PM, Ming Lei wrote:
> On Wed, Aug 17, 2022 at 12:34:42PM -0400, Chris Murphy wrote:
>> 
>> 
>> On Wed, Aug 17, 2022, at 11:34 AM, Ming Lei wrote:
>> 
>> > From the 2nd log of blockdebugfs-all.txt, still not see any in-flight IO on
>> > request based block devices, but sda is _not_ included in this log, and
>> > only sdi, sdg and sdf are collected, is that expected?
>> 
>> While the problem was happening I did
>> 
>> cd /sys/kernel/debug/block
>> find . -type f -exec grep -aH . {} \;
>> 
>> The file has the nodes out of order, but I don't know enough about the interface to see if there are things that are missing, or what it means.
>> 
>> 
>> > BTW, all request based block devices should be observed in blk-mq debugfs.
>> 
>> /sys/kernel/debug/block contains
>> 
>> drwxr-xr-x.  2 root root 0 Aug 17 15:20 md0
>> drwxr-xr-x. 51 root root 0 Aug 17 15:20 sda
>> drwxr-xr-x. 51 root root 0 Aug 17 15:20 sdb
>> drwxr-xr-x. 51 root root 0 Aug 17 15:20 sdc
>> drwxr-xr-x. 51 root root 0 Aug 17 15:20 sdd
>> drwxr-xr-x. 51 root root 0 Aug 17 15:20 sde
>> drwxr-xr-x. 51 root root 0 Aug 17 15:20 sdf
>> drwxr-xr-x. 51 root root 0 Aug 17 15:20 sdg
>> drwxr-xr-x. 51 root root 0 Aug 17 15:20 sdh
>> drwxr-xr-x.  4 root root 0 Aug 17 15:20 sdi
>> drwxr-xr-x.  2 root root 0 Aug 17 15:20 zram0
>
> OK, so lots of devices are missed in your log, and the following command
> is supposed to work for collecting log from all block device's debugfs:
>
> (cd /sys/kernel/debug/block/ && find . -type f -exec grep -aH . {} \;)

OK here it is:

https://drive.google.com/file/d/18nEOx2Ghsqx8uII6nzWpCFuYENHuQd-f/view?usp=sharing


-- 
Chris Murphy