linux-kernel - Re: [discuss] Re: 2.6.19-rc5: known regressions (v3)

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: <20061116122358.996fdbb3.akpm@osdl.org>
Date:	Thu, 16 Nov 2006 12:23:58 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Mikael Pettersson <mikpe@...uu.se>
Cc:	ebiederm@...ssion.com (Eric W. Biederman), Andi Kleen <ak@...e.de>,
	Linus Torvalds <torvalds@...l.org>, discuss@...-64.org,
	William Cohen <wcohen@...hat.com>,
	Komuro <komurojun-mbn@...ty.com>,
	Ernst Herzberg <earny@...4u.de>,
	Andre Noll <maan@...temlinux.org>,
	oprofile-list@...ts.sourceforge.net,
	Jens Axboe <jens.axboe@...cle.com>,
	linux-usb-devel@...ts.sourceforge.net, phil.el@...adoo.fr,
	Adrian Bunk <bunk@...sta.de>, Ingo Molnar <mingo@...hat.com>,
	Alan Stern <stern@...land.harvard.edu>,
	linux-pci@...ey.karlin.mff.cuni.cz,
	Stephen Hemminger <shemminger@...l.org>,
	Prakash Punnoor <prakash@...noor.de>,
	Len Brown <len.brown@...el.com>,
	Alex Romosan <romosan@...orax.lbl.gov>, gregkh@...e.de,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrey Borzenkov <arvidjaar@...l.ru>
Subject: Re: [discuss] Re: 2.6.19-rc5: known regressions (v3)

On Thu, 16 Nov 2006 11:55:46 +0100
Mikael Pettersson <mikpe@...uu.se> wrote:

> Andrew Morton writes:
>  > Surely the appropriate behaviour is to allow oprofile to steal the NMI and
>  > to then put the NMI back to doing the watchdog thing after oprofile has
>  > finished with it.
> 
> Which is _exactly_ what pre-2.6.19-rc1 kernels did. I implemented
> the in-kernel API allowing real performance counter drivers like
> oprofile (and perfctr) to claim the HW from the NMI watchdog,
> do their work, and then release it which resumed the watchdog.

OK.  But from Andi's comments it seems that the NMI watchdog was failing to
resume its operation.

> Note that oprofile (and perfctr) didn't do anything behind the
> NMI watchdog's back. They went via the API. Nothing dodgy going on.
-
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/