linux-kernel - Re: WARNING: CPU: 0 PID: 1 at init/main.c:711 do_one

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: <52935F73.4090209@panasas.com>
Date:	Mon, 25 Nov 2013 16:32:19 +0200
From:	Boaz Harrosh <bharrosh@...asas.com>
To:	Richard Weinberger <richard.weinberger@...il.com>
CC:	Yuanhan Liu <yuanhan.liu@...ux.intel.com>,
	LKP <fnstml-lkp@...fujitsu.com>,
	Fengguang Wu <fengguang.wu@...el.com>,
	<linux-crypto@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: WARNING: CPU: 0 PID: 1 at init/main.c:711 do_one_initcall()

On 11/25/2013 04:15 PM, Richard Weinberger wrote:
> On Fri, Nov 22, 2013 at 7:02 AM, Yuanhan Liu
> <yuanhan.liu@...ux.intel.com> wrote:
>> Greetings,
>>
>> I got the below dmesg and the first bad commit is
>>
>> commit 20545536cd8ea949c61527b6395ec8c0d2c237b1
>> Author: Boaz Harrosh <bharrosh@...asas.com>
>> Date:   Thu Jul 19 15:22:37 2012 +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?
> 
> This patch never hit my mailbox...
> 
>>     Signed-off-by: Boaz Harrosh <bharrosh@...asas.com>
>>

Sir Richard

I never followed on this patch. Sorry. I do think it is in
the right direction, but it has a dev-by-zero problem and
a 32 bitness problem. (So I never sent it, beyond the initial
query)

[It stopped to be very important for me since I stopped using
 UM very much. Ever since FC17 I'm unable to produce a running
 image. It just will not boot, an image that a kvm would. So
 very sad me, but no UML for me anymore.]

If you want to investigate. try doing a modprobe xor.ko on
a uml and see. since xor.ko is only built on demand for example
enabling exofs or object-layout-driver will select it. ,or MD-raid5.

Thanks
Boaz

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/