public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nemosoft Unv." <nemosoft@smcc.demon.nl>
To: Jan Harkes <jaharkes@cs.cmu.edu>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
	webcam@smcc.demon.nl, "Eloy A.Paris" <eloy.paris@usa.net>,
	linux-usb-devel@lists.sourceforge.net
Subject: RE: [PATCH -R] Re: 2.4.10 is toxic to my system when I use my US
Date: Thu, 27 Sep 2001 08:33:27 +0200 (MEST)	[thread overview]
Message-ID: <XFMail.010927083327.nemosoft@smcc.demon.nl> (raw)
In-Reply-To: <20010926191123.A30545@cs.cmu.edu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1365 bytes --]

Greetings,

On 26-Sep-01 Jan Harkes wrote:
> 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
[snip]

> 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.

Personally, I say the above piece of code is faulty. Refering to a
pointer after you appearently deleted it, is just very bad programming
practice. 

I´d say, fix the usb-uhci file, and do a quick run on all other instances
of list_del. I think most programmers got it right, or 2.4.10 kernels would
be coming down all over the planet.

 - Nemosoft

-----------------------------------------------------------------------------
Try SorceryNet!   One of the best IRC-networks around!   irc.sorcery.net:9000
URL: never        IRC: nemosoft      IscaBBS (bbs.isca.uiowa.edu): Nemosoft
                        >> Never mind the daylight << 

  reply	other threads:[~2001-09-27  6:33 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 ` [PATCH -R] " Jan Harkes
2001-09-27  6:33   ` Nemosoft Unv. [this message]
2001-09-27  9:00     ` [PATCH -R] Re: 2.4.10 is toxic to my system when I use my US 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=XFMail.010927083327.nemosoft@smcc.demon.nl \
    --to=nemosoft@smcc.demon.nl \
    --cc=eloy.paris@usa.net \
    --cc=jaharkes@cs.cmu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --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