On Mon, 1 Jul 2019, Andrea Vai wrote: > > At any rate, you are some commits you could try (beginning with > > "git > > checkout <commit>" and then running your scripts): > > > > c76cd634eb5b > > b1669432b355 > > 507413a5f88a > > a52fb43a5faa > > 38fabca18fc4 > > fc2fd5f0f1aa > > > > These are all between 4.20 and 5.0-rc1. > > Hi, > these were all "good". > > Then I ran another bisect (the sixth (!), more carefully, starting > from > > git bisect good c76cd634eb5b > git bisect bad 241e39004581 > > ), and it seems to give some consistent result. > > I found that: > > f664a3cc17b7d0a2bc3b3ab96181e1029b0ec0e6 is the first bad commit > commit f664a3cc17b7d0a2bc3b3ab96181e1029b0ec0e6 > Author: Jens Axboe <[email protected]> > Date: Thu Nov 1 16:36:27 2018 -0600 > > scsi: kill off the legacy IO path > > This removes the legacy (non-mq) IO path for SCSI. > > Cc: [email protected] > Acked-by: Himanshu Madhani <[email protected]> > Reviewed-by: Hannes Reinecke <[email protected]> > Tested-by: Ming Lei <[email protected]> > Reviewed-by: Omar Sandoval <[email protected]> > Acked-by: Martin K. Petersen <[email protected]> > Signed-off-by: Jens Axboe <[email protected]> > > :040000 040000 312373927bae1c6fd1da40ded2c12dfa5e4de71c > 4eccbd2c84bf83cb2eb72a81514d59ebf12866b7 M Documentation > :040000 040000 98de24b4fe20b82095f53f56c9193c5537d70ed0 > 8e2092780100205ae1c3723a598a89794a50677f M drivers > :040000 040000 fbc10c84d3eb6b7933598018319f96767ee3a0f3 > 2523940c2819e8adb32758f5093e477da481ca65 M include > > I reverted it and the test succeeded. > Then I made a double check: "git clone" again; git checkout > 3a7ea2c483a53fc89e336f69c6ee1d7defe00811 (the last good), and the test > succeded. Then git checkout f664a3cc17b7d0a2bc3b3ab96181e1029b0ec0e6 > (the first bad) and the test failed; then reverted it and the test > succeded again. > > Does it make sense?
Yes, that does make sense. What you should do next is report the problem to all the people involved in that commit: Jens Axboe, Himanshu Madhani, and so on. Be sure to CC: the USB mailing list and also [email protected]. Given them a full description of the problem and explain how you determined that this commit was the cause. They should be able to help figure out what's going wrong and fix it. Alan Stern
