From: Jeff Dike <jdike@addtoit.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] [PATCH] fix writing into /dev/kmem
Date: Sat, 28 Feb 2004 21:36:36 -0500 [thread overview]
Message-ID: <20040229023636.GB8272@ccure.user-mode-linux.org> (raw)
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.
Jeff
--- drivers/char/mem.c~ 2004-01-05 11:23:32.000000000 -0500
+++ drivers/char/mem.c 2004-02-27 08:52:14.000000000 -0500
@@ -287,6 +287,7 @@
ssize_t virtr = 0;
char * kbuf; /* k-addr because vwrite() takes vmlist_lock rwlock */
+ p = (unsigned long) __va(p);
if (p < (unsigned long) high_memory) {
wrote = count;
if (count > (unsigned long) high_memory - p)
@@ -321,7 +322,7 @@
free_page((unsigned long)kbuf);
}
- *ppos = p;
+ *ppos = __pa((void *) p);
return virtr + wrote;
}
-------------------------------------------------------
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
next reply other threads:[~2004-02-29 2:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 2:36 Jeff Dike [this message]
2004-02-29 12:25 ` [uml-devel] [PATCH] fix writing into /dev/kmem BlaisorBlade
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=20040229023636.GB8272@ccure.user-mode-linux.org \
--to=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