From: David Miller <davem@davemloft.net>
To: yanjun.zhu@oracle.com
Cc: tariqt@mellanox.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, haakon.bugge@oracle.com
Subject: Re: [PATCH 1/1] net/mlx4_core: avoid resetting HCA when accessing an offline device
Date: Mon, 16 Apr 2018 12:51:10 -0400 (EDT) [thread overview]
Message-ID: <20180416.125110.1875435797136179428.davem@davemloft.net> (raw)
In-Reply-To: <1523840527-22746-1-git-send-email-yanjun.zhu@oracle.com>
From: Zhu Yanjun <yanjun.zhu@oracle.com>
Date: Sun, 15 Apr 2018 21:02:07 -0400
> While a faulty cable is used or HCA firmware error, HCA device will
> be offline. When the driver is accessing this offline device, the
> following call trace will pop out.
...
> In the above call trace, the function mlx4_cmd_poll calls the function
> mlx4_cmd_post to access the HCA while HCA is offline. Then mlx4_cmd_post
> returns an error -EIO. Per -EIO, the function mlx4_cmd_poll calls
> mlx4_cmd_reset_flow to reset HCA. And the above call trace pops out.
>
> This is not reasonable. Since HCA device is offline when it is being
> accessed, it should not be reset again.
>
> In this patch, since HCA is offline, the function mlx4_cmd_post returns
> an error -EINVAL. Per -EINVAL, the function mlx4_cmd_poll directly returns
> instead of resetting HCA.
>
> CC: Srinivas Eeda <srinivas.eeda@oracle.com>
> CC: Junxiao Bi <junxiao.bi@oracle.com>
> Suggested-by: Håkon Bugge <haakon.bugge@oracle.com>
> Signed-off-by: Zhu Yanjun <yanjun.zhu@oracle.com>
Tariq, I'm assuming you'll take this in and send it to me later.
Thanks.
next prev parent reply other threads:[~2018-04-16 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 1:02 [PATCH 1/1] net/mlx4_core: avoid resetting HCA when accessing an offline device Zhu Yanjun
2018-04-16 16:51 ` David Miller [this message]
2018-04-17 7:05 ` Tariq Toukan
2018-04-17 15:37 ` Tariq Toukan
2018-04-18 5:46 ` Yanjun Zhu
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=20180416.125110.1875435797136179428.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=haakon.bugge@oracle.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tariqt@mellanox.com \
--cc=yanjun.zhu@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).