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

Message-ID: <CAAuSN92UAjuJXprBAj9z0sekk=iBWGe3PP88z8NmrZ5fExOyjg@mail.gmail.com>
Date:	Mon, 1 Aug 2011 11:33:24 -0700
From:	ZAK Magnus <zakmagnus@...gle.com>
To:	Don Zickus <dzickus@...hat.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

Okay... So this is a problem we need to solve. Does there exist a good
way to output a stack trace to, say, a file in /proc? I think that
would be an appealing solution, if doable.

On Mon, Aug 1, 2011 at 5:52 AM, Don Zickus <dzickus@...hat.com> wrote:
> On Fri, Jul 29, 2011 at 04:12:32PM -0700, ZAK Magnus wrote:
>> Are you saying that any call to printk() will touch the watchdogs? I
>> wasn't aware of that and it doesn't seem to comply with my
>> observations too well, either. Then again, at the moment I don't
>> understand some of the things I'm currently seeing so I could just be
>> wrong.
>
> I believe the serial console write is the source of all the
> touch_nmi_watchdogs that result from a printk.
>
> drivers/tty/serial/8250.c::serial8250_console_write()
>
> 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/