From: Tejun Heo <tj@kernel.org>
To: linux-ide@vger.kernel.org, jens.axboe@oracle.com,
bharrosh@panasas.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, bzolnier@gmail.com,
petkovbb@googlemail.com, zaitcev@
Subject: [PATCHSET block#for-2.6.31] block: fix fallouts from recent cleanups, take#2
Date: Tue, 19 May 2009 18:33:03 +0900 [thread overview]
Message-ID: <1242725586-13142-1-git-send-email-tj@kernel.org> (raw)
Hello,
This is the second take of fix-fallouts patchset. The first one[L]
was posted without header message. Changes from the last take are
* ub change updated per Pete Zitcev's comment
* resid_len init bug spotted by Boaz Harrosh fixed
This patchset contains the following three patches.
0001-ub-use-__blk_end_request_all.patch
0002-block-set-rq-resid_len-to-blk_rq_bytes-on-issue.patch
0003-bio-always-copy-back-data-for-copied-kernel-request.patch
0001 updates ub to use __blk_end_request_all() and 0002 restores the
original residue count behavior. 0003 makes sure kernel pc buffer is
bounced back even on request failure as user pc ones do. This
inconsistency was discovered during discussion over residue count
semantics.
This patchset contains the following changes.
block/blk-core.c | 5 +++--
drivers/block/ub.c | 30 +++++++++++-------------------
drivers/ide/ide-cd.c | 4 ++--
drivers/ide/ide-tape.c | 2 +-
drivers/message/fusion/mptsas.c | 3 ++-
drivers/scsi/libsas/sas_expander.c | 4 ++++
drivers/scsi/libsas/sas_host_smp.c | 3 ---
drivers/scsi/mpt2sas/mpt2sas_transport.c | 4 ++--
fs/bio.c | 2 +-
9 files changed, 26 insertions(+), 31 deletions(-)
Thanks.
--
tejun
[L] http://thread.gmane.org/gmane.linux.ide/40728
next reply other threads:[~2009-05-19 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 9:33 Tejun Heo [this message]
2009-05-19 9:33 ` [PATCH 1/3] ub: use __blk_end_request_all() Tejun Heo
2009-05-19 9:33 ` [PATCH 2/3] block: set rq->resid_len to blk_rq_bytes() on issue Tejun Heo
2009-05-19 9:33 ` [PATCH 3/3] bio: always copy back data for copied kernel requests Tejun Heo
2009-05-19 9:39 ` [PATCHSET block#for-2.6.31] block: fix fallouts from recent cleanups, take#2 Jens Axboe
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=1242725586-13142-1-git-send-email-tj@kernel.org \
--to=tj@kernel.org \
--cc=bharrosh@panasas.com \
--cc=bzolnier@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=petkovbb@googlemail.com \
/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;
as well as URLs for NNTP newsgroup(s).