From: David Daney <ddaney.cavm@gmail.com>
To: "Hill, Steven" <sjhill@mips.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"ralf@linux-mips.org" <ralf@linux-mips.org>
Subject: Re: [PATCH v4] MIPS: Make CP0 config registers readable via sysfs.
Date: Fri, 04 Jan 2013 11:05:05 -0800 [thread overview]
Message-ID: <50E727E1.8040604@gmail.com> (raw)
In-Reply-To: <31E06A9FC96CEC488B43B19E2957C1B801146AF10B@exchdb03.mips.com>
On 01/04/2013 10:38 AM, Hill, Steven wrote:
>> You're exporting privileged context outside the kernel -- have all the
>> security implications been considered?
>>
> Maciej,
>
> I have gone through the config registers bit-by-bit and I do not see
> where there are any security implications.
[...]
> Unless you can provide a counterexample,
> this patch does not compromise the system in anyway.
>
The patch stands alone. Any security problems it might have are
completely unrelated to any hypothetical Counter Examples.
David Daney
next prev parent reply other threads:[~2013-01-04 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 22:15 [PATCH v4] MIPS: Make CP0 config registers readable via sysfs Steven J. Hill
2012-12-13 23:27 ` Maciej W. Rozycki
2012-12-13 23:38 ` David Daney
2013-01-04 18:38 ` Hill, Steven
2013-01-04 19:05 ` David Daney [this message]
2013-01-04 19:30 ` Hill, Steven
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=50E727E1.8040604@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=sjhill@mips.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.