mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: xiaolei wang <xiaolei.wang@windriver.com>
To: Paolo Abeni <pabeni@redhat.com>,
	nicolas.ferre@microchip.com, claudiu.beznea@tuxon.dev,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, rmk+kernel@armlinux.org.uk,
	Kexin.Hao@windriver.com
Cc: netdev@vger.kernel.org, stable@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: macb: Relocate mog_init_rings() callback from macb_mac_link_up() to macb_open()
Date: Fri, 19 Dec 2025 17:16:49 +0800	[thread overview]
Message-ID: <d13b87c6-6d53-4a71-9b61-a69e62d555e4@windriver.com> (raw)
In-Reply-To: <f73dcdc2-a63f-44e9-9c3e-c1c6340d099f@redhat.com>


On 12/18/25 20:14, Paolo Abeni wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On 12/9/25 9:52 AM, Xiaolei Wang wrote:
>> In the non-RT kernel, local_bh_disable() merely disables preemption,
>> whereas it maps to an actual spin lock in the RT kernel. Consequently,
>> when attempting to refill RX buffers via netdev_alloc_skb() in
>> macb_mac_link_up(), a deadlock scenario arises as follows:
>>    Chain caused by macb_mac_link_up():
>>     &bp->lock --> (softirq_ctrl.lock)
>>
>>     Chain caused by macb_start_xmit():
>>     (softirq_ctrl.lock) --> _xmit_ETHER#2 --> &bp->lock
> Including the whole lockdep splat instead of the above would be clearer;
> in fact, I had to fetch the relevant info from there.
OK, I will add all the logs.
>
>> Notably, invoking the mog_init_rings() callback upon link establishment
>> is unnecessary. Instead, we can exclusively call mog_init_rings() within
>> the ndo_open() callback. This adjustment resolves the deadlock issue.
>> Given that mog_init_rings() is only applicable to
>> non-MACB_CAPS_MACB_IS_EMAC cases, we can simply move it to macb_open()
>> and simultaneously eliminate the MACB_CAPS_MACB_IS_EMAC check.
> This part is not clear to me: AFAICS the new code now does such init
> step unconditionally, which looks confusing. I think such step should
> still be under the relevant conditional (or you need to include a
> better/more verbose explanation describing why such check is not really
> needed).

I noticed that the initialization function in 'emac_config' is 
'at91ether_init()',

and 'netdev_ops' is 'at91ether_netdev_ops'. It doesn't use 'macb_open()',

so after moving 'mog_init_rings()' to 'macb_open', we no longer need to 
add this check.

>
>> Fixes: 633e98a711ac ("net: macb: use resolved link config in mac_link_up()")
>> Cc: stable@vger.kernel.org
>> Suggested-by: Kevin Hao <kexin.hao@windriver.com>
>> Signed-off-by: Xiaolei Wang <xiaolei.wang@windriver.com>
> Side note: you still need to include the 'net' tag into the subj prefix.

OK, I will add "net" to the subject in the next version.

thanks

xiaolei

>
> /P
>

      reply	other threads:[~2025-12-19  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-09  8:52 Xiaolei Wang
2025-12-18 12:14 ` Paolo Abeni
2025-12-19  9:16   ` xiaolei wang [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=d13b87c6-6d53-4a71-9b61-a69e62d555e4@windriver.com \
    --to=xiaolei.wang@windriver.com \
    --cc=Kexin.Hao@windriver.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=pabeni@redhat.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=stable@vger.kernel.org \
    /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®