All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Subbaraya Sundeep <sbhatta@marvell.com>,
	davem@davemloft.net, kuba@kernel.org, sgoutham@marvell.com,
	netdev@vger.kernel.org
Subject: Re: [net PATCH 4/5] octeontx2-af: Fix mcam entry resource leak
Date: Tue, 26 Jul 2022 15:32:53 +0200	[thread overview]
Message-ID: <04967132ceb556048db399b1cc8ec065365fa62d.camel@redhat.com> (raw)
In-Reply-To: <1658672209-8837-5-git-send-email-sbhatta@marvell.com>

On Sun, 2022-07-24 at 19:46 +0530, Subbaraya Sundeep wrote:
> The teardown sequence in FLR handler returns if no NIX LF
> is attached to PF/VF because it indicates that graceful
> shutdown of resources already happened. But there is a
> chance of all allocated MCAM entries not being freed by
> PF/VF. Hence free mcam entries even in case of detached LF.
> 
> Fixes: c554f9c1574e("octeontx2-af: Teardown NPA, NIX LF upon receiving FLR")

The above fixes tag need a space between the commit hash and the '('.
Could you adjust that and post a new version?

Thanks!

Paolo


  reply	other threads:[~2022-07-26 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-24 14:16 [net PATCH 0/5] Octeontx2 AF driver fixes for NPC Subbaraya Sundeep
2022-07-24 14:16 ` [net PATCH 1/5] octeontx2-af: Apply tx nibble fixup always Subbaraya Sundeep
2022-07-24 14:16 ` [net PATCH 2/5] octeontx2-af: suppress external profile loading warning Subbaraya Sundeep
2022-07-24 14:16 ` [net PATCH 3/5] octeontx2-af: Allow mkex profiles without dmac Subbaraya Sundeep
2022-07-24 14:16 ` [net PATCH 4/5] octeontx2-af: Fix mcam entry resource leak Subbaraya Sundeep
2022-07-26 13:32   ` Paolo Abeni [this message]
2022-07-24 14:16 ` [net PATCH 5/5] octeontx2-af: Fix key checking for source mac Subbaraya Sundeep

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=04967132ceb556048db399b1cc8ec065365fa62d.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.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 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.