linux-kernel - Re: I/O hangs after resuming from suspend-to-ram

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <692537117e26fe71b5e07cd8c86b38e4@natalenko.name>
Date:   Wed, 30 Aug 2017 08:15:02 +0200
From:   oleksandr@...alenko.name
To:     Ming Lei <ming.lei@...hat.com>
Cc:     Jens Axboe <axboe@...nel.dk>, Christoph Hellwig <hch@....de>,
        linux-block@...r.kernel.org, linux-raid@...r.kernel.org,
        linux-kernel@...r.kernel.org, Shaohua Li <shli@...nel.org>
Subject: Re: I/O hangs after resuming from suspend-to-ram

Hello.

Addressing your questions below.

> Can't reproduce even with putting dmcypt on raid10 after applying my 
> patch.

Just a side note, that dm-crypt is not necessary here — I am able to 
trigger hang with RAID10 and LVM only.

> BTW, could you share us which blk-mq scheduler you are using on sata?

Okay, now it makes sense. Previously, without your patch I was able to 
reproduce the issue with "mq-deadline", "bfq" and "none". Now, I cannot 
trigger it with "none" set, but "mq-deadline" still hangs for me. Does 
this mean each scheduler should be modified separately?

> Could you apply the following debug patch and provide the dmesg log 
> after running the commands below?

Is it still relevant since I confirm issue to be fixed with "none"?

Thanks.

30.08.2017 07:17, Ming Lei написав:
> …SNIP…
> Can't reproduce even with putting dmcypt on raid10 after applying
> my patch.
> …SNIP…