From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
Kiran Patil <kiran.patil@intel.com>,
Nicholas Bellinger <nab@linux-iscsi.org>
Subject: [PATCH-v2 0/4] Bugfixes for .39-rc8
Date: Tue, 10 May 2011 21:35:31 -0700 [thread overview]
Message-ID: <1305088535-27486-1-git-send-email-nab@linux-iscsi.org> (raw)
From: Nicholas Bellinger <nab@linux-iscsi.org>
Hi James and Co,
This series is resend of four patches that should be considered critical
target core bugfixes for .39 that have been under stress testing in a
couple of different labs recently using lio-core-2.6.git/lio-4.1 (.39-rcX)
and /lio-4.0 (.38.3) branch code.
These are all important bugfixes that are required to run with in-flight
.40 HW target drivers in the upstream LIO tree. This includes fixes for
the main transport_do_task_sg_chain() Data I/O mapping logic, and
task->task_sg[] shutdown path from MSI-X interrupt context. These bugfixes
apply for all of the following HW fabric drivers:
tcm_fc(openfcoe) w/ ddp offload, tcm_qla2xxx, ib_srpt and ibmvscsis.
These patches address issues that are able to easily produce OOPsen with
small backstore max_sectors values. Please review+apply for .39 and
also queue into stable@kernel.org for .38.
The series is also available here for a direct pull:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/scsi-post-merge-2.6.git for-39-rc-fixes
and has been made against the following scsi-rc-fixes-2.6.git HEAD:
commit c055f5b2614b4f758ae6cc86733f31fa4c2c5844
Author: James Bottomley <James.Bottomley@suse.de>
Date: Sun May 1 09:42:07 2011 -0500
[SCSI] fix oops in scsi_run_queue()
Thanks!
--nab
Nicholas Bellinger (4):
target: Fix multi task->task_sg[] chaining logic bug
target: Fix interrupt context bug with stats_lock and
core_tmr_alloc_req
target: Fix bug with task_sg chained transport_free_dev_tasks release
target: Fix task->task_execute_queue=1 clear bug + LUN_RESET OOPs
drivers/target/target_core_device.c | 4 +-
drivers/target/target_core_tmr.c | 7 +++--
drivers/target/target_core_transport.c | 46 +++++++++++++++++++++++--------
include/target/target_core_base.h | 1 +
include/target/target_core_transport.h | 1 +
5 files changed, 42 insertions(+), 17 deletions(-)
--
1.7.5.1
next reply other threads:[~2011-05-11 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 4:35 Nicholas A. Bellinger [this message]
2011-05-11 4:35 ` [PATCH-v2 1/4] target: Fix multi task->task_sg[] chaining logic bug Nicholas A. Bellinger
2011-05-17 21:27 ` Kiran Patil
2011-05-11 4:35 ` [PATCH-v2 2/4] target: Fix interrupt context bug with stats_lock and core_tmr_alloc_req Nicholas A. Bellinger
2011-05-11 4:35 ` [PATCH-v2 3/4] target: Fix bug with task_sg chained transport_free_dev_tasks release Nicholas A. Bellinger
2011-05-11 4:35 ` [PATCH-v2 4/4] target: Fix task->task_execute_queue=1 clear bug + LUN_RESET OOPs Nicholas A. Bellinger
2011-05-14 0:05 ` [PATCH-v2 0/4] Bugfixes for .39-rc8 Nicholas A. Bellinger
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=1305088535-27486-1-git-send-email-nab@linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hch@lst.de \
--cc=kiran.patil@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).