Bug#336220: xdm: bogus /dev/mem access lead to trouble on arm platforms

2007-09-17 Thread Lennert Buytenhek
On Mon, Sep 17, 2007 at 08:55:49AM +0200, Brice Goglin wrote:

   On arm platforms where physical RAM doesn't start at physical address
   zero, opening /dev/mem and reading from it causes a kernel oops.  This
   is arguably a kernel bug, but it's still not a very good idea to just
   start randomly poking around in /dev/mem in search of entropy, which is
   what xdm does if it can't get entropy elsewhere.
   
   (When the kernel is fixed, blindly reading from /dev/mem will simply
   just fail with EFAULT instead of oopsing.  If that will cause xdm to
   fail, it should really just fail right away if /dev/random doesn't work.)
  
  xdm seems to try /dev/urandom first nowadays (before /dev/random and then
  /dev/mem). I don't whether arm systems have a /dev/urandom, but it seems
  more likely than having a /dev/random.
  
  I don't know which version of xdm you were running when you reported this
  problem (Xorg 6.8.2 was the latest release on 2005/10/28). But it was at
  the same time that the urandom support has been added upstream (in Xorg
  6.9.99.902 on 2005/10/29).
  
  So please test with a more recent xdm and report back whether it helps.
 
 Ping?

I'm not sure what to reply to this.

The problem is not that xdm doesn't check /dev/urandom first, the
problem is that it reads from /dev/mem _at all_.

It is possible that checking /dev/urandom first masks the problem
in most configurations, but it doesn't solve it (if you don't have
/dev/random and /dev/urandom in your filesystem for whatever reason,
you still oops.)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#367188: xorg: Please add big-endian arm (armeb) support

2006-05-14 Thread Lennert Buytenhek
Package: xorg
Version: 7.0.17
Severity: wishlist
Tags: patch

The attached patch adds support for the big-endian arm (armeb)
architecture to xorg 7.0.17 by copying vars.arm to vars.armeb.


-- System Information:
Debian Release: 3.1
Architecture: armeb (armv5teb)
Kernel: Linux 2.6.17-rc2
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
--- xorg-7.0.17/debian/scripts/vars.armeb.orig  2006-05-07 11:31:26.0 
+0200
+++ xorg-7.0.17/debian/scripts/vars.armeb   2006-05-07 11:30:59.0 
+0200
@@ -0,0 +1,10 @@
+
+# This file is NOT a shell script.
+#
+# This file gets included by both debian/rules (make) AND the scripts in
+# debian/scripts (Bourne shell).
+XSERVER_XORG_VIDEO_DEPENDS=xserver-xorg-video-apm, xserver-xorg-video-ark, 
xserver-xorg-video-ati, xserver-xorg-video-chips, xserver-xorg-video-cirrus, 
xserver-xorg-video-cyrix, xserver-xorg-video-dummy, xserver-xorg-video-fbdev, 
xserver-xorg-video-glint, xserver-xorg-video-i128, xserver-xorg-video-i740, 
xserver-xorg-video-i810, xserver-xorg-video-imstt, xserver-xorg-video-mga, 
xserver-xorg-video-neomagic, xserver-xorg-video-newport, 
xserver-xorg-video-nsc, xserver-xorg-video-nv, xserver-xorg-video-rendition, 
xserver-xorg-video-s3, xserver-xorg-video-s3virge, xserver-xorg-video-savage, 
xserver-xorg-video-siliconmotion, xserver-xorg-video-sis, 
xserver-xorg-video-sisusb, xserver-xorg-video-tdfx, xserver-xorg-video-tga, 
xserver-xorg-video-trident, xserver-xorg-video-tseng, xserver-xorg-video-vesa, 
xserver-xorg-video-vga, xserver-xorg-video-via, xserver-xorg-video-voodoo, 
xserver-xorg-video-vmware, xserver-xorg-video-v4l
+
+# xserver-xorg-video-glide,
+
+XSERVER_XORG_INPUT_DEPENDS=xserver-xorg-input-evdev, xserver-xorg-input-kbd, 
xserver-xorg-input-mouse, xserver-xorg-input-synaptics, 
xserver-xorg-input-wacom


Bug#336220: xdm: bogus /dev/mem access lead to trouble on arm platforms

2005-10-28 Thread Lennert Buytenhek
Package: xdm
Severity: important

On arm platforms where physical RAM doesn't start at physical address
zero, opening /dev/mem and reading from it causes a kernel oops.  This
is arguably a kernel bug, but it's still not a very good idea to just
start randomly poking around in /dev/mem in search of entropy, which is
what xdm does if it can't get entropy elsewhere.

(When the kernel is fixed, blindly reading from /dev/mem will simply
just fail with EFAULT instead of oopsing.  If that will cause xdm to
fail, it should really just fail right away if /dev/random doesn't work.)


-- System Information:
Debian Release: testing/unstable
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: armeb (armv4b)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]