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: <m18xic4den.fsf@ebiederm.dsl.xmission.com>
Date:	Wed, 15 Nov 2006 14:18:24 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Andrew Morton <akpm@...l.org>
Cc:	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)

Andrew Morton <akpm@...l.org> writes:

> Is it correct to say that oprofile-on-2.6.18 works, and that
> oprofile-on-2.6.19-rc5 does not?
>
> Or is there some sort of workaround for this, or does 2.6.19-rc5 only fail
> in some particular scenarios?
>
> If it's really true that oprofile is simply busted then that's a serious
> problem and we should find some way of unbusting it.  If that means just
> adding a dummy "0" entry which always returns zero or something like that,
> then fine.
>
> But we can't just go and bust it.

The simple question.  If we turn off the NMI watchdog on 2.6.19-rc5 
does oprofile work?  I believe that is what Andi said.

The description I read was a resource conflict. The resources oprofile
just expects it can used are already in use so we tell it no and
the user space oprofile doesn't cope.

Now I don't know the interface allows us to rename the interfaces
from 1 2 3 to 0 1 2.  If we can then that looks like something we can
fix.  Otherwise from the description I tend to agree with Andi.

The user space application assumed it own hardware that it did not.

Hmm.  I bet if nothing else we could move the NMI watchdog from 0 to 3
and make things work that way...


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