Linux PCI Non-Transparent Bridge framework and drivers
 help / color / mirror / Atom feed
From: "Allen Hubbe" <Allen.Hubbe@dell.com>
To: 'Dave Jiang' <dave.jiang@intel.com>, jdmason@kudzu.us
Cc: linux-ntb@googlegroups.com
Subject: RE: [PATCH] ntb: transport shouldn't disable link due to bogus values in SPADs
Date: Mon, 31 Jul 2017 10:46:42 -0400	[thread overview]
Message-ID: <000001d30a0b$d3b52b20$7b1f8160$@dell.com> (raw)
In-Reply-To: <150127984807.48385.10962784387437107365.stgit@djiang5-desk3.ch.intel.com>

From: Dave Jiang
> It seems that under certain scenarios the SPAD can have bogus values caused
> by an agent (i.e. BIOS or other software) that is not the kernel driver, and
> that causes memory window setup failure. This should not cause the link to
> be disabled because if we do that, the driver will never recover again. We
> have verified in testing that this issue happens and prevents proper link
> recovery.
> 
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>

Acked-by: Allen Hubbe <Allen.Hubbe@dell.com>

> ---
>  drivers/ntb/ntb_transport.c |    4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/drivers/ntb/ntb_transport.c b/drivers/ntb/ntb_transport.c
> index 9a03c58..f0dd5a7 100644
> --- a/drivers/ntb/ntb_transport.c
> +++ b/drivers/ntb/ntb_transport.c
> @@ -924,10 +924,8 @@ static void ntb_transport_link_work(struct work_struct *work)
>  		ntb_free_mw(nt, i);
> 
>  	/* if there's an actual failure, we should just bail */
> -	if (rc < 0) {
> -		ntb_link_disable(ndev);
> +	if (rc < 0)
>  		return;
> -	}
> 
>  out:
>  	if (ntb_link_is_up(ndev, NULL, NULL) == 1)
> 
> --
> You received this message because you are subscribed to the Google Groups "linux-ntb" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to linux-
> ntb+unsubscribe@googlegroups.com.
> To post to this group, send email to linux-ntb@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/linux-
> ntb/150127984807.48385.10962784387437107365.stgit%40djiang5-desk3.ch.intel.com.
> For more options, visit https://groups.google.com/d/optout.


  reply	other threads:[~2017-07-31 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 22:10 [PATCH] ntb: transport shouldn't disable link due to bogus values in SPADs Dave Jiang
2017-07-31 14:46 ` Allen Hubbe [this message]
2017-08-01 17:33   ` Jon Mason

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='000001d30a0b$d3b52b20$7b1f8160$@dell.com' \
    --to=allen.hubbe@dell.com \
    --cc=dave.jiang@intel.com \
    --cc=jdmason@kudzu.us \
    --cc=linux-ntb@googlegroups.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