From: patchwork-bot+netdevbpf@kernel.org
To: Foster Snowhill <forst@pen.gy>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, gvalkov@gmail.com, horms@kernel.org,
oneukum@suse.com, netdev@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH net v5 0/7] usbnet: ipheth: prevent OoB reads of NDP16
Date: Tue, 28 Jan 2025 11:20:33 +0000 [thread overview]
Message-ID: <173806323350.3759067.5078692360425955195.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250125235409.3106594-1-forst@pen.gy>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 26 Jan 2025 00:54:02 +0100 you wrote:
> iOS devices support two types of tethering over USB: regular, where the
> internet connection is shared from the phone to the attached computer,
> and reverse, where the internet connection is shared from the attached
> computer to the phone.
>
> The `ipheth` driver is responsible for regular tethering only. With this
> tethering type, iOS devices support two encapsulation modes on RX:
> legacy and NCM.
>
> [...]
Here is the summary with links:
- [net,v5,1/7] usbnet: ipheth: fix possible overflow in DPE length check
https://git.kernel.org/netdev/net/c/c219427ed296
- [net,v5,2/7] usbnet: ipheth: check that DPE points past NCM header
https://git.kernel.org/netdev/net/c/429fa68b58ce
- [net,v5,3/7] usbnet: ipheth: use static NDP16 location in URB
https://git.kernel.org/netdev/net/c/86586dcb75cb
- [net,v5,4/7] usbnet: ipheth: refactor NCM datagram loop
https://git.kernel.org/netdev/net/c/2a9a196429e9
- [net,v5,5/7] usbnet: ipheth: break up NCM header size computation
https://git.kernel.org/netdev/net/c/efcbc678a14b
- [net,v5,6/7] usbnet: ipheth: fix DPE OoB read
https://git.kernel.org/netdev/net/c/ee591f2b2817
- [net,v5,7/7] usbnet: ipheth: document scope of NCM implementation
https://git.kernel.org/netdev/net/c/be154b598fa5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-01-28 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 23:54 [PATCH net v5 0/7] usbnet: ipheth: prevent OoB reads of NDP16 Foster Snowhill
2025-01-25 23:54 ` [PATCH net v5 1/7] usbnet: ipheth: fix possible overflow in DPE length check Foster Snowhill
2025-01-25 23:54 ` [PATCH net v5 2/7] usbnet: ipheth: check that DPE points past NCM header Foster Snowhill
2025-01-25 23:54 ` [PATCH net v5 3/7] usbnet: ipheth: use static NDP16 location in URB Foster Snowhill
2025-01-25 23:54 ` [PATCH net v5 4/7] usbnet: ipheth: refactor NCM datagram loop Foster Snowhill
2025-01-25 23:54 ` [PATCH net v5 5/7] usbnet: ipheth: break up NCM header size computation Foster Snowhill
2025-01-25 23:54 ` [PATCH net v5 6/7] usbnet: ipheth: fix DPE OoB read Foster Snowhill
2025-01-25 23:54 ` [PATCH net v5 7/7] usbnet: ipheth: document scope of NCM implementation Foster Snowhill
2025-01-26 11:19 ` [PATCH net v5 0/7] usbnet: ipheth: prevent OoB reads of NDP16 Bjørn Mork
2025-01-26 13:44 ` Foster Snowhill
2025-01-28 11:20 ` patchwork-bot+netdevbpf [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=173806323350.3759067.5078692360425955195.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=forst@pen.gy \
--cc=gvalkov@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=pabeni@redhat.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