linux-kernel - Re: [PATCH v3 2/2] Make hard lockup detection use timestamps

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]

Date:	Wed, 3 Aug 2011 15:44:38 -0400
From:	Don Zickus <dzickus@...hat.com>
To:	ZAK Magnus <zakmagnus@...gle.com>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Mandeep Singh Baines <msb@...omium.org>
Subject: Re: [PATCH v3 2/2] Make hard lockup detection use timestamps

On Wed, Aug 03, 2011 at 11:27:16AM -0700, ZAK Magnus wrote:
> An update:
> 
> I realized that the timing function I was using was no good. On x86 it
> will try to use the TSC but if it can't (which, as I understand, isn't
> a very rare case), it will fall back on a jiffies-based solution. If
> interrupts are disabled, time would appear to "stand still" and
> lockups wouldn't be detected. So, looks like I have to nix this
> particular patch and not change the hard lockup detection that much.

Hmm, I was initially worried about that, but after seeing the function
you were using assuming Peter vetted it properly to use cleanly from an
NMI context.  I guess I didn't fully understand the limitations of it.

> 
> Meanwhile, I'm working on printing stack traces to a buffer/out to
> file. I got some help and it looks like it's not that hard to do. I'll
> send it when it's ready.

Interesting.  I look forward to seeing it.

Cheers,
Don

--
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/