From: Bart Van Assche <bvanassche@acm.org>
To: Laurence Oberman <loberman@redhat.com>, Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Christoph Hellwig <hch@infradead.org>,
Hannes Reinecke <hare@suse.com>,
James Smart <james.smart@broadcom.com>,
Jianchao Wang <jianchao.w.wang@oracle.com>,
Keith Busch <keith.busch@intel.com>,
Dongli Zhang <dongli.zhang@oracle.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] block: Fix blk_mq_try_issue_directly()
Date: Thu, 04 Apr 2019 10:09:15 -0700 [thread overview]
Message-ID: <1554397755.118779.252.camel@acm.org> (raw)
In-Reply-To: <4b19805967da8d6a11346a7820af06eb91c5bc6c.camel@redhat.com>
On Thu, 2019-04-04 at 12:47 -0400, Laurence Oberman wrote:
> I can conform, reverting those 3 in order also resolves the panic I was
> seeing. I have 3 reboot tests of the srpt server allowing the client ot
> remain stable and try reconnect.
>
> For the above patch:
> Tested-by: Laurence Oberman <loberman@redhat.com>
>
> Too many changes in code I am not familiar enough to review and
> comnment why reverting helps.
Thanks for the testing!
Bart.
next prev parent reply other threads:[~2019-04-04 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 20:11 [PATCH] block: Fix blk_mq_try_issue_directly() Bart Van Assche
2019-04-04 7:08 ` Ming Lei
2019-04-04 14:59 ` Bart Van Assche
2019-04-04 15:09 ` Laurence Oberman
2019-04-04 15:28 ` Bart Van Assche
2019-04-04 15:33 ` Laurence Oberman
2019-04-04 16:47 ` Laurence Oberman
2019-04-04 17:09 ` Bart Van Assche [this message]
2019-04-08 2:07 ` jianchao.wang
2019-04-08 2:36 ` jianchao.wang
2019-04-09 1:31 ` jianchao.wang
2019-04-09 12:28 ` Laurence Oberman
2019-04-10 0:51 ` jianchao.wang
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=1554397755.118779.252.camel@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=dongli.zhang@oracle.com \
--cc=hare@suse.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=jianchao.w.wang@oracle.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=ming.lei@redhat.com \
--cc=stable@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.