mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Parthiban Veerasooran <parthiban.veerasooran@microchip.com>
To: <Selvamani.Rajagopal@onsemi.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Andrew Lunn <andrew@lunn.ch>, Andrew Lunn <andrew+netdev@lunn.ch>,
	Piergiorgio Beruto <pier.beruto@onsemi.com>,
	"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 v4 3/3] net: ethernet: oa_tc6: Disabled tx queues when disable_traffic is set
Date: Wed, 22 Jul 2026 15:39:34 +0530	[thread overview]
Message-ID: <b6524b93-593f-49c5-88f2-393297ed86fd@microchip.com> (raw)
In-Reply-To: <20260720-fix-race-condition-and-crash-v4-3-8273e2f38a1f@onsemi.com>

Imperative mood for the subject: "Disable tx queues when disable_traffic 
is set" (netdev convention).

On 21/07/26 7:50 am, Selvamani Rajagopal via B4 Relay wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> From: Selvamani Rajagopal <Selvamani.Rajagopal@onsemi.com>
> 
> Previously, TX queue interface was stopped when
> disable_traffic flag was set. It is more appropriate to
> disable the queue as there is no recovery, once
> disable_traffic is set. Carrier is also marked off
"Carrier is also marked off" contradicts both the code and your own v4 
changelog: the patch only adds netif_tx_disable(), there is no 
netif_carrier_off(), and v4 says you reverted the carrier change. Please 
drop this sentence — the message currently describes behavior the patch 
doesn't implement.
> 
> Fixes: b542d13fab0f ("net: ethernet: oa_tc6: Interrupt is active low, level triggered.")
> Signed-off-by: Selvamani Rajagopal <Selvamani.Rajagopal@onsemi.com>
> 
--- is missing
> changes in v4
>    - Reverted the the statement that turned carrier off on
typo.
>      disble_traffic, as it may have side effects
typo.
> changes in v3
>    - New patch. Carrier marked off once disable_traffic is set
> ---
>   drivers/net/ethernet/oa_tc6.c | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/drivers/net/ethernet/oa_tc6.c b/drivers/net/ethernet/oa_tc6.c
> index 9e6850ccfe6c..4b8f6280be51 100644
> --- a/drivers/net/ethernet/oa_tc6.c
> +++ b/drivers/net/ethernet/oa_tc6.c
> @@ -730,6 +730,11 @@ static void oa_tc6_disable_traffic(struct oa_tc6 *tc6)
>          skb = oa_tc6_detach_waiting_tx_skb(tc6);
>          spin_unlock_bh(&tc6->tx_skb_lock);
> 
> +       /* disable_traffic, when set, is a point of no
> +        * return to working state. TX queues are
> +        * disabled.
> +        */
Comment wraps at ~40 columns; fill to ~80 like the rest of the file.

Best regards,
Parthiban V
> +       netif_tx_disable(tc6->netdev);
>          oa_tc6_drop_tx_skb(tc6, skb);
>          oa_tc6_free_ongoing_skbs(tc6);
>          oa_tc6_write_register(tc6, OA_TC6_REG_INT_MASK0, regval);
> 
> --
> 2.43.0
> 
> 


  reply	other threads:[~2026-07-22 10:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  2:20 [PATCH net v4 0/3] Fix to possible skb leak due to race condtion in tx path Selvamani Rajagopal via B4 Relay
2026-07-21  2:20 ` [PATCH net v4 1/3] net: ethernet: oa_tc6: Protect skb pointer used by two different kernel instances Selvamani Rajagopal via B4 Relay
2026-07-22 10:08   ` Parthiban Veerasooran
2026-07-27  0:26     ` Selvamani Rajagopal
2026-07-21  2:20 ` [PATCH net v4 2/3] net: ethernet: oa_tc6: Improvements to error recovery Selvamani Rajagopal via B4 Relay
2026-07-22 10:09   ` Parthiban Veerasooran
2026-07-27  0:06     ` Selvamani Rajagopal
2026-07-21  2:20 ` [PATCH net v4 3/3] net: ethernet: oa_tc6: Disabled tx queues when disable_traffic is set Selvamani Rajagopal via B4 Relay
2026-07-22 10:09   ` Parthiban Veerasooran [this message]
2026-07-26 22:59     ` Selvamani Rajagopal

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=b6524b93-593f-49c5-88f2-393297ed86fd@microchip.com \
    --to=parthiban.veerasooran@microchip.com \
    --cc=Selvamani.Rajagopal@onsemi.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pier.beruto@onsemi.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

all inboxes | Powered by JetHome®