patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Somnath Kotur <somnath.kotur@broadcom.com>
To: Luca Boccassi <bluca@debian.org>
Cc: dpdk stable <stable@dpdk.org>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [dpdk-stable] [19.11 1/2] net/bnxt: fix checking VNIC in shutdown path
Date: Thu, 29 Oct 2020 16:14:52 +0530	[thread overview]
Message-ID: <CAOBf=ms-MRWXKajaQAvm9tt9rNiU8LWUMMQ7D6ynnCLSLQp5Jw@mail.gmail.com> (raw)
In-Reply-To: <97365917b7997e22444eefdfb3e9f1e45f543c7a.camel@debian.org>

Oh ok... Apologies then Luca..We went by the final diff you had between the
upstream commit patch and the actual patch... perhaps that confused us or
threw us ( speaking for kalesh's 2 patches as well) off a bit ...
If they( all 4) are identical to what you already have on your sandbox,
then indeed we are good to go

Thanks a lot
Som




On Thu, 29 Oct 2020, 16:06 Luca Boccassi, <bluca@debian.org> wrote:

> On Thu, 2020-10-29 at 14:14 +0530, Somnath Kotur wrote:
> > [ backported from upstream commit
> 4b029f02de3a0ce9cdd9a3475b84ca2e42d74281 ]
> >
> > Add a couple of NULL pointer checks in bnxt_free_all_filters()
> > and bnxt_free_vnics() respectively to guard against certain error
> > injection/recovery scenarios where it was found that the application
> > was crashing with the bp->vnic_info pointer being NULL.
> >
> > Fixes: 51fafb89a9a0 ("net/bnxt: get rid of ff pools and use VNIC info
> array")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com>
> > Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> > ---
> >  drivers/net/bnxt/bnxt_filter.c | 15 +++++++++------
> >  drivers/net/bnxt/bnxt_vnic.c   |  3 +++
> >  2 files changed, 12 insertions(+), 6 deletions(-)
>
> Hi,
>
> Both of these patches appear to be 100% identical to the ones I pushed
> yesterday? Was there something unclear in the generated email that made
> you think the rebase was different that we can fix?
>
>
> https://github.com/bluca/dpdk-stable/commit/77abebfe906e80404ecdfa71c60da318cd0fb563
>
> https://github.com/bluca/dpdk-stable/commit/618bfe2417717a3b446180a10d1a2299d3f626e9
>
> --
> Kind regards,
> Luca Boccassi
>

      reply	other threads:[~2020-10-29 10:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  8:44 Somnath Kotur
2020-10-29  8:44 ` [dpdk-stable] [19.11 2/2] net/bnxt: add separate mutex for FW health check Somnath Kotur
2020-10-29 10:36 ` [dpdk-stable] [19.11 1/2] net/bnxt: fix checking VNIC in shutdown path Luca Boccassi
2020-10-29 10:44   ` Somnath Kotur [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='CAOBf=ms-MRWXKajaQAvm9tt9rNiU8LWUMMQ7D6ynnCLSLQp5Jw@mail.gmail.com' \
    --to=somnath.kotur@broadcom.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=bluca@debian.org \
    --cc=stable@dpdk.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 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).