mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fruhwirth Clemens <clemens@endorphin.org>
To: linux-kernel@vger.kernel.org
Subject: 2.4.20aa1 ide-scsi crashes
Date: Mon, 6 Jan 2003 16:41:39 +0100	[thread overview]
Message-ID: <20030106154138.GA2588@ghanima.endorphin.org> (raw)

under heavy I/O load for my scsi-emulated cdrom 2.4.20aa1 crashes at

drivers/scsi/scsi_dma:155 with 
panic("scsi_free:Trying to free unused memory")

panic(..) somehow refuses to print the call trace because "IEEE in interrupt
handler - no sync".

The only scsi module I'm using is ide-scsi. As I browsed the aa patch I
recognized that a few &io_request_lock have been exchanged for
"q->queue_lock". But ide-scsi is still locking on io_request_lock. This is
probably the source of the race condition. However I'm not sure because I
think q->queue_lock is being initialized to &io_request_lock, so it should
still be the same lock.

See drivers/scsi/ide-scsi:295 or 
    drivers/scsi/ide-scsi:850 (Why isn't there a lock in that case?)

(done) referrs to sr.c:rw_intr which calls scsi_io_completion which calls
the panic(..)-ing scsi_free)

Any guesses?

Regards, Clemens
Please CC answers, /me not on list.

                 reply	other threads:[~2003-01-06 15:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030106154138.GA2588@ghanima.endorphin.org \
    --to=clemens@endorphin.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome