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] Sync SCSI bugfix tree
Date: 23 Oct 2003 12:14:28 -0500 [thread overview]
Message-ID: <1066929269.1831.35.camel@mulgrave> (raw)
This is the current set of SCSI bugfixes only for 2.6
you can pull it from
bk://linux-scsi.bkbits.net/scsi-bugfixes-2.6
I've added the justifications into the short changelogs:
<p.lavarre:ieee.org>:
o SG_SET_RESERVED_SIZE negative oops
- can oops the kernel if incorrect parameters passed
Douglas Gilbert:
o SCSI constants.c
- fixes a mismerge that lost us the report luns sense
Mark Haverkamp:
o Work around aacraid FW problem
- can corrupt data for >4GB machines
Mike Anderson:
o Add release function to sd for scsi_disk structure
- Ongoing fixes to refcounting issues which cause oopses on surprise
ejection of USB (and other) SCSI devices.
Mike Christie:
o fix oops caused when writing to the rescan attribute
Patrick Mansfield:
o SCSI: limit mode sense usage
- required to make some USB devices work by preventing them from
receiving the cache mode sense command
James
reply other threads:[~2003-10-23 17:14 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=1066929269.1831.35.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