From: "Frank Ch. Eigler" <fche@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Dave Jones <davej@redhat.com>, Josh Boyer <jwboyer@redhat.com>,
dhowells@redhat.com, linux-kernel@vger.kernel.org,
peterz@infradead.org, mingo@redhat.com,
Len Brown <lenb@kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH] MODSIGN: Add TAINT_NOKEY_MODULE
Date: Sun, 20 Jan 2013 19:19:39 -0500 [thread overview]
Message-ID: <20130121001939.GB25509@redhat.com> (raw)
In-Reply-To: <8738xvxv55.fsf@rustcorp.com.au>
Hi -
> [...]
> - add_taint(TAINT_DIE);
> + add_taint(TAINT_DIE, LOCKDEP_NOW_UNRELIABLE);
> [...]
If "UNRELIABLE" a good way to describe it - not DANGEROUS or
COUNTERPRODUCTIVE or something, then maybe lockdep *can* produce
reasonable results following such a taint. If the results are merely
suspect, could lockdep reports include the taint report, but otherwise
keep working?
- FChE
next parent reply other threads:[~2013-01-21 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130104191205.GD27554@hansolo.jdub.homelinux.org>
[not found] ` <87bod14x44.fsf@rustcorp.com.au>
[not found] ` <20130107145832.GA12363@hansolo.jdub.homelinux.org>
[not found] ` <20130115190911.GA6964@hansolo.jdub.homelinux.org>
[not found] ` <87y5ftyf51.fsf@rustcorp.com.au>
[not found] ` <20130116193724.GF6964@hansolo.jdub.homelinux.org>
[not found] ` <87pq14y6bs.fsf@rustcorp.com.au>
[not found] ` <20130117150202.GB32586@redhat.com>
[not found] ` <8738xvxv55.fsf@rustcorp.com.au>
2013-01-21 0:19 ` Frank Ch. Eigler [this message]
2013-01-21 1:50 ` [PATCH] MODSIGN: Add TAINT_NOKEY_MODULE Rusty Russell
2013-01-21 0:46 ` Rafael J. Wysocki
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=20130121001939.GB25509@redhat.com \
--to=fche@redhat.com \
--cc=davej@redhat.com \
--cc=dhowells@redhat.com \
--cc=jwboyer@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rjw@sisk.pl \
--cc=rusty@rustcorp.com.au \
/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