From: Sebastian Herbszt <herbszt@gmx.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Bart Van Assche <bart.vanassche@sandisk.com>,
Christoph Hellwig <hch@lst.de>,
Johannes Thumshirn <jthumshirn@suse.de>,
Dan Williams <dan.j.williams@intel.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: [PATCH] Separate target visibility from reaped state information
Date: Sun, 7 Feb 2016 23:48:28 +0100 [thread overview]
Message-ID: <20160207234828.0000708e@localhost> (raw)
In-Reply-To: <yq160y7q5ku.fsf@sermon.lab.mkp.net>
Martin K. Petersen wrote:
> >>>>> "Sebastian" == Sebastian Herbszt <herbszt@gmx.de> writes:
>
> >> The only change from the current workflow is that the DEL transition
> >> (now the reaped flag) is done before the spin lock is dropped which
> >> would fix a tiny window for two threads both trying to remove the
> >> same target, but there's nothing that could possibly fix an iterative
> >> soft lockup caused by restarting the loop, which is what the
> >> changelog says.
>
> Sebastian> James, Martin, what's the status of this patch? I still hit
> Sebastian> the reported soft lockup on 4.5-rc1.
>
> And you have verified that Bart's patch applied on top of 4.5-rc1 still
> fixes the lockup? (I know you tested a previous version)
I now have verified that Bart's patch does fix my soft lockup on 4.5-rc2.
Sebastian
next prev parent reply other threads:[~2016-02-07 22:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 16:51 [PATCH] Separate target visibility from reaped state information Bart Van Assche
2016-01-18 8:55 ` Johannes Thumshirn
2016-01-20 0:30 ` Martin K. Petersen
2016-01-20 1:03 ` James Bottomley
2016-01-31 17:54 ` Sebastian Herbszt
2016-02-02 1:11 ` Martin K. Petersen
2016-02-02 9:03 ` Johannes Thumshirn
2016-02-03 17:17 ` Christoph Hellwig
2016-02-03 17:54 ` James Bottomley
2016-02-03 21:37 ` *** GMX Spamverdacht *** " Sebastian Herbszt
2016-02-07 22:48 ` Sebastian Herbszt [this message]
2016-02-02 3:43 ` Bart Van Assche
2016-02-02 11:46 ` James Bottomley
2016-02-02 18:29 ` Bart Van Assche
2016-02-03 0:43 ` James Bottomley
2016-02-03 1:17 ` Bart Van Assche
2016-02-03 2:01 ` James Bottomley
2016-02-03 22:38 ` Sebastian Herbszt
2016-02-03 22:55 ` James Bottomley
2016-02-03 23:28 ` Sebastian Herbszt
2016-02-07 22:56 ` Sebastian Herbszt
2016-02-10 14:05 ` Johannes Thumshirn
2016-02-10 15:34 ` James Bottomley
2016-02-10 16:06 ` Johannes Thumshirn
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=20160207234828.0000708e@localhost \
--to=herbszt@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bart.vanassche@sandisk.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).