netdev - Re: [PATCH] qmi_wwan: Do not call netif_rx from rx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <162378180344.31286.3200730023491803021.git-patchwork-notify@kernel.org>
Date:   Tue, 15 Jun 2021 18:30:03 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Kristian Evensen <kristian.evensen@...il.com>
Cc:     netdev@...r.kernel.org, bjorn@...k.no
Subject: Re: [PATCH] qmi_wwan: Do not call netif_rx from rx_fixup

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Tue, 15 Jun 2021 12:01:51 +0200 you wrote:
> When the QMI_WWAN_FLAG_PASS_THROUGH is set, netif_rx() is called from
> qmi_wwan_rx_fixup(). When the call to netif_rx() is successful (which is
> most of the time), usbnet_skb_return() is called (from rx_process()).
> usbnet_skb_return() will then call netif_rx() a second time for the same
> skb.
> 
> Simplify the code and avoid the redundant netif_rx() call by changing
> qmi_wwan_rx_fixup() to always return 1 when QMI_WWAN_FLAG_PASS_THROUGH
> is set. We then leave it up to the existing infrastructure to call
> netif_rx().
> 
> [...]

Here is the summary with links:
  - qmi_wwan: Do not call netif_rx from rx_fixup
    https://git.kernel.org/netdev/net/c/057d49334c02

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html