linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Harkes <jaharkes@cs.cmu.edu>
To: "Eloy A. Paris" <eloy.paris@usa.net>
Cc: webcam@smcc.demon.nl, linux-kernel@vger.kernel.org,
	torvalds@transmeta.com
Subject: [PATCH -R] Re: 2.4.10 is toxic to my system when I use my USB webcam (was: More info. on crash)
Date: Wed, 26 Sep 2001 19:11:25 -0400	[thread overview]
Message-ID: <20010926191123.A30545@cs.cmu.edu> (raw)
In-Reply-To: <20010926104354.A2192@antenas>
In-Reply-To: <20010926104354.A2192@antenas>

On Wed, Sep 26, 2001 at 10:43:54AM -0400, Eloy A. Paris wrote:
> I have been doing some tests to determine where the problems is. The
> good news is that the problem is not in your driver. The bad news is
> that 2.4.10 is toxic to my system (at least when I try to use my
> Phillips webcam) and that the problem lies somewhere else.
> 
> Here's a quick summary of the tests I did:
> 
> (0) Stock 2.4.9: rock solid
> (1) Stock 2.4.10: system crash after device is open()'ed
> (2) 2.4.10 + pwc 8.1 (backed out pwc 8.2): system crash as in (1)
> (3) 2.4.10 + changes to usbcore.o and usb-uhci.o backed out: system
>     crash.
> (4) 2.4.9 + pwc 8.2: rock solid

It hit me as well and I found the culprit, the crash happens in
usb-uhci.c:process_iso, where the following code used to be 'safe'

	for (i = 0; p != &urb_priv->desc_list; i++) {
...
	    list_del (p);
	    p = p->next;
	    delete_desc (s, desc);
	}

However, some infidel sneaked the following change into 2.4.10, late in
the testcycle, which is deadly. This patch needs to be reverted. If the
behaviour is wanted all uses of list_del in the kernel need to be looked
at very closely.

Jan

====
diff -u --recursive --new-file v2.4.9/linux/include/linux/list.h linux/include/l
inux/list.h
--- v2.4.9/linux/include/linux/list.h   Fri Feb 16 16:06:17 2001
+++ linux/include/linux/list.h  Sun Sep 23 10:31:02 2001
@@ -90,6 +92,7 @@
 static __inline__ void list_del(struct list_head *entry)
 {
        __list_del(entry->prev, entry->next);
+       entry->next = entry->prev = 0;
 }
 
 /**


  reply	other threads:[~2001-09-26 23:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26 14:43 2.4.10 is toxic to my system when I use my USB webcam (was: More info. on crash) Eloy A. Paris
2001-09-26 23:11 ` Jan Harkes [this message]
2001-09-27  6:33   ` [PATCH -R] Re: 2.4.10 is toxic to my system when I use my US Nemosoft Unv.
2001-09-27  9:00     ` Ingo Molnar
2001-09-27 12:20       ` [linux-usb-devel] " Georg Acher
2001-09-27 12:13     ` Georg Acher

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=20010926191123.A30545@cs.cmu.edu \
    --to=jaharkes@cs.cmu.edu \
    --cc=eloy.paris@usa.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=webcam@smcc.demon.nl \
    /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;
as well as URLs for NNTP newsgroup(s).