linux-kernel - Re: [PATCH v2] Fix Hard Lockup in ktime_get

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] [day] [month] [year] [list]

Message-ID: <CAO6TR8Wy2iFDkdbnxyS4EhfV_sEz5DL7fbZGJUimqfDz90J6yQ@mail.gmail.com>
Date:	Tue, 19 Jan 2016 22:43:33 -0700
From:	Jeff Merkey <linux.mdb@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	John Stultz <john.stultz@...aro.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v2] Fix Hard Lockup in ktime_get_ts64 with debuggers

I just finished a 4 hour regression test of this patch and please drop
it.   It does fix the symptom but not the illness.  It worked on i386
and x86_64 for my first test but failed the second test.  I did a 4
hour debugging session and the problem just shows up another way.

This patch gets rid of the hard lockup but it results in the gnome gui
and systemd eventually locking up after entering and exiting the
debugger and holding the system suspended for several hours.  This
tells me that whatever is causing that value to get so large with the
clock skew is affecting other areas of the timekeeping logic.

I will keep working on it since I need this to work.  kgdb also
experiences the same problem.

So drop this patch and I'll keep looking for the sickness rather than
treat the symtoms.  If you guys have any ideas let me know.

Jeff