All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maurizio Lombardi <mlombard@redhat.com>
To: Paul Dagnelie <pcd@delphix.com>
Cc: target-devel@vger.kernel.org, Sumedh Bala <sbala@delphix.com>,
	Sebastien Roy <sebastien.roy@delphix.com>
Subject: Re: [BUG] iscsi hangs during login attempt
Date: Mon, 19 Sep 2022 19:01:42 +0200	[thread overview]
Message-ID: <CAFL455nJWMV31xVzpnZ4PCdmnWZ11fnKwnzegW_sNfuqoZDjJw@mail.gmail.com> (raw)
In-Reply-To: <CAJ-UWOeis8L26X1rSa0t+h3rzmQCFLSxPKBS7YiP=hArgnjPSA@mail.gmail.com>

Hello,

st 14. 9. 2022 v 20:00 odesílatel Paul Dagnelie <pcd@delphix.com> napsal:
>
> iscsit_cause_connection_reinstatement signals the rx and tx threads,
> and then waits for the conn_wait_comp completion, which is signalled
> in iscsit_close_connection. That appears to be called by the tx and rx
> threads when they exit.  After puzzling through the core for a bit, I
> found the kernel threads in question, and they appear to be calmly
> waiting in the normal blocking path waiting for IOs to come in for
> them to respond to. I would think that if they were in that state when
> the SIGINT came in they would have exited properly.

I received a few bug reports and crash dumps during the past months that
appear to be about  the same problem.
Our QA is able to reproduce it so I will test if it's really the same issue
and if your hypothesis is correct, I am going to try to come up with a patch.

Thanks,
Maurizio


  reply	other threads:[~2022-09-19 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 18:00 [BUG] iscsi hangs during login attempt Paul Dagnelie
2022-09-19 17:01 ` Maurizio Lombardi [this message]
2022-09-20 15:49 ` Maurizio Lombardi
2022-09-20 17:51   ` Paul Dagnelie
2022-09-26 17:03     ` Maurizio Lombardi
     [not found]       ` <CAEU3=8GPcCagm_VW3p9miw1ALr-y7=SvONLxLBBeWft-R2o3YA@mail.gmail.com>
2022-10-31 21:13         ` Paul Dagnelie
2022-11-04 10:34           ` Maurizio Lombardi

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=CAFL455nJWMV31xVzpnZ4PCdmnWZ11fnKwnzegW_sNfuqoZDjJw@mail.gmail.com \
    --to=mlombard@redhat.com \
    --cc=pcd@delphix.com \
    --cc=sbala@delphix.com \
    --cc=sebastien.roy@delphix.com \
    --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.