From: James Bottomley <James.Bottomley@steeleye.com>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: [BK PATCH] SCSI Bugfixes for 2.6.0-test9
Date: 19 Nov 2003 14:33:31 -0600 [thread overview]
Message-ID: <1069270260.1664.8.camel@mulgrave> (raw)
This contains the current slew of bug fixes harvested from the scsi
mailing lists. I think we could still do with getting our
slave_alloc/destroy bug sorted out, and finally getting our mid layer
refcounting up to the level where were robust against surprise ejection,
but those could also wait for 2.6.1
You can pull the changes from:
bk://linux-scsi.bkbits.net/scsi-bugfixes-2.6
The short changelogs are:
Alan Stern:
o Off-by-one bug in user page calculations for Direct I/O
Andrew Morton:
o fix scsi_report_lun_scan bug
Christoph Hellwig:
o scsi_device refcounting and list lockdown
James Bottomley:
o Add missing .module initialisation to lasi700 and sim710
o lasi700: Fix missed variable name change causing module load error
James
next reply other threads:[~2003-11-19 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 20:33 James Bottomley [this message]
2003-11-19 23:09 ` [BK PATCH] SCSI Bugfixes for 2.6.0-test9 Douglas Gilbert
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=1069270260.1664.8.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.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