netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mohammad heib <mheib@redhat.com>
To: Paolo Abeni <pabeni@redhat.com>,
	intel-wired-lan@lists.osuosl.org, anthony.l.nguyen@intel.com
Cc: przemyslaw.kitszel@intel.com, davem@davemloft.net,
	aduyck@mirantis.com, kuba@kernel.org, netdev@vger.kernel.org,
	jacob.e.keller@intel.com,
	Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net v2 1/2] i40e: drop udp_tunnel_get_rx_info() call from i40e_open()
Date: Sun, 28 Dec 2025 21:44:42 +0200	[thread overview]
Message-ID: <ba98c377-395c-456f-afb4-c0cb50f504cf@redhat.com> (raw)
In-Reply-To: <e8aa1cf8-f42e-4329-8bd8-0f2c3fedde55@redhat.com>

HI Paolo,
Thank you for the review.

On 12/28/25 11:29 AM, Paolo Abeni wrote:
> On 12/18/25 1:13 PM, mheib@redhat.com wrote:
>> From: Mohammad Heib <mheib@redhat.com>
>>
>> The i40e driver calls udp_tunnel_get_rx_info() during i40e_open().
>> This is redundant because UDP tunnel RX offload state is preserved
>> across device down/up cycles. The udp_tunnel core handles
>> synchronization automatically when required.
>>
>> Furthermore, recent changes in the udp_tunnel infrastructure require
>> querying RX info while holding the udp_tunnel lock. Calling it
>> directly from the ndo_open path violates this requirement,
>> triggering the following lockdep warning:
>>
>>    Call Trace:
>>     <TASK>
>>     ? __udp_tunnel_nic_assert_locked+0x39/0x40 [udp_tunnel]
>>     i40e_open+0x135/0x14f [i40e]
>>     __dev_open+0x121/0x2e0
>>     __dev_change_flags+0x227/0x270
>>     dev_change_flags+0x3d/0xb0
>>     devinet_ioctl+0x56f/0x860
>>     sock_do_ioctl+0x7b/0x130
>>     __x64_sys_ioctl+0x91/0xd0
>>     do_syscall_64+0x90/0x170
>>     ...
>>     </TASK>
>>
>> Remove the redundant and unsafe call to udp_tunnel_get_rx_info() from
>> i40e_open() resolve the locking violation.
>>
>> Fixes: 06a5f7f167c5 ("i40e: Move all UDP port notifiers to single function")
>> Signed-off-by: Mohammad Heib <mheib@redhat.com>
>> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
> 
> @Tony: I assume you prefer to take this series into your tree first.
> 
> @Mohammad: I think we don't need to packport this path in old kernels; I
> guess a better fixes tag should point to the recent udp_tunnel
> infrastructure changes.

indeed we don't need this change in the old versions.
I updated the fixes tag to:
   - Fixes: 1ead7501094c ("udp_tunnel: remove rtnl_lock dependency").
This better reflects the change that exposed the problem, even though 
the fix itself is in the driver.


> 
> Thanks,
> 
> Paolo
> 
Thanks,


      reply	other threads:[~2025-12-28 19:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18 12:13 [PATCH net v2 1/2] i40e: drop udp_tunnel_get_rx_info() call from i40e_open() mheib
2025-12-18 12:13 ` [PATCH net v2 2/2] ice: drop udp_tunnel_get_rx_info() call from ndo_open() mheib
2025-12-18 12:42 ` [Intel-wired-lan] [PATCH net v2 1/2] i40e: drop udp_tunnel_get_rx_info() call from i40e_open() Paul Menzel
2025-12-28  9:29 ` Paolo Abeni
2025-12-28 19:44   ` mohammad heib [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=ba98c377-395c-456f-afb4-c0cb50f504cf@redhat.com \
    --to=mheib@redhat.com \
    --cc=aduyck@mirantis.com \
    --cc=aleksandr.loktionov@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jacob.e.keller@intel.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.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;
as well as URLs for NNTP newsgroup(s).