From: Greg KH <greg@kroah.com>
To: Steve Wise <swise@opengridcomputing.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 2/3] iw_cxgb4: drop listen destroy replies if no ep found
Date: Fri, 15 Sep 2017 09:46:27 -0700 [thread overview]
Message-ID: <20170915164627.GC27343@kroah.com> (raw)
In-Reply-To: <20170915140752.A29BEE0C1D@smtp.ogc.us>
On Tue, Sep 05, 2017 at 11:52:33AM -0700, Steve Wise wrote:
> If the thread waiting for a CLOSE_LISTSRV_RPL times out and bails,
> then we need to handle a subsequent CPL if it arrives and the stid has
> been released. In this case silently drop it.
>
> Signed-off-by: Steve Wise <swise@opengridcomputing.com>
> ---
> drivers/infiniband/hw/cxgb4/cm.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/infiniband/hw/cxgb4/cm.c b/drivers/infiniband/hw/cxgb4/cm.c
> index 6d85a5d..d76bfe3 100644
> --- a/drivers/infiniband/hw/cxgb4/cm.c
> +++ b/drivers/infiniband/hw/cxgb4/cm.c
> @@ -2333,9 +2333,14 @@ static int close_listsrv_rpl(struct c4iw_dev *dev, struct sk_buff *skb)
> unsigned int stid = GET_TID(rpl);
> struct c4iw_listen_ep *ep = get_ep_from_stid(dev, stid);
>
> + if (!ep) {
> + pr_debug("%s stid %d lookup failure!\n", __func__, stid);
> + goto out;
> + }
> pr_debug("%s ep %p\n", __func__, ep);
> c4iw_wake_up(&ep->com.wr_wait, status2errno(rpl->status));
> c4iw_put_ep(&ep->com);
> +out:
> return 0;
> }
>
> --
> 1.8.3.1
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
prev parent reply other threads:[~2017-09-15 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 18:52 [PATCH 2/3] iw_cxgb4: drop listen destroy replies if no ep found Steve Wise
2017-09-15 16:46 ` Greg KH [this message]
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=20170915164627.GC27343@kroah.com \
--to=greg@kroah.com \
--cc=dledford@redhat.com \
--cc=linux-rdma@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=swise@opengridcomputing.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).