From: patchwork-bot+netdevbpf@kernel.org
To: Geetha sowjanya <gakula@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lcherian@marvell.com, tduszynski@marvell.com, kuba@kernel.org,
davem@davemloft.net, hkelam@marvell.com, sbhatta@marvell.com,
sgoutham@marvell.com
Subject: Re: [net PATCH] octeontx2-pf: Fix interface down flag on error
Date: Sun, 25 Jul 2021 08:30:05 +0000 [thread overview]
Message-ID: <162720180521.26018.4602291131095083214.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210725075903.6426-1-gakula@marvell.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Sun, 25 Jul 2021 13:29:03 +0530 you wrote:
> In the existing code while changing the number of TX/RX
> queues using ethtool the PF/VF interface resources are
> freed and reallocated (otx2_stop and otx2_open is called)
> if the device is in running state. If any resource allocation
> fails in otx2_open, driver free already allocated resources
> and return. But again, when the number of queues changes
> as the device state still running oxt2_stop is called.
> In which we try to free already freed resources leading
> to driver crash.
> This patch fixes the issue by setting the INTF_DOWN flag on
> error and free the resources in otx2_stop only if the flag is
> not set.
>
> [...]
Here is the summary with links:
- [net] octeontx2-pf: Fix interface down flag on error
https://git.kernel.org/netdev/net/c/69f0aeb13bb5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-07-25 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 7:59 [net PATCH] octeontx2-pf: Fix interface down flag on error Geetha sowjanya
2021-07-25 8:30 ` patchwork-bot+netdevbpf [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=162720180521.26018.4602291131095083214.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=tduszynski@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox