From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 47701] When too many disks fall out at the same time, RCU hangs
Date: Sun, 7 Oct 2012 02:20:43 +0000 (UTC) [thread overview]
Message-ID: <20121007022043.E4EB711FC43@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-47701-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=47701
Joe Lawrence <joe.lawrence@stratus.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |joe.lawrence@stratus.com
--- Comment #2 from Joe Lawrence <joe.lawrence@stratus.com> 2012-10-07 02:20:43 ---
Stratus noticed a similar crash (hang actually) earlier this week when removing
a single SAS disk as part of a RAID 1 MD mirror. In our instance, the all CPUs
were idle, except one that was running scsi_target_reap and another waiting on
RCU synchronize_sched. Since the former function was stuck in some loop, RCU
stalled and the machine wedged. Another Stratus engineer noticed patch [1],
and once applied to our kernel, MD/mpt2sas disk removal no longer hung the
machine.
[1] [SCSI] scsi_remove_target: fix softlockup regression on hot remove
https://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=bc3f02a795d3b4faa99d37390174be2a75d091bd
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-10-07 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 23:13 [Bug 47701] New: When too many disks fall out at the same time, RCU hangs bugzilla-daemon
2012-10-06 14:30 ` [Bug 47701] " bugzilla-daemon
2012-10-07 2:20 ` bugzilla-daemon [this message]
2012-10-07 14:20 ` bugzilla-daemon
2013-11-19 23:10 ` bugzilla-daemon
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=20121007022043.E4EB711FC43@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).