From: Simon Horman <horms@kernel.org>
To: Vimlesh Kumar <vimleshk@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
sedara@marvell.com, srasheed@marvell.com, hgani@marvell.com,
Veerasenareddy Burru <vburru@marvell.com>,
Satananda Burla <sburla@marvell.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net v3 3/3] octeon_ep_vf: ensure dbell BADDR updation
Date: Mon, 12 Jan 2026 14:39:42 +0000 [thread overview]
Message-ID: <aWUHrqOpf-6hZqlu@horms.kernel.org> (raw)
In-Reply-To: <20260107131857.3434352-4-vimleshk@marvell.com>
On Wed, Jan 07, 2026 at 01:18:56PM +0000, Vimlesh Kumar wrote:
> Make sure the OUT DBELL base address reflects the
> latest values written to it.
>
> Fix:
> Add a wait until the OUT DBELL base address register
> is updated with the DMA ring descriptor address,
> and modify the setup_oq function to properly
> handle failures.
>
> Fixes: 2c0c32c72be29 ("octeon_ep_vf: add hardware configuration APIs")
> Signed-off-by: Sathesh Edara <sedara@marvell.com>
> Signed-off-by: Shinas Rasheed <srasheed@marvell.com>
> Signed-off-by: Vimlesh Kumar <vimleshk@marvell.com>
> ---
> V3:
> - Use reverse christmas tree order variable declaration.
> - Return error if timeout happens during setup oq.
...
> diff --git a/drivers/net/ethernet/marvell/octeon_ep_vf/octep_vf_rx.c b/drivers/net/ethernet/marvell/octeon_ep_vf/octep_vf_rx.c
> index d70c8be3cfc4..6446f6bf0b90 100644
> --- a/drivers/net/ethernet/marvell/octeon_ep_vf/octep_vf_rx.c
> +++ b/drivers/net/ethernet/marvell/octeon_ep_vf/octep_vf_rx.c
> @@ -171,7 +171,9 @@ static int octep_vf_setup_oq(struct octep_vf_device *oct, int q_no)
> goto oq_fill_buff_err;
>
> octep_vf_oq_reset_indices(oq);
> - oct->hw_ops.setup_oq_regs(oct, q_no);
> + if (oct->hw_ops.setup_oq_regs(oct, q_no))
> + goto oq_fill_buff_err;
> +
Hi Vimlesh, all,
I think that a new label needs to be added to the unwind ladder such that
octep_vf_oq_free_ring_buffers() is called if the error condition above is met.
Likewise in patch 2/3.
Flagged by Claude Code with Review Prompts[1]
[1] https://github.com/masoncl/review-prompts/
> oct->num_oqs++;
>
> return 0;
--
pw-bot: cr
next prev parent reply other threads:[~2026-01-12 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 13:18 [PATCH net v3 0/3] disable interrupts and ensure dbell updation Vimlesh Kumar
2026-01-07 13:18 ` [PATCH net v3 1/3] octeon_ep: disable per ring interrupts Vimlesh Kumar
2026-01-07 13:18 ` [PATCH net v3 2/3] octeon_ep: ensure dbell BADDR updation Vimlesh Kumar
2026-01-07 13:18 ` [PATCH net v3 3/3] octeon_ep_vf: " Vimlesh Kumar
2026-01-12 14:39 ` Simon Horman [this message]
2026-01-15 9:34 ` [EXTERNAL] " Vimlesh Kumar
2026-01-15 13:46 ` Simon Horman
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=aWUHrqOpf-6hZqlu@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hgani@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sburla@marvell.com \
--cc=sedara@marvell.com \
--cc=srasheed@marvell.com \
--cc=vburru@marvell.com \
--cc=vimleshk@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