From: Arjan van de Ven <arjan@linux.intel.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Voluspa <lista1@comhem.se>,
arjan@infradead.org, linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [PATCH] lockdep: disable lock debugging when kernel state becomes untrusted
Date: Tue, 05 Sep 2006 09:10:32 +0200 [thread overview]
Message-ID: <44FD22E8.8080309@linux.intel.com> (raw)
In-Reply-To: <20060904235549.f8f6eaab.akpm@osdl.org>
Andrew Morton wrote:
> On Tue, 5 Sep 2006 08:40:42 +0200
> Voluspa <lista1@comhem.se> wrote:
>
>>> That would appear to be a bug. debug_locks_off() is running
>>> console_verbose() waaaay after the locking selftest code has
>>> completed.
>> The possibly final -rc6 is likewise broken. What would it take to incur
>> some respect for us, the millions of users effected by this shit?
>> Should we all become quasi-developers and bombard lkml with patches
>> that taint the kernel whenever some of the Intel binary blobs are
>> loaded?
don't use those btw, they're ancient and unneeded/superceded since ages.
>>
>> Would that cluebat Arjan off of his high horse?
>
> Thanks for the reminder ;)
>
> Arjan, what's that console_verbose() doing in debug_locks_off()? Whatever
> it is, can we fix it? Presumably the previous loglevel needs to be
> readopted somehow, or we just take it out of there.
I'd say take them out of there; I don't know why they're there in the first place.. Ingo ?
next prev parent reply other threads:[~2006-09-05 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 1:09 Voluspa
2006-08-14 1:41 ` Andrew Morton
2006-09-05 6:40 ` Voluspa
2006-09-05 6:55 ` Andrew Morton
2006-09-05 7:10 ` Arjan van de Ven [this message]
2006-09-05 7:15 ` Ingo Molnar
2006-09-05 7:52 ` Voluspa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44FD22E8.8080309@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lista1@comhem.se \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®