linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] [PATCH] fix writing into /dev/kmem
Date: Sun, 29 Feb 2004 13:25:40 +0100	[thread overview]
Message-ID: <200402291325.40644.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20040229023636.GB8272@ccure.user-mode-linux.org>

Alle 03:36, domenica 29 febbraio 2004, Jeff Dike ha scritto:
> The patch below fixes a bug in the /dev/kmem driver which causes UML to
> die if you write to it.  Of course, the kernel will die if you write random
> crap to kernel memory, but at least it doesn't die in a UML-specific way.

> This is a cut'n'paste from an xterm, so apply with patch -l.

This patch is like the one for the read from /dev/kmem (i.e. the one fixing 
the panic when one does "cat /dev/kmem": you can reproduce this panic on 
Uml2.6): it makes it behave like /dev/mem (man 4 mem is indeed helpful!). So 
it is basically not *the right way*.

Also, someone got a panic with the read patch applied while klogd was reading 
something. The diagnosys was that the /dev/mem driver checks for overflows, 
while this patched /dev/kmem driver does not. To read the physical address 
0x1with /dev/kmem, you are supposed to read 0xc0000001; so with that patch 
any proper user of /dev/kmem will overflow p.

So, I propose to either return -EFAULT with not accessible addresses (which is 
the proper fix), or to (at least and as a workaround) correct the "fops" 
fields of /dev/kmem to redirect it on /dev/mem (at least this avoids the 
crash better than the current patches).
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-02-29 12:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29  2:36 [uml-devel] [PATCH] fix writing into /dev/kmem Jeff Dike
2004-02-29 12:25 ` BlaisorBlade [this message]
2004-03-02  1:31   ` Jeff Dike
2004-03-02 18:41     ` BlaisorBlade
2004-03-04  2:02       ` Jeff Dike
2004-03-08 11:50         ` BlaisorBlade
2004-02-29 16:20 ` BlaisorBlade
2004-03-02  1:11   ` Jeff Dike
2004-03-02  1:31   ` Jeff Dike

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=200402291325.40644.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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