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, 26 Sep 2022 19:03:38 +0200	[thread overview]
Message-ID: <CAFL455kcxPSLrJ8R2k-2dTr6f6Eg5W-7M2bUioC=P++W0YC=PA@mail.gmail.com> (raw)
In-Reply-To: <CAJ-UWOeFDrL83akdz70LWYROjD_RboPQrP7kT1vwPvGnu_MyGw@mail.gmail.com>

Hello,

út 20. 9. 2022 v 19:51 odesílatel Paul Dagnelie <pcd@delphix.com> napsal:
>
> That looks like a promising fix, thanks for getting on this so
> quickly! If I can ask, what was the workload/test that you used that
> reproduced it internally so quickly?

Sorry maybe I didn't explain myself clearly enough.
I wanted to say that some months ago our QA submitted some
crash reports that look very similar to the problem you described here.
They have a reproducer (I will ask for details about how it works and
I'll let you know)
but unfortunately the system crashes quite rarely; in other words,
it's not quick at all.

Right now they are trying to reproduce the crash with a recent kernel
so I can look at the crash dump again.

In the meanwhile, did you have any luck with reproducing it?

Maurizio


  reply	other threads:[~2022-09-26 17:39 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
2022-09-20 15:49 ` Maurizio Lombardi
2022-09-20 17:51   ` Paul Dagnelie
2022-09-26 17:03     ` Maurizio Lombardi [this message]
     [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='CAFL455kcxPSLrJ8R2k-2dTr6f6Eg5W-7M2bUioC=P++W0YC=PA@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.