Re: for-next branch and blktests/srp

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2018-12-06 at 08:47 -0800, Bart Van Assche wrote:
+AD4 If I merge Jens' for-next branch with Linus' master branch, boot the
+AD4 resulting kernel in a VM and run blktests/tests/srp/002 then that test
+AD4 never finishes. The same test passes against Linus' master branch. I
+AD4 think this is a regression. The following appears in the system log if
+AD4 I run that test:
+AD4 
+AD4 Call Trace:
+AD4 INFO: task kworker/0:1:12 blocked for more than 120 seconds.
+AD4 Call Trace:
+AD4 INFO: task ext4lazyinit:2079 blocked for more than 120 seconds.
+AD4 Call Trace:
+AD4 INFO: task fio:2151 blocked for more than 120 seconds.
+AD4 Call Trace:
+AD4 INFO: task fio:2154 blocked for more than 120 seconds.

Hi Jens,

My test results so far are as follows:
+ACo With kernel v4.20-rc5 test srp/002 passes.
+ACo With your for-next branch test srp/002 reports the symptoms reported in my e-mail.
+ACo With Linus' master branch from this morning test srp/002 fails in the same way as
  your for-next branch.
+ACo Also with Linus' master branch, test srp/002 passes if I revert the following commit:
  ffe81d45322c (+ACI-blk-mq: fix corruption with direct issue+ACI). So it seems like that
  commit fixed one regression but introduced another regression.

Bart.



[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux