From: Georg Acher <acher@in.tum.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Nemosoft Unv." <nemosoft@smcc.demon.nl>,
Jan Harkes <jaharkes@cs.cmu.edu>,
Linus Torvalds <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: [linux-usb-devel] RE: [PATCH -R] Re: 2.4.10 is toxic to my system when I use my US
Date: Thu, 27 Sep 2001 14:20:06 +0200 [thread overview]
Message-ID: <20010927142006.B1491@atbode61.informatik.tu-muenchen.de> (raw)
In-Reply-To: <XFMail.010927083327.nemosoft@smcc.demon.nl> <Pine.LNX.4.33.0109271057030.3716-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0109271057030.3716-100000@localhost.localdomain>; from mingo@elte.hu on Thu, Sep 27, 2001 at 11:00:24AM +0200
On Thu, Sep 27, 2001 at 11:00:24AM +0200, Ingo Molnar wrote:
> yep. this is one reason why the 2.4.10 kernel clears the ->next and ->prev
> pointers in list_del() - the above code will break immediately.
Good intention, very bad timing. All of these bug-provoking fixes for a
production kernel should only occur in the first kernels of a -pre-series,
not in the last one.
--
Georg Acher, acher@in.tum.de
http://www.in.tum.de/~acher/
"Oh no, not again !" The bowl of petunias
next prev parent reply other threads:[~2001-09-27 12:21 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 ` [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 ` Georg Acher [this message]
2001-09-27 12:13 ` [linux-usb-devel] " 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=20010927142006.B1491@atbode61.informatik.tu-muenchen.de \
--to=acher@in.tum.de \
--cc=eloy.paris@usa.net \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mingo@elte.hu \
--cc=nemosoft@smcc.demon.nl \
--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
all inboxes | Powered by JetHome®