public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Faik Uygur <faikuygur@ttnet.net.tr>
To: Mauricio Martinez <mauricio@coe.neu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS in read_cd... what to do?
Date: Wed, 29 Jan 2003 23:25:16 +0200	[thread overview]
Message-ID: <20030129212516.GA2489@ttnet.net.tr> (raw)
In-Reply-To: <Pine.GSO.4.33.0301270937370.18209-100000@Amps.coe.neu.edu>


> I reported twice (Jan 15 the last time) to this list a kernel oops when
> reading a CD in a SONY CDU-31A unit with kernels 2.4.18 - 2.4.20 (and
> probably all the 2.4 series), which works fine on 2.2.x (and even
> 1.2.x!!), maybe the maintainer of this part os the code is offline... Are
> there any alternatives to fix this problem? Thank you.

There is something wrong here. This should help.

--- linux-2.4.20/drivers/cdrom/cdu31a.c.orig    Fri Nov 29 01:53:12 2002
+++ linux-2.4.20/drivers/cdrom/cdu31a.c Wed Jan 29 23:12:39 2003
@@ -1384,9 +1384,9 @@
                               readahead_buffer + (2048 -
                                                   readahead_dataleft),
                               readahead_dataleft);
-                       readahead_dataleft = 0;
                        bytesleft -= readahead_dataleft;
                        offset += readahead_dataleft;
+                       readahead_dataleft = 0;
                } else {
                        /* The readahead will fill the whole buffer, get the data
                           and return. */



      parent reply	other threads:[~2003-01-29 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27 14:43 OOPS in read_cd... what to do? Mauricio Martinez
2003-01-27 16:23 ` Brian Gerst
2003-01-28 12:51   ` Andreas Henriksson
2003-01-28 18:48     ` Alan Cox
2003-01-28 19:52       ` Andreas Henriksson
2003-01-29  4:07       ` Cabletron E2100 (e2100.c) Oops Andreas Henriksson
2003-01-29 21:25 ` Faik Uygur [this message]

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=20030129212516.GA2489@ttnet.net.tr \
    --to=faikuygur@ttnet.net.tr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mauricio@coe.neu.edu \
    /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