From: "Tony Battersby" <tonyb@cybernetics.com>
To: dougg@torque.net
Cc: linux-scsi@vger.kernel.org
Subject: RE: BUG() in 2.4: sg direct IO + exit()
Date: Wed, 24 Mar 2004 11:22:55 -0500 [thread overview]
Message-ID: <04Mar24.112256est.332201@cyborg.cybernetics.com> (raw)
In-Reply-To: <406185C6.6050705@torque.net>
> It is not causing an oops when I try with scsi_debug and lk 2.6.5-rc2.
> Neither is there a problem with a Suse 9 stock SMP kernel
> (2.4.21-99-smp4G) on an old dual celeron (A-bit mb) box with a
> Sony SDT-7000 tape drive on /dev/sg0.
It could be that on your machine the command finishes before the exit(),
causing unmap_kiobuf->__free_pages->put_page_testzero(page) to leave the
page reference count nonzero instead of calling __free_pages_ok. A
command that takes longer to finish (e.g. READ(6)) might trigger the
BUG() on your machine.
Anthony J. Battersby
Cybernetics
prev parent reply other threads:[~2004-03-24 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 15:04 BUG() in 2.4: sg direct IO + exit() Tony Battersby
2004-03-24 12:57 ` Douglas Gilbert
2004-03-24 13:02 ` Jens Axboe
2004-03-27 10:38 ` Douglas Gilbert
2004-03-28 12:43 ` Jens Axboe
2004-03-24 16:22 ` Tony Battersby [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=04Mar24.112256est.332201@cyborg.cybernetics.com \
--to=tonyb@cybernetics.com \
--cc=dougg@torque.net \
--cc=linux-scsi@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