All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marcin Kościelnicki" <koriakin-mP9o5jsk0RY@public.gmane.org>
To: Andy Ritger <aritger-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: offer to help, DCB
Date: Wed, 25 Sep 2013 09:46:12 +0200	[thread overview]
Message-ID: <524294C4.20701@0x04.net> (raw)
In-Reply-To: <20130925003422.GE28691-4K9zQNqW3/fFT5IIyIEb6QC/G2K4zDHf@public.gmane.org>

> Does Nouveau reimplement Falcon microcode due to particular deficiencies
> in NVIDIA's microcode, or because you couldn't get permission in the past
> to redistribute the firmware extracted from NVIDIA's proprietary driver?
> If the latter, I think we can get to the point of solving that with more
> amenable licensing.  If the former, I'd like to report the deficiencies
> from your point of view back to NVIDIA's firmware team, so that we can
> improve the firmware for Nouveau use.

While I'm personally one of the guys who wouldn't like to see a binary 
blob in nouveau, no matter the terms, I've read the firmware blobs 
decompilation and I'm quite concerned about possible security implications.

The PGRAPH context switch microcode allows user to read/write arbitrary 
MMIO registers by submitting the firmware methods. The GF100+ video 
decoding etc. falcon microcodes allow you to just ask for physical 
instead of virtual addressing, and that includes physical system memory. 
Why did nVidia include such obviously security-breaking functionality in 
the firmware images? As I understand it, a user having access to just 
the FIFO submission interface should only have access to his own VM 
area, and not have enough power to take over the machine. Is there any 
security model for nVidia hardware/firmware/kernel driver system?

Marcin Kościelnicki
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2013-09-25  7:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24  4:44 offer to help, DCB Andy Ritger
     [not found] ` <20130924044457.GA25785-4K9zQNqW3/fFT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2013-09-24  7:12   ` Maarten Lankhorst
     [not found]     ` <52413B42.9050101-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2013-09-24 18:19       ` Andy Ritger
     [not found]         ` <20130924181938.GD27823-4K9zQNqW3/fFT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2013-09-24 19:43           ` Dave Airlie
     [not found]             ` <CAPM=9tykSx_p-SgK9+JpUADD8E_M6ciS5kXd68UaE-A9-sgiYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-25  0:34               ` Andy Ritger
     [not found]                 ` <20130925003422.GE28691-4K9zQNqW3/fFT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2013-09-25  0:59                   ` Dave Airlie
2013-09-25  7:46                   ` Marcin Kościelnicki [this message]
     [not found]                     ` <524294C4.20701-mP9o5jsk0RY@public.gmane.org>
2013-09-27 17:52                       ` Andy Ritger
2013-09-24 17:27   ` Ben Skeggs

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=524294C4.20701@0x04.net \
    --to=koriakin-mp9o5jsk0ry@public.gmane.org \
    --cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=aritger-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /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.