public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: hugh@veritas.com
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
	egmont@uhulinux.hu, linux-kernel@vger.kernel.org,
	stable@kernel.org
Subject: Re: [PATCH] fix compat console unimap regression
Date: Fri, 25 May 2007 21:54:20 -0700 (PDT)	[thread overview]
Message-ID: <20070525.215420.74747016.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0705260032250.25650@blonde.wat.veritas.com>

From: Hugh Dickins <hugh@veritas.com>
Date: Sat, 26 May 2007 00:39:17 +0100 (BST)

> Why is it that since the 2f1a2ccb9c0de632ab07193becf5f7121794f6ae console
> UTF-8 fixes went into 2.6.22-rc1, the PowerMac G5 shows only inverse video
> question marks for the text on tty2-6? whereas tty1 is fine, and so is x86.
> 
> No fault of that patch: by removing the old fallback behaviour, it reveals
> that 32-bit setfont running on 64-bit kernels has only really worked on
> the current console, the rest getting faked by that inadequate fallback.
> 
> Bring the compat do_unimap_ioctl into line with the main one: PIO_UNIMAP
> and GIO_UNIMAP apply to the specified tty, not redirected to fg_console.
> Use the same checks, and most particularly, remember to check access_ok:
> con_set_unimap and con_get_unimap are using __get_user and __put_user.
> 
> And the compat vt_check should ask for the same capability as the main
> one, CAP_SYS_TTY_CONFIG rather than CAP_SYS_ADMIN.  Added in vt_ioctl's
> vc_cons_allocated check for safety, though failure may well be impossible.
> 
> Signed-off-by: Hugh Dickins <hugh@veritas.com>

Thanks for figuring this out, I've been wondering what in the
world was causing this on sparc64.

      reply	other threads:[~2007-05-26  5:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25 23:39 [PATCH] fix compat console unimap regression Hugh Dickins
2007-05-26  4:54 ` David Miller [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=20070525.215420.74747016.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=egmont@uhulinux.hu \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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