mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: jmerkey@comcast.net
Cc: alan@lxorguk.ukuu.org.uk, wli@holomorphy.com, roland@topspin.com,
	linux-kernel@vger.kernel.org, jmerkey@drdos.com
Subject: Re: 1GB/2GB/3GB User Space Splitting Patch 2.6.8.1 (PSEUDO SPAM)
Date: Mon, 30 Aug 2004 11:10:19 -0700	[thread overview]
Message-ID: <20040830111019.5ddc99ab.rddunlap@osdl.org> (raw)
In-Reply-To: <083020040556.26446.4132C1810009E19F0000674E2200751150970A059D0A0306@comcast.net>

On Mon, 30 Aug 2004 05:56:17 +0000 jmerkey@comcast.net wrote:

| 
| 
| 
| 
| > What kernel version?  I can't even find usb_read_device() in 2.6.9-rc1.
| > 
| > BTW, as someone else requested, please teach your mail client to wrap
| > lines around column 70-72.  Thanks.
| > 
| > ~Randy
| 
| linux-2.6.8.1.tar.gz


usb_device_read here (usb_read_device above :)


| static ssize_t usb_device_read(struct file *file, 
|                                                          char __user *buf, 
|                                                          size_t nbytes, 
|                                                          loff_t *ppos)
| {
|         struct list_head *buslist;
|         struct usb_bus *bus;
|         ssize_t ret, total_written = 0;
|         loff_t skip_bytes = *ppos;
|                                                                                 
|         if (*ppos < 0)
|                 return -EINVAL;
|         if (nbytes <= 0)
|                 return 0;
|         if (!access_ok(VERIFY_WRITE, buf, nbytes))
|                 return -EFAULT;
|                                                                                 
|         /* enumerate busses */
|         down (&usb_bus_list_lock);
|         for (buslist = usb_bus_list.next; 
|                buslist != &usb_bus_list; 
|                buslist = buslist->next) {
|                 /* print devices for this bus */
|                 bus = list_entry(buslist, struct usb_bus, 
|                                              bus_list);
|                 /* print devices for this bus */
|                 bus = list_entry(buslist, struct usb_bus, 
|                                              bus_list);
|                                                                                 
|                 /* recurse through all children of the root hub */
|                 if (!bus->root_hub)
|                         continue;
| 
| // IT BARFS RIGHT HERE -->
|                 down(&bus->root_hub->serialize);

It doesn't barf on me.  I added one other patch on top of yours:
one from Roland Dreier, for arch/i386/kernel/doublefault.c [below].

| P.S.  I am using my comcast account which
| is not as good as MUTT -- line wrap settings
| since it is web based.  
| drdos.com gets rejected
| so I am typing less characters/line. :-)
| -
Thanks.

--
~Randy



Looks like arch/i386/kernel/doublefault.c is one place in the code
that hardcodes the assumption that PAGE_OFFSET == 0xC0000000.  Here's
a patch that fixes that.

(Of course this doesn't really fix anything except debugging output)

 - Roland

Signed-off-by: Roland Dreier <roland@topspin.com>

Index: linux-2.6.8-rc1/arch/i386/kernel/doublefault.c
===================================================================
--- linux-2.6.8-rc1.orig/arch/i386/kernel/doublefault.c
+++ linux-2.6.8-rc1/arch/i386/kernel/doublefault.c
@@ -13,7 +13,7 @@
 static unsigned long doublefault_stack[DOUBLEFAULT_STACKSIZE];
 #define STACK_START (unsigned long)(doublefault_stack+DOUBLEFAULT_STACKSIZE)
 
-#define ptr_ok(x) ((x) > 0xc0000000 && (x) < 0xc1000000)
+#define ptr_ok(x) ((x) > PAGE_OFFSET && (x) < PAGE_OFFSET + 0x1000000)
 
 static void doublefault_fn(void)
 {
-

  reply	other threads:[~2004-08-30 18:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30  5:56 jmerkey
2004-08-30 18:10 ` Randy.Dunlap [this message]
2004-08-30 18:28   ` Roland Dreier
2004-09-22 18:52   ` Timothy Miller
2004-09-22 18:51     ` Roland Dreier
2004-09-22 20:22       ` Timothy Miller
2004-09-27 14:55         ` Roland Dreier
  -- strict thread matches above, loose matches on Subject: below --
2004-08-31 22:50 jmerkey
2004-08-30  4:01 jmerkey
2004-08-30  4:35 ` Randy.Dunlap
2004-08-26 23:47 linux
2004-08-26 21:08 jmerkey
2004-08-26 21:43 ` William Lee Irwin III
2004-08-26 20:24 jmerkey
2004-08-26 20:38 ` William Lee Irwin III
2004-08-26 21:41 ` Dave Jones
2004-08-26  4:21 jmerkey
2004-08-26  4:33 ` William Lee Irwin III
2004-08-26  4:46   ` Roland Dreier
2004-08-26  4:49     ` William Lee Irwin III
2004-08-26  8:40       ` Ryan Cumming
2004-08-29 12:48       ` Alan Cox
2004-08-29 16:42         ` William Lee Irwin III
2004-08-29 15:45           ` Alan Cox
2004-08-29 17:00             ` William Lee Irwin III
2004-08-26  4:38 ` Martin J. Bligh
2004-08-26  4:42 ` Roland Dreier

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=20040830111019.5ddc99ab.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jmerkey@comcast.net \
    --cc=jmerkey@drdos.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@topspin.com \
    --cc=wli@holomorphy.com \
    /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

all inboxes | Powered by JetHome®