All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Roger Quadros <rogerq@kernel.org>
Cc: 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>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Jesper Dangaard Brouer <hawk@kernel.org>,
	John Fastabend <john.fastabend@gmail.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Maxime Chevallier <maxime.chevallier@bootlin.com>,
	Siddharth Vadapalli <s-vadapalli@ti.com>,
	Md Danish Anwar <danishanwar@ti.com>,
	Govindarajan Sriramakrishnan <srk@ti.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org
Subject: Re: [PATCH net v3 2/2] net: ethernet: ti: am65-cpsw: fix warning in am65_cpsw_nuss_remove_rx_chns()
Date: Tue, 5 Nov 2024 13:30:42 +0000	[thread overview]
Message-ID: <20241105133042.GD4507@kernel.org> (raw)
In-Reply-To: <20241101-am65-cpsw-multi-rx-j7-fix-v3-2-338fdd6a55da@kernel.org>

On Fri, Nov 01, 2024 at 12:18:51PM +0200, Roger Quadros wrote:
> flow->irq is initialized to 0 which is a valid IRQ. Set it to -EINVAL
> in error path of am65_cpsw_nuss_init_rx_chns() so we do not try
> to free an unallocated IRQ in am65_cpsw_nuss_remove_rx_chns().
> 
> If user tried to change number of RX queues and am65_cpsw_nuss_init_rx_chns()
> failed due to any reason, the warning will happen if user tries to change
> the number of RX queues after the error condition.
> 
> root@am62xx-evm:~# ethtool -L eth0 rx 3
> [   40.385293] am65-cpsw-nuss 8000000.ethernet: set new flow-id-base 19
> [   40.393211] am65-cpsw-nuss 8000000.ethernet: Failed to init rx flow2
> netlink error: Invalid argument
> root@am62xx-evm:~# ethtool -L eth0 rx 2
> [   82.306427] ------------[ cut here ]------------
> [   82.311075] WARNING: CPU: 0 PID: 378 at kernel/irq/devres.c:144 devm_free_irq+0x84/0x90
> [   82.469770] Call trace:
> [   82.472208]  devm_free_irq+0x84/0x90
> [   82.475777]  am65_cpsw_nuss_remove_rx_chns+0x6c/0xac [ti_am65_cpsw_nuss]
> [   82.482487]  am65_cpsw_nuss_update_tx_rx_chns+0x2c/0x9c [ti_am65_cpsw_nuss]
> [   82.489442]  am65_cpsw_set_channels+0x30/0x4c [ti_am65_cpsw_nuss]
> [   82.495531]  ethnl_set_channels+0x224/0x2dc
> [   82.499713]  ethnl_default_set_doit+0xb8/0x1b8
> [   82.504149]  genl_family_rcv_msg_doit+0xc0/0x124
> [   82.508757]  genl_rcv_msg+0x1f0/0x284
> [   82.512409]  netlink_rcv_skb+0x58/0x130
> [   82.516239]  genl_rcv+0x38/0x50
> [   82.519374]  netlink_unicast+0x1d0/0x2b0
> [   82.523289]  netlink_sendmsg+0x180/0x3c4
> [   82.527205]  __sys_sendto+0xe4/0x158
> [   82.530779]  __arm64_sys_sendto+0x28/0x38
> [   82.534782]  invoke_syscall+0x44/0x100
> [   82.538526]  el0_svc_common.constprop.0+0xc0/0xe0
> [   82.543221]  do_el0_svc+0x1c/0x28
> [   82.546528]  el0_svc+0x28/0x98
> [   82.549578]  el0t_64_sync_handler+0xc0/0xc4
> [   82.553752]  el0t_64_sync+0x190/0x194
> [   82.557407] ---[ end trace 0000000000000000 ]---
> 
> Fixes: da70d184a8c3 ("net: ethernet: ti: am65-cpsw: Introduce multi queue Rx")

Hi Roger,

I wonder if the problem predates the cited commit and was, rather,
introduced by:

Fixes: 24bc19b05f1f ("net: ethernet: ti: am65-cpsw: Add suspend/resume support")

...

  reply	other threads:[~2024-11-05 13:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 10:18 [PATCH net v3 0/2] net: ethernet: ti: am65-cpsw: Fixes to multi queue RX feature Roger Quadros
2024-11-01 10:18 ` [PATCH net v3 1/2] net: ethernet: ti: am65-cpsw: Fix multi queue Rx on J7 Roger Quadros
2024-11-05 13:21   ` Simon Horman
2024-11-05 13:52     ` Roger Quadros
2024-11-01 10:18 ` [PATCH net v3 2/2] net: ethernet: ti: am65-cpsw: fix warning in am65_cpsw_nuss_remove_rx_chns() Roger Quadros
2024-11-05 13:30   ` Simon Horman [this message]
2024-11-05 14:11     ` Roger Quadros
2024-11-05 15:10 ` [PATCH net v3 0/2] net: ethernet: ti: am65-cpsw: Fixes to multi queue RX feature patchwork-bot+netdevbpf

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=20241105133042.GD4507@kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=danishanwar@ti.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rogerq@kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=srk@ti.com \
    --cc=vigneshr@ti.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.