On 04/10/2014 09:53 AM, Fengguang Wu wrote: > Hi Boaz, > > I catch the below warning again in > > git://git.open-osd.org/linux-open-osd.git raid6 > OK Thanks. Daa I thought I fixed it but I forgot the obvious problem. I pushed a new tree I think it might be good this time. (finally) Thanks Boaz > commit 60e833d86a01ad9d8204a04b8db324106ab50395 > Author: Boaz Harrosh <bharrosh@xxxxxxxxxxx> > AuthorDate: Thu Jul 19 15:22:37 2012 +0300 > Commit: Boaz Harrosh <bharrosh@xxxxxxxxxxx> > CommitDate: Tue Apr 8 08:42:14 2014 +0300 > > RFC: do_xor_speed Broken on UML do to jiffies > > Remember that hang I reported a while back on UML. Well > I'm at it again, and it still hangs and I found why. > > I have dprinted jiffies and it never advances during the > loop at do_xor_speed. There for it is stuck in an endless > loop. I have also dprinted current_kernel_time() and it > returns the same constant value as well. > > Note that it does usually work on UML, only during > the modprobe of xor.ko while that test is running. It looks > like some lucking is preventing the clock from ticking. > > However ktime_get_ts does work for me so I changed the code > as below, so I can work. See how I put several safety > guards, to never get hangs again. > And I think my time based approach is more accurate then > previous system. > > UML guys please investigate the jiffies issue? what is > xor.ko not doing right? > > Signed-off-by: Boaz Harrosh <bharrosh@xxxxxxxxxxx> > <> > [ 0.383315] WARNING: CPU: 0 PID: 1 at init/main.c:708 do_one_initcall+0x11d/0x136() -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
