All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: target-devel@vger.kernel.org
Subject: Re: SPC-3 persistent reservations race condition
Date: Tue, 20 Nov 2018 18:31:13 +0000	[thread overview]
Message-ID: <20181120193113.4959ad61@suse.de> (raw)
In-Reply-To: <3ee76029-a49c-e5ce-39c8-62af5f4ce711@zoner.cz>

Hi Martin,

On Tue, 13 Nov 2018 16:17:36 +0100, Martin Svec wrote:

> Hello,
> 
> during Hyper-V Cluster Validation tests, we hit a bug in SPC-3 persistent reservations
> implementation where LIO iSCSI target started to loop indefinitely while freeing
> a PR registration.

Any chance you could capture and share a network trace for the specific
test that triggers the deadlock. Having something to turn into a
libiscsi regression test would be helpful here.

Cheers, David

  reply	other threads:[~2018-11-20 18:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 15:17 SPC-3 persistent reservations race condition Martin Svec
2018-11-20 18:31 ` David Disseldorp [this message]
2018-11-21 13:16 ` Martin Svec
2018-11-21 13:33 ` David Disseldorp
2018-11-22 18:47 ` Martin Svec
2018-11-25 23:10 ` David Disseldorp
2018-11-29 13:40 ` Martin Svec
2018-11-29 13:57 ` David Disseldorp

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=20181120193113.4959ad61@suse.de \
    --to=ddiss@suse.de \
    --cc=target-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.