Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Alexandra Winter <wintera@linux.ibm.com>
To: stable@vger.kernel.org, stable-commits@vger.kernel.org
Cc: Thorsten Winkler <twinkler@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>
Subject: Re: Patch "s390/qeth: move netif_napi_add_tx() and napi_enable() from under BH" has been added to the 6.13-stable tree
Date: Tue, 18 Feb 2025 16:08:25 +0100	[thread overview]
Message-ID: <b01c840b-55fb-455d-88fa-69848d2dcebf@linux.ibm.com> (raw)
In-Reply-To: <20250218123639.3271098-1-sashal@kernel.org>



On 18.02.25 13:36, Sasha Levin wrote:
> This is a note to let you know that I've just added the patch titled
> 
>     s390/qeth: move netif_napi_add_tx() and napi_enable() from under BH
> 
> to the 6.13-stable tree which can be found at:
>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> 
> The filename of the patch is:
>      s390-qeth-move-netif_napi_add_tx-and-napi_enable-fro.patch
> and it can be found in the queue-6.13 subdirectory.
> 
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
> 

Hello Sasha,
this is a fix for a regression that was introduced with v6.14-rc1.
So I do not think it needs to go into 6.13 stable tree.
But it does not hurt either.


> 
> 
> commit 48eda8093b86b426078bd245a9b4fbc5d057c436
> Author: Alexandra Winter <wintera@linux.ibm.com>
> Date:   Wed Feb 12 17:36:59 2025 +0100
> 
>     s390/qeth: move netif_napi_add_tx() and napi_enable() from under BH
>     
>     [ Upstream commit 0d0b752f2497471ddd2b32143d167d42e18a8f3c ]
>     
>     Like other drivers qeth is calling local_bh_enable() after napi_schedule()
>     to kick-start softirqs [0].
>     Since netif_napi_add_tx() and napi_enable() now take the netdev_lock()
>     mutex [1], move them out from under the BH protection. Same solution as in
>     commit a60558644e20 ("wifi: mt76: move napi_enable() from under BH")
>     
>     Fixes: 1b23cdbd2bbc ("net: protect netdev->napi_list with netdev_lock()")
>     Link: https://lore.kernel.org/netdev/20240612181900.4d9d18d0@kernel.org/ [0]
>     Link: https://lore.kernel.org/netdev/20250115035319.559603-1-kuba@kernel.org/ [1]
>     Signed-off-by: Alexandra Winter <wintera@linux.ibm.com>
>     Acked-by: Joe Damato <jdamato@fastly.com>
>     Link: https://patch.msgid.link/20250212163659.2287292-1-wintera@linux.ibm.com
>     Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>     Signed-off-by: Sasha Levin <sashal@kernel.org>
> 
> diff --git a/drivers/s390/net/qeth_core_main.c b/drivers/s390/net/qeth_core_main.c
> index a3adaec5504e4..20328d695ef92 100644
> --- a/drivers/s390/net/qeth_core_main.c
> +++ b/drivers/s390/net/qeth_core_main.c
> @@ -7050,14 +7050,16 @@ int qeth_open(struct net_device *dev)
>  	card->data.state = CH_STATE_UP;
>  	netif_tx_start_all_queues(dev);
>  
> -	local_bh_disable();
>  	qeth_for_each_output_queue(card, queue, i) {
>  		netif_napi_add_tx(dev, &queue->napi, qeth_tx_poll);
>  		napi_enable(&queue->napi);
> -		napi_schedule(&queue->napi);
>  	}
> -
>  	napi_enable(&card->napi);
> +
> +	local_bh_disable();
> +	qeth_for_each_output_queue(card, queue, i) {
> +		napi_schedule(&queue->napi);
> +	}
>  	napi_schedule(&card->napi);
>  	/* kick-start the NAPI softirq: */
>  	local_bh_enable();


       reply	other threads:[~2025-02-18 15:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250218123639.3271098-1-sashal@kernel.org>
2025-02-18 15:08 ` Alexandra Winter [this message]
2025-02-18 15:19   ` Patch "s390/qeth: move netif_napi_add_tx() and napi_enable() from under BH" has been added to the 6.13-stable tree Greg KH
2025-02-18 15:32     ` Alexandra Winter
2025-02-18 17:09       ` Greg KH

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=b01c840b-55fb-455d-88fa-69848d2dcebf@linux.ibm.com \
    --to=wintera@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=svens@linux.ibm.com \
    --cc=twinkler@linux.ibm.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