public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
	linux-kernel@vger.kernel.org,
	"Greg Kroah-Hartman" <gregkh@suse.de>
Subject: Re: New compat_alloc_user_space() GPLness and fglrx
Date: Mon, 20 Sep 2010 13:19:40 +0200	[thread overview]
Message-ID: <201009201319.40563.arnd@arndb.de> (raw)
In-Reply-To: <20100918124214.GA31802@khazad-dum.debian.net>

On Saturday 18 September 2010, Henrique de Moraes Holschuh wrote:
> Well, that means ATI needs to mess with the insides of their binary
> blob... Anyone knows of a channel to talk to them?  Someone must tell
> them about this, I am just an unwilling user of fglrx (R600 support in
> the open drivers is nowhere near what I need yet).
> 
> Meanwhile, what is the solution?  Keep using (the newly named)
> arch_compat_alloc_user_space()?

Since you don't know how that is used in the driver, that could
very well keep the security hole open as long as the driver is loaded.

You still have the obvious options that you won't like:

1. stay on an older (broken) kernel
2. don't use fglrx until this is fixed
3. copy the new compat_alloc_user_space as an inline function
   into the wrapper module (possibly making it undistributable)

	Arnd

      reply	other threads:[~2010-09-20 11:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-18  1:42 New compat_alloc_user_space() GPLness and fglrx Henrique de Moraes Holschuh
2010-09-18  8:26 ` Arnd Bergmann
2010-09-18 12:42   ` Henrique de Moraes Holschuh
2010-09-20 11:19     ` Arnd Bergmann [this message]

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=201009201319.40563.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=gregkh@suse.de \
    --cc=hmh@hmh.eng.br \
    --cc=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox