* Re: linux-next: manual merge of the net-next tree with the netfilter tree
From: Andrea Mayer @ 2026-04-09 1:04 UTC (permalink / raw)
To: Mark Brown, Matthieu Baerts
Cc: David Miller, Jakub Kicinski, Paolo Abeni, Networking,
Justin Iurman, Linux Kernel Mailing List, Linux Next Mailing List,
Andrea Mayer
In-Reply-To: <d9d4e328-6668-4c24-bace-77a0f93bbed6@sirena.org.uk>
On Wed, 8 Apr 2026 18:00:50 +0100
Mark Brown <broonie@kernel.org> wrote:
> On Wed, Apr 08, 2026 at 06:43:36PM +0200, Matthieu Baerts wrote:
> > On 08/04/2026 17:08, Mark Brown wrote:
>
> > > This also needs a fixup for a new jump to the error handling paths that
> > > was added in seg6_build_state().
>
> > I also had this other conflict there, and I did this when resolving it
> > in MPTCP tree:
>
> > + if (tb[SEG6_IPTUNNEL_SRC]) {
> > + slwt->tunsrc = nla_get_in6_addr(tb[SEG6_IPTUNNEL_SRC]);
> > +
> > + if (ipv6_addr_any(&slwt->tunsrc) ||
> > + ipv6_addr_is_multicast(&slwt->tunsrc) ||
> > + ipv6_addr_loopback(&slwt->tunsrc)) {
> > + NL_SET_ERR_MSG(extack, "invalid tunsrc address");
> > + err = -EINVAL;
> > - goto free_dst_cache;
> > ++ goto err_destroy_output;
> > + }
> > + }
> > +
>
> Yes, that's the additional fixup I mentioned above - it didn't conflict
> for me (well, the exit path did).
Thanks Mark and Matthieu for taking care of this.
I went through both commits and the rerere.
The resolution looks correct from the seg6 side. Build-tested.
Happy to help if anything else comes up.
Cheers,
Andrea
^ permalink raw reply
* Re: [PATCH net-next v3 3/3] gve: implement PTP gettimex64
From: Jordan Rhee @ 2026-04-09 1:08 UTC (permalink / raw)
To: Jacob Keller
Cc: Jakub Kicinski, Harshitha Ramamurthy, netdev, joshwash,
andrew+netdev, davem, edumazet, pabeni, richardcochran, willemb,
nktgrg, jfraker, ziweixiao, maolson, thostet, jefrogers,
alok.a.tiwari, yyd, linux-kernel, Naman Gulati
In-Reply-To: <093a5c92-f94c-49d6-96ea-0c76ff18f9e1@intel.com>
On Wed, Apr 8, 2026 at 3:43 PM Jacob Keller <jacob.e.keller@intel.com> wrote:
>
> On 4/6/2026 1:41 PM, Jordan Rhee wrote:
> > On Fri, Apr 3, 2026 at 2:18 PM Jacob Keller <jacob.e.keller@intel.com> wrote:
> >>
> >> On 4/3/2026 12:44 PM, Harshitha Ramamurthy wrote:
> >>> From: Jordan Rhee <jordanrhee@google.com>
> >>>
> >>> Enable chrony and phc2sys to synchronize system clock to NIC clock.
> >>>
> >>> The system cycle counters are sampled by the device to minimize the
> >>> uncertainty window. If the system times are sampled in the host, the
> >>> delta between pre and post readings is 100us or more due to AQ command
> >>> latency. The system times returned by the device have a delta of ~1us,
> >>> which enables significantly more accurate clock synchronization.
> >>>
> >>> Reviewed-by: Willem de Bruijn <willemb@google.com>
> >>> Reviewed-by: Kevin Yang <yyd@google.com>
> >>> Reviewed-by: Naman Gulati <namangulati@google.com>
> >>> Signed-off-by: Jordan Rhee <jordanrhee@google.com>
> >>> Signed-off-by: Harshitha Ramamurthy <hramamurthy@google.com>
> >>> ---
> >>
> >>> +/*
> >>> + * Convert a raw cycle count (e.g. from get_cycles()) to the system clock
> >>> + * type specified by clockid. The system_time_snapshot must be taken before
> >>> + * the cycle counter is sampled.
> >>> + */
> >>> +static int gve_cycles_to_timespec64(struct gve_priv *priv, clockid_t clockid,
> >>> + struct system_time_snapshot *snap,
> >>> + u64 cycles, struct timespec64 *ts)
> >>> +{
> >>> + struct gve_cycles_to_clock_callback_ctx ctx = {0};
> >>> + struct system_device_crosststamp xtstamp;
> >>> + int err;
> >>> +
> >>> + ctx.cycles = cycles;
> >>> + err = get_device_system_crosststamp(gve_cycles_to_clock_fn, &ctx, snap,
> >>> + &xtstamp);
> >>> + if (err) {
> >>> + dev_err_ratelimited(&priv->pdev->dev,
> >>> + "get_device_system_crosststamp() failed to convert %lld cycles to system time: %d\n",
> >>> + cycles,
> >>> + err);
> >>> + return err;
> >>> + }
> >>> +
> >>
> >> This looks a lot like a cross timestamp (i.e. something like PCIe PTM)
> >> Why not just implement the .crosstimestamp and PTP_SYS_OFF_PRECISE? Does
> >> that not work properly? Or is this not really a cross timestamp despite
> >> use of the get_device_system_crosststamp handler? :D
> >
> > .crosstimestamp is for devices that support simultaneous NIC and
> > system timestamps. Devices that don't support simultaneous timestamps
> > have to take a system time sandwich by calling
> > ptp_read_system_prets()/ptp_read_system_postts() on either side of the
> > NIC timestamp. Upper layers (e.g. chrony) use the sandwich delta in
> > nontrivial ways when estimating the system clock / NIC clock offset.
> > This is information that must be preserved, and it would be incorrect
> > to implement .crosstimestamp by returning the midpoint of the
> > sandwich, as tempting as that implementation might be.
> >
>
> True.
>
> > Gvnic does not support simultaneous NIC and system timestamps, so it
> > must use the sandwich technique. Since the NIC timestamp is obtained
> > using a firmware (hypervisor) call, the uncertainty window would be
> > too large if it were taken inside the VM. Gvnic takes the sandwich in
> > the hypervisor and returns the raw TSC values to the VM.
> > get_device_system_crosststamp() is used to convert the TSCs to system
> > times, which I believe is the only correct way to do this conversion.
> > Jordan
> >
>
> Hmm. The function says:
>
> "Synchronously capture system/device timestamp". That is what confuses
> me. Your implementation uses gve_cycles_to_clock_fn() which just sets
> some values in the system_counterval struct and exits. It doesn't
> "capture a system/device timestamp" tuple.
>
> This does feel a bit weird. No other caller appears to exist outside of
> the cross timestamp implementations.
>
> It sounds like what you want is a function that takes a cycles count
> value and does the conversion from TSC to the appropriate clock, along
> with all of the interopolation etc. What you've done is sort of a cludge
> around get_device_system_crosststamp() to force it to do that for you
> without actually using it as intended.
>
> I'd argue it would be better to have a cycles_to_ktime() or something
> which takes the TSC cycles value and the appropriate clock and does the
> exact same flow as get_device_system_crosststamp() for converting the
> cycles into proper ktime values without the mess of the callback
> function etc.
Yes, that's exactly how I'm using get_device_system_crosststamp().
There is no cycles_to_ktime() function, and adding one would make this
patch more difficult to backport to older kernels.
There is precedent for using get_device_system_crosststamp() this way
in the virtio_rtc driver. In viortc_ptp_getcrosststamp(), the
timestamp is sampled before calling get_device_system_crosststamp(),
and the callback simply populates the return values from the context.
I believe the snapshot parameter was added to support this use case.
>
> I guess in principle what you've implemented is "correct" and
> functional, but it definitely feels a bit weird to use the API in this
> way. It smells like a neat hack instead of a proper interface for this
> purpose.
>
> That said, I won't object strongly if the maintainers are fine with
> using it for this purpose.
>
> Thanks,
> Jake
^ permalink raw reply
* [PATCH] ax25: fix OOB read after address header strip in ax25_rcv().
From: Ashutosh Desai @ 2026-04-09 1:22 UTC (permalink / raw)
To: netdev
Cc: linux-hams, jreuter, davem, edumazet, kuba, pabeni, horms,
linux-kernel, Ashutosh Desai
ax25_rcv() calls skb_pull(skb, ax25_addr_size(&dp)) to strip the
address header, then immediately reads skb->data[0] and skb->data[1]
without verifying the buffer still contains at least 2 bytes.
A crafted 15-byte KISS frame (1 KISS byte + 14 address bytes with
EBIT set in the source address, no control/PID bytes) passes
ax25_addr_parse() which only requires len >= 14, and passes the KISS
byte check (low nibble == 0). After skb_pull(1) in ax25_kiss_rcv()
and skb_pull(14) in ax25_rcv(), skb->len is 0 and the subsequent
reads of skb->data[0] (control byte) and skb->data[1] (PID byte)
are out of bounds.
Add a check that at least 2 bytes remain after stripping the address
header, freeing the skb and returning on malformed input.
Signed-off-by: Ashutosh Desai <ashutoshdesai993@gmail.com>
---
net/ax25/ax25_in.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/net/ax25/ax25_in.c b/net/ax25/ax25_in.c
index d75b3e9ed..92baac77f 100644
--- a/net/ax25/ax25_in.c
+++ b/net/ax25/ax25_in.c
@@ -217,6 +217,11 @@ static int ax25_rcv(struct sk_buff *skb, struct net_device *dev,
*/
skb_pull(skb, ax25_addr_size(&dp));
+ if (skb->len < 2) {
+ kfree_skb(skb);
+ return 0;
+ }
+
/* For our port addresses ? */
if (ax25cmp(&dest, dev_addr) == 0 && dp.lastrepeat + 1 == dp.ndigi)
mine = 1;
--
2.34.1
^ permalink raw reply related
* [PATCH] rose: fix OOB read on short CLEAR REQUEST frames.
From: Ashutosh Desai @ 2026-04-09 1:32 UTC (permalink / raw)
To: netdev
Cc: linux-hams, davem, edumazet, kuba, pabeni, horms, linux-kernel,
Ashutosh Desai
rose_process_rx_frame() dispatches to state machines after calling
rose_decode(), but does not verify the frame is long enough before
doing so. All five state machine handlers read skb->data[3] and
skb->data[4] (cause and diagnostic bytes) when handling a
ROSE_CLEAR_REQUEST frame, yet the only upstream length check is
ROSE_MIN_LEN (3 bytes) in rose_route_frame().
A crafted 3-byte ROSE CLEAR REQUEST frame (bytes: GFI/LCI-high,
LCI-low, 0x13) passes the minimum length gate and reaches the state
machines, where skb->data[3] and skb->data[4] are read one and two
bytes past the valid buffer respectively.
Add a check in rose_process_rx_frame() that drops any CLEAR REQUEST
frame shorter than 5 bytes (3-byte header + cause + diagnostic),
covering all five state machines with a single guard.
Signed-off-by: Ashutosh Desai <ashutoshdesai993@gmail.com>
---
net/rose/rose_in.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/net/rose/rose_in.c b/net/rose/rose_in.c
index 0276b393f..1ac9a6aee 100644
--- a/net/rose/rose_in.c
+++ b/net/rose/rose_in.c
@@ -271,6 +271,11 @@ int rose_process_rx_frame(struct sock *sk, struct sk_buff *skb)
frametype = rose_decode(skb, &ns, &nr, &q, &d, &m);
+ if (frametype == ROSE_CLEAR_REQUEST && skb->len < 5) {
+ kfree_skb(skb);
+ return 0;
+ }
+
switch (rose->state) {
case ROSE_STATE_1:
queued = rose_state1_machine(sk, skb, frametype);
--
2.34.1
^ permalink raw reply related
* Re: [PATCH net-next v6 00/10] Decouple receive and transmit enablement in team driver
From: Kuniyuki Iwashima @ 2026-04-09 1:48 UTC (permalink / raw)
To: marcharvey
Cc: andrew+netdev, davem, edumazet, horms, jiri, kuba, linux-kernel,
linux-kselftest, netdev, pabeni, shuah
In-Reply-To: <CANkEMgk16j2xzQ85JGQ4OWqeiwiVO5Gy-UfkN3omKkKizpLxiQ@mail.gmail.com>
From: Marc Harvey <marcharvey@google.com>
Date: Wed, 8 Apr 2026 17:10:05 -0700
> On Wed, Apr 8, 2026 at 9:40 AM Jakub Kicinski <kuba@kernel.org> wrote:
> >
> > It pains me to report on non-debug kernels:
>
> I'm sorry to have pained you. Despite my best efforts to run with the
> exact same environment and conditions as your CI, my teamd can be
> killed with "teamd -k" but yours hangs (both are version 1.32 on
> Fedora with the same kernel config).
Considering the subsequent "kill" works on the dbg instance (thanks
to 2400s timeout), I guess teamd is somehow stuck at SIGTERM handling
removing team devices in teamd_port_remove_all(). (SIGTERM being masked
sounds unlikely)
https://netdev-ctrl.bots.linux.dev/logs/vmksft/bonding-dbg/results/593802/4-teamd-activebackup-sh/stdout
https://netdev-ctrl.bots.linux.dev/logs/vmksft/bonding-dbg/results/593802/4-teamd-activebackup-sh/stderr
---8<---
[ 759.819815][T21724] test_team1: Port device eth1 removed
[ 759.822323][T21724] test_team1: Port device eth0 removed
[ 790.615687][T21728] test_team2: Port device eth1 removed
[ 790.617445][T21728] test_team2: Port device eth0 removed
---8<---
Adding -N and letting "ip netns del" release the last netns refcnt
and defer device destruction to cleanup_net() may help.
> For v7, I’ll invoke "teamd -k"
> using the timeout utility, or just increase the test timeout.
+1 for the latter, maybe set timeout=300.
daemon_pid_file_kill_wait(SIGTERM, 30) * 2 = 120s, but just in case.
See these files for howto:
$ find tools/testing/selftests/net/ -name settings
^ permalink raw reply
* Re: [PATCH net v5 00/21] rxrpc: Miscellaneous fixes
From: patchwork-bot+netdevbpf @ 2026-04-09 1:50 UTC (permalink / raw)
To: David Howells
Cc: netdev, marc.dionne, kuba, davem, edumazet, pabeni, linux-afs,
linux-kernel
In-Reply-To: <20260408121252.2249051-1-dhowells@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 8 Apr 2026 13:12:28 +0100 you wrote:
> Here are some fixes for rxrpc:
>
> (1) Fix key quota calculation.
>
> (2) Fix a memory leak.
>
> (3) Fix rxrpc_new_client_call_for_sendmsg() to substitute NULL for an
> empty key.
>
> [...]
Here is the summary with links:
- [net,v5,01/21] rxrpc: Fix key quota calculation for multitoken keys
https://git.kernel.org/netdev/net/c/bdbfead6d389
- [net,v5,02/21] rxrpc: Fix key parsing memleak
https://git.kernel.org/netdev/net/c/b555912b9b21
- [net,v5,03/21] rxrpc: Fix anonymous key handling
https://git.kernel.org/netdev/net/c/6a59d84b4fc2
- [net,v5,04/21] rxrpc: Fix call removal to use RCU safe deletion
https://git.kernel.org/netdev/net/c/146d4ab94cf1
- [net,v5,05/21] rxrpc: Fix RxGK token loading to check bounds
https://git.kernel.org/netdev/net/c/d179a868dd75
- [net,v5,06/21] rxrpc: Fix use of wrong skb when comparing queued RESP challenge serial
https://git.kernel.org/netdev/net/c/b33f5741bb18
- [net,v5,07/21] rxrpc: Fix rack timer warning to report unexpected mode
https://git.kernel.org/netdev/net/c/65b3ffe0972e
- [net,v5,08/21] rxrpc: Fix key reference count leak from call->key
https://git.kernel.org/netdev/net/c/d666540d217e
- [net,v5,09/21] rxrpc: Fix to request an ack if window is limited
https://git.kernel.org/netdev/net/c/0cd3e3f3f2ec
- [net,v5,10/21] rxrpc: Only put the call ref if one was acquired
https://git.kernel.org/netdev/net/c/6331f1b24a3e
- [net,v5,11/21] rxrpc: reject undecryptable rxkad response tickets
https://git.kernel.org/netdev/net/c/fe4447cd9562
- [net,v5,12/21] rxrpc: fix RESPONSE authenticator parser OOB read
https://git.kernel.org/netdev/net/c/3e3138007887
- [net,v5,13/21] rxrpc: fix oversized RESPONSE authenticator length check
https://git.kernel.org/netdev/net/c/a2567217ade9
- [net,v5,14/21] rxrpc: fix reference count leak in rxrpc_server_keyring()
https://git.kernel.org/netdev/net/c/f125846ee79f
- [net,v5,15/21] rxrpc: Fix key/keyring checks in setsockopt(RXRPC_SECURITY_KEY/KEYRING)
https://git.kernel.org/netdev/net/c/2afd86ccbb20
- [net,v5,16/21] rxrpc: Fix missing error checks for rxkad encryption/decryption failure
https://git.kernel.org/netdev/net/c/f93af41b9f5f
- [net,v5,17/21] rxrpc: Fix integer overflow in rxgk_verify_response()
https://git.kernel.org/netdev/net/c/699e52180f42
- [net,v5,18/21] rxrpc: Fix leak of rxgk context in rxgk_verify_response()
https://git.kernel.org/netdev/net/c/7e1876caa836
- [net,v5,19/21] rxrpc: Fix buffer overread in rxgk_do_verify_authenticator()
https://git.kernel.org/netdev/net/c/f564af387c8c
- [net,v5,20/21] rxrpc: only handle RESPONSE during service challenge
https://git.kernel.org/netdev/net/c/c43ffdcfdbb5
- [net,v5,21/21] rxrpc: proc: size address buffers for %pISpc output
https://git.kernel.org/netdev/net/c/a44ce6aa2efb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: [PATCH net 1/7] ipvs: fix NULL deref in ip_vs_add_service error path
From: patchwork-bot+netdevbpf @ 2026-04-09 1:50 UTC (permalink / raw)
To: Florian Westphal
Cc: netdev, pabeni, davem, edumazet, kuba, netfilter-devel, pablo
In-Reply-To: <20260408163512.30537-2-fw@strlen.de>
Hello:
This series was applied to netdev/net.git (main)
by Florian Westphal <fw@strlen.de>:
On Wed, 8 Apr 2026 18:35:06 +0200 you wrote:
> From: Weiming Shi <bestswngs@gmail.com>
>
> When ip_vs_bind_scheduler() succeeds in ip_vs_add_service(), the local
> variable sched is set to NULL. If ip_vs_start_estimator() subsequently
> fails, the out_err cleanup calls ip_vs_unbind_scheduler(svc, sched)
> with sched == NULL. ip_vs_unbind_scheduler() passes the cur_sched NULL
> check (because svc->scheduler was set by the successful bind) but then
> dereferences the NULL sched parameter at sched->done_service, causing a
> kernel panic at offset 0x30 from NULL.
>
> [...]
Here is the summary with links:
- [net,1/7] ipvs: fix NULL deref in ip_vs_add_service error path
https://git.kernel.org/netdev/net/c/9a91797e61d2
- [net,2/7] netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator
https://git.kernel.org/netdev/net/c/1f3083aec883
- [net,3/7] netfilter: xt_multiport: validate range encoding in checkentry
https://git.kernel.org/netdev/net/c/ff64c5bfef12
- [net,4/7] netfilter: ip6t_eui64: reject invalid MAC header for all packets
https://git.kernel.org/netdev/net/c/fdce0b3590f7
- [net,5/7] netfilter: nft_ct: fix use-after-free in timeout object destroy
https://git.kernel.org/netdev/net/c/f8dca15a1b19
- [net,6/7] netfilter: nfnetlink_queue: make hash table per queue
https://git.kernel.org/netdev/net/c/936206e3f6ff
- [net,7/7] selftests: nft_queue.sh: add a parallel stress test
https://git.kernel.org/netdev/net/c/dde1a6084c5c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: [PATCH] net: mdio: realtek-rtl9300: use scoped device_for_each_child_node loop
From: patchwork-bot+netdevbpf @ 2026-04-09 1:50 UTC (permalink / raw)
To: Felix Gu
Cc: andrew, hkallweit1, linux, davem, edumazet, kuba, pabeni,
chris.packham, netdev, linux-kernel
In-Reply-To: <20260405-rtl9300-v1-1-08e4499cf944@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 05 Apr 2026 14:51:52 +0800 you wrote:
> Switch to device_for_each_child_node_scoped() to auto-release fwnode
> references on early exit.
>
> Fixes: 24e31e474769 ("net: mdio: Add RTL9300 MDIO driver")
> Signed-off-by: Felix Gu <ustc.gu@gmail.com>
> ---
> drivers/net/mdio/mdio-realtek-rtl9300.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> [...]
Here is the summary with links:
- net: mdio: realtek-rtl9300: use scoped device_for_each_child_node loop
https://git.kernel.org/netdev/net/c/c09ea768bdb9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: [PATCH 1/8] xfrm: clear trailing padding in build_polexpire()
From: patchwork-bot+netdevbpf @ 2026-04-09 2:00 UTC (permalink / raw)
To: Steffen Klassert; +Cc: davem, kuba, herbert, netdev
In-Reply-To: <20260408095925.253681-2-steffen.klassert@secunet.com>
Hello:
This series was applied to netdev/net.git (main)
by Steffen Klassert <steffen.klassert@secunet.com>:
On Wed, 8 Apr 2026 11:58:57 +0200 you wrote:
> From: Yasuaki Torimaru <yasuakitorimaru@gmail.com>
>
> build_expire() clears the trailing padding bytes of struct
> xfrm_user_expire after setting the hard field via memset_after(),
> but the analogous function build_polexpire() does not do this for
> struct xfrm_user_polexpire.
>
> [...]
Here is the summary with links:
- [1/8] xfrm: clear trailing padding in build_polexpire()
https://git.kernel.org/netdev/net/c/71a98248c63c
- [2/8] xfrm: account XFRMA_IF_ID in aevent size calculation
https://git.kernel.org/netdev/net/c/7081d46d3231
- [3/8] xfrm: Wait for RCU readers during policy netns exit
https://git.kernel.org/netdev/net/c/069daad4f2ae
- [4/8] xfrm: hold dev ref until after transport_finish NF_HOOK
https://git.kernel.org/netdev/net/c/1c428b038400
- [5/8] xfrm: fix refcount leak in xfrm_migrate_policy_find
https://git.kernel.org/netdev/net/c/83317cce60a0
- [6/8] xfrm_user: fix info leak in build_mapping()
https://git.kernel.org/netdev/net/c/1beb76b2053b
- [7/8] xfrm_user: fix info leak in build_report()
https://git.kernel.org/netdev/net/c/d10119968d0e
- [8/8] net: af_key: zero aligned sockaddr tail in PF_KEY exports
https://git.kernel.org/netdev/net/c/426c355742f0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: [PATCH net 1/2] batman-adv: reject oversized global TT response buffers
From: patchwork-bot+netdevbpf @ 2026-04-09 2:00 UTC (permalink / raw)
To: Simon Wunderlich
Cc: davem, kuba, netdev, b.a.t.m.a.n, caoruide123, stable, yifanwucs,
tomapufckgml, yuantan098, bird, enjou1224z, n05ec, sven
In-Reply-To: <20260408110255.976389-2-sw@simonwunderlich.de>
Hello:
This series was applied to netdev/net.git (main)
by Simon Wunderlich <sw@simonwunderlich.de>:
On Wed, 8 Apr 2026 13:02:54 +0200 you wrote:
> From: Ruide Cao <caoruide123@gmail.com>
>
> batadv_tt_prepare_tvlv_global_data() builds the allocation length for a
> global TT response in 16-bit temporaries. When a remote originator
> advertises a large enough global TT, the TT payload length plus the VLAN
> header offset can exceed 65535 and wrap before kmalloc().
>
> [...]
Here is the summary with links:
- [net,1/2] batman-adv: reject oversized global TT response buffers
https://git.kernel.org/netdev/net/c/3a359bf5c61d
- [net,2/2] batman-adv: hold claim backbone gateways by reference
https://git.kernel.org/netdev/net/c/82d8701b2c93
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: [GIT PULL] wireless-2026-04-08
From: patchwork-bot+netdevbpf @ 2026-04-09 2:00 UTC (permalink / raw)
To: Johannes Berg; +Cc: netdev, linux-wireless
In-Reply-To: <20260408081802.111623-3-johannes@sipsolutions.net>
Hello:
This pull request was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 8 Apr 2026 10:15:25 +0200 you wrote:
> Hi,
>
> So in a way I'd hoped it wouldn't come to this, but while I
> was out last week a couple of things came in that seemed
> relevant enough to squeeze in now. I guess it wouldn't be
> much of an issue if not, but I figured I'd try anyway :)
>
> [...]
Here is the summary with links:
- [GIT,PULL] wireless-2026-04-08
https://git.kernel.org/netdev/net/c/d65b175cfac6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: [PATCH 1/2] xfrm: update outdated comment
From: patchwork-bot+netdevbpf @ 2026-04-09 2:00 UTC (permalink / raw)
To: Steffen Klassert; +Cc: davem, kuba, herbert, netdev
In-Reply-To: <20260408094258.148555-2-steffen.klassert@secunet.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Steffen Klassert <steffen.klassert@secunet.com>:
On Wed, 8 Apr 2026 11:42:40 +0200 you wrote:
> From: kexinsun <kexinsun@smail.nju.edu.cn>
>
> The function __xfrm4_bundle_create() was refactored into
> xfrm_bundle_create() (among others) by commit 25ee3286dcbc
> ("xfrm: Merge common code into xfrm_bundle_create"). The
> responsibility for setting dst->obsolete to DST_OBSOLETE_FORCE_CHK
> now lives in xfrm_bundle_create(). Update the comment accordingly.
>
> [...]
Here is the summary with links:
- [1/2] xfrm: update outdated comment
https://git.kernel.org/netdev/net-next/c/be14d13625c9
- [2/2] xfrm: Drop support for HMAC-RIPEMD-160
https://git.kernel.org/netdev/net-next/c/05d42dc8ab92
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: (subset) [PATCH 0/7] clk: qcom: add support for the clock controllers on Nord platforms
From: Bjorn Andersson @ 2026-04-09 2:07 UTC (permalink / raw)
To: Michael Turquette, Stephen Boyd, Rob Herring, Krzysztof Kozlowski,
Conor Dooley, Taniya Das, Taniya Das, Richard Cochran, Shawn Guo,
Deepti Jaggi, Bartosz Golaszewski
Cc: linux-arm-msm, linux-clk, devicetree, linux-kernel, netdev,
Prasanna Tolety
In-Reply-To: <20260403-nord-clks-v1-0-018af14979fd@oss.qualcomm.com>
On Fri, 03 Apr 2026 16:10:48 +0200, Bartosz Golaszewski wrote:
> This documents the gcc, tcsr and rpmhcc support in Nord platforms and
> adds corresponding drivers as well as enables them in arm64 defconfig.
>
>
Applied, thanks!
[1/7] dt-bindings: clock: qcom: Document the Nord SoC TCSR Clock Controller
commit: 31fcf6995e74117fe235a7a07a6e13077070b4a2
[2/7] dt-bindings: clock: qcom-rpmhcc: Add support for Nord SoCs
commit: 8a108047245780ca17667b05a7af600d118ec1d6
[3/7] dt-bindings: clock: qcom: Add Nord Global Clock Controller
commit: 06498d59bb4e10032b1495762a999d640fe4a8dc
[4/7] clk: qcom: Add TCSR clock driver for Nord SoC
commit: 9d13c7bbee5f789738a645df5868b69da5ae3879
[5/7] clk: qcom: rpmh: Add support for Nord rpmh clocks
commit: cf6e6ac63c62cb9f60f981dbaebe591bdbee2f46
[6/7] clk: qcom: gcc: Add multiple global clock controller driver for Nord SoC
commit: a4f780cd5c7aa8c0d2d044ffd153f7a3a13ca81e
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
^ permalink raw reply
* Re: [PATCH net-next] docs: netdev: improve wording of reviewer guidance
From: patchwork-bot+netdevbpf @ 2026-04-09 2:10 UTC (permalink / raw)
To: Jakub Kicinski
Cc: davem, netdev, edumazet, pabeni, andrew+netdev, horms, corbet,
skhan, workflows, linux-doc
In-Reply-To: <20260406175334.3153451-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 6 Apr 2026 10:53:34 -0700 you wrote:
> Reword the reviewer guidance based on behavior we see on the list.
> Steer folks:
> - towards sending tags
> - away from process issues.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
> [...]
Here is the summary with links:
- [net-next] docs: netdev: improve wording of reviewer guidance
https://git.kernel.org/netdev/net-next/c/bd5c24e4001d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: [GIT PULL v2 net-next] netfilter: updates for net-next
From: patchwork-bot+netdevbpf @ 2026-04-09 2:10 UTC (permalink / raw)
To: Florian Westphal
Cc: netdev, pabeni, davem, edumazet, kuba, netfilter-devel, pablo
In-Reply-To: <20260408060419.25258-1-fw@strlen.de>
Hello:
This pull request was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 8 Apr 2026 08:04:19 +0200 you wrote:
> No changes since v1, I only dropped the last patch (13/13). This is also
> why I am not resending the individual patches again.
>
> The following PR contains Netfilter updates for *net-next*:
>
> 1) Fix ancient sparse warnings in nf conntrack nat modules, from
> Sun Jian.
> 2) Fix typo in enum description, from Jelle van der Waa.
> 3) remove redundant refetch of netns pointer in nf_conntrack_sip.
> 4) add a deprecation warning for dccp match.
> We can extend the deadline later if needed, but plan atm is to
> remove the feature.
> 5) remove nf_conntrack_h323 debug code that can read out-of-bounds
> with malformed messages. This code was commented out, but better
> remove this.
> 6+7) add more netlink policy validations in netfilter.
> This could theoretically cause issues when a client sends e.g.
> unsupported feature flags that were previously ignored, so we
> may have to relax some changes. For now, try to be stricter and
> reject upfront.
> 8+9) minor code cleanup in nft_set_pipapo (an nftables set backend).
> 10) Add nftables matching support fro double-tagged vlan and pppoe
> frames, from Pablo Neira Ayuso.
> 11) Fix up indentation of debug messages in nf_conntrack_h323 conntrack
> helper, from David Laight.
> 12) Add a helper to iterate to next flow action and bail out if the
> maximum number of actions is reached, also from Pablo.
>
> [...]
Here is the summary with links:
- [GIT,PULL,v2,net-next] netfilter: updates for net-next
https://git.kernel.org/netdev/net-next/c/1795654f0005
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: [RFC net-next 15/15] Documentation: networking: add ipxlat translator guide
From: Xavier HSINYUAN @ 2026-04-09 2:17 UTC (permalink / raw)
To: Daniel Gröber
Cc: ralf, antonio, corbet, davem, edumazet, horms, kuba, linux-doc,
linux-kernel, netdev, pabeni, skhan
In-Reply-To: <fldksy7obiaonlcxrjcbnfkfmaup27t3fq3ktubd7sx35fsswx@hjmchh6sr7rw>
Hi Daniel,
> Indeed, the JSON is just wrong and --do dev-set is missing. However
> `--family ipxlat` works for me and looking at the code is basically the
> same as specifying --spec.
>
> Could you try this:
>
> $ JSON='{"ifindex": '"$IID"', "config": {"xlat-prefix6": { "prefix": "'$ADDR_HEX'", "prefix-len": 96}}}'
> $ ./tools/net/ynl/pyynl/cli.py --family ipxlat --do dev-set --json "$JSON"
This looks good to me now. `--family ipxlat` is fine with me if this runs
from the source tree.
> I worry once we start with that we're really just re-stating what's already
> extensively documented in the RFCs.
>
> How about a reference to RFC 7915 Appendix A? This has a full bidirectional
> end-to-end example of how translation operates:
> https://datatracker.ietf.org/doc/html/rfc7915#appendix-A
>
> Admittedly using a /96 prefix (which the appendix doesn't) would make it
> easier to grok whats going on. Not sure that's reason enough to get into
> more detailed examples here.
A reference to RFC 7915 Appendix A sounds good to me. Still, a short /96
mapping example would help readers quickly see how the translation works
before reading the full RFC, and would make the following NAT64 section
easier to follow as well.
Best regards,
Xavier
^ permalink raw reply
* Re: [RFC net-next 05/15] ipxlat: add IPv6 packet validation path
From: Xavier HSINYUAN @ 2026-04-09 2:18 UTC (permalink / raw)
To: ralf
Cc: andrew+netdev, antonio, davem, dxld, edumazet, kuba, linux-kernel,
netdev, pabeni
In-Reply-To: <20260319151230.655687-6-ralf@mandelbit.com>
Hi Ralf,
>+static int ipxlat_v6_validate_icmp_csum(const struct sk_buff *skb)
>+{
>+ struct ipv6hdr *iph6;
>+ unsigned int len;
>+ __sum16 csum;
>+
>+ if (skb->ip_summed != CHECKSUM_NONE)
>+ return 0;
>+
>+ iph6 = ipv6_hdr(skb);
>+ len = ipxlat_skb_datagram_len(skb);
>+ csum = csum_ipv6_magic(&iph6->saddr, &iph6->daddr, len, NEXTHDR_ICMP,
>+ skb_checksum(skb, skb_transport_offset(skb), len,
>+ 0));
>+
>+ return unlikely(csum) ? -EINVAL : 0;
>+}
We should include net/ip6_checksum.h to make x86_64 with KMSAN/KASAN and
other architectures with optional _HAVE_ARCH_IPV6_CSUM happy.
Best regards,
Xavier
^ permalink raw reply
* Re: [PATCH] net: txgbe: leave space for null terminators on property_entry
From: patchwork-bot+netdevbpf @ 2026-04-09 2:20 UTC (permalink / raw)
To: Fabio Baltieri
Cc: jiawenwu, mengyuanlou, andrew+netdev, davem, edumazet, kuba,
pabeni, horms, netdev, linux-kernel
In-Reply-To: <20260405222013.5347-1-fabio.baltieri@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 5 Apr 2026 23:20:13 +0100 you wrote:
> Lists of struct property_entry are supposed to be terminated with an
> empty property, this driver currently seems to be allocating exactly the
> amount of entry used.
>
> Change the struct definition to leave an extra element for all
> property_entry.
>
> [...]
Here is the summary with links:
- net: txgbe: leave space for null terminators on property_entry
https://git.kernel.org/netdev/net/c/5a37d228799b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: [PATCH net] net: ioam6: fix OOB and missing lock
From: patchwork-bot+netdevbpf @ 2026-04-09 2:20 UTC (permalink / raw)
To: Justin Iurman; +Cc: netdev, davem, dsahern, edumazet, kuba, pabeni, horms
In-Reply-To: <20260404134137.24553-1-justin.iurman@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 4 Apr 2026 15:41:37 +0200 you wrote:
> When trace->type.bit6 is set:
>
> if (trace->type.bit6) {
> ...
> queue = skb_get_tx_queue(dev, skb);
> qdisc = rcu_dereference(queue->qdisc);
>
> [...]
Here is the summary with links:
- [net] net: ioam6: fix OOB and missing lock
https://git.kernel.org/netdev/net/c/b30b1675aa2b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: [PATCH net-next] net: phy: realtek: get rid of magic numbers in rtl8201_config_intr()
From: patchwork-bot+netdevbpf @ 2026-04-09 2:20 UTC (permalink / raw)
To: Aleksander Jan Bajkowski
Cc: andrew, hkallweit1, linux, davem, edumazet, kuba, pabeni, daniel,
vladimir.oltean, michael, markus.stockhausen, ih, rmk+kernel,
netdev, linux-kernel
In-Reply-To: <20260406201222.1043396-1-olek2@wp.pl>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 6 Apr 2026 22:12:12 +0200 you wrote:
> Replace the magic numbers with defines. Register names were obtained from
> publicly available documentation[1]. This should make it clear what's going
> on in the code.
>
> 1. RTL8201F/RTL8201FL/RTL8201FN Rev. 1.4 Datasheet
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
>
> [...]
Here is the summary with links:
- [net-next] net: phy: realtek: get rid of magic numbers in rtl8201_config_intr()
https://git.kernel.org/netdev/net-next/c/dbc2bb4e8742
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: [PATCH net-next] bonding: remove unused bond_is_first_slave and bond_is_last_slave macros
From: patchwork-bot+netdevbpf @ 2026-04-09 2:20 UTC (permalink / raw)
To: Xiang Mei; +Cc: netdev, jv, andy, davem, edumazet, kuba, pabeni
In-Reply-To: <20260404220412.444753-1-xmei5@asu.edu>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 4 Apr 2026 15:04:12 -0700 you wrote:
> Since commit 2884bf72fb8f ("net: bonding: fix use-after-free in
> bond_xmit_broadcast()"), bond_is_last_slave() was only used in
> bond_xmit_broadcast(). After the recent fix replaced that usage with
> a simple index comparison, bond_is_last_slave() has no remaining
> callers. bond_is_first_slave() likewise has no callers.
>
> Remove both unused macros.
>
> [...]
Here is the summary with links:
- [net-next] bonding: remove unused bond_is_first_slave and bond_is_last_slave macros
https://git.kernel.org/netdev/net-next/c/f81f4e79b192
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: [PATCH net-next 1/4] net: dsa: remove struct platform_data
From: Jakub Kicinski @ 2026-04-09 2:38 UTC (permalink / raw)
To: Vladimir Oltean
Cc: netdev, David S. Miller, Eric Dumazet, Paolo Abeni, Simon Horman,
Andrew Lunn
In-Reply-To: <20260406212158.721806-2-vladimir.oltean@nxp.com>
On Tue, 7 Apr 2026 00:21:55 +0300 Vladimir Oltean wrote:
> - ``dsa_switch_tree``: structure assigned to the conduit network device under
> ``dsa_ptr``, this structure references a dsa_platform_data structure as well as
> the tagging protocol supported by the switch tree, and which receive/transmit
AIs point out struct dsa_switch_tree still contains a pointer to struct
dsa_platform_data and the doc above mentions it. Please follow up.
^ permalink raw reply
* Re: [PATCH net-next 1/2] keys, dns: drop unused upayload->data NUL terminator
From: Jakub Kicinski @ 2026-04-09 2:39 UTC (permalink / raw)
To: Thorsten Blum
Cc: David S. Miller, Eric Dumazet, Paolo Abeni, Simon Horman,
Tim Bird, netdev, linux-kernel
In-Reply-To: <20260406175810.1018681-3-thorsten.blum@linux.dev>
On Mon, 6 Apr 2026 19:58:09 +0200 Thorsten Blum wrote:
> Subject: [PATCH net-next 1/2] keys, dns: drop unused upayload->data NUL terminator
This says net-next but patch 2 never reached netdev@
--
pw-bot: cr
^ permalink raw reply
* Re: [PATCH net-next] codel: annotate data-races in codel_dump_stats()
From: patchwork-bot+netdevbpf @ 2026-04-09 2:40 UTC (permalink / raw)
To: Eric Dumazet; +Cc: davem, kuba, pabeni, horms, jhs, jiri, netdev, eric.dumazet
In-Reply-To: <20260407143053.1570620-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 7 Apr 2026 14:30:53 +0000 you wrote:
> codel_dump_stats() only runs with RTNL held,
> reading fields that can be changed in qdisc fast path.
>
> Add READ_ONCE()/WRITE_ONCE() annotations.
>
> Alternative would be to acquire the qdisc spinlock, but our long-term
> goal is to make qdisc dump operations lockless as much as we can.
>
> [...]
Here is the summary with links:
- [net-next] codel: annotate data-races in codel_dump_stats()
https://git.kernel.org/netdev/net-next/c/ea25e03da7a7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
* Re: [PATCH net-next v2] selftests: forwarding: lib: rewrite processing of command line arguments
From: patchwork-bot+netdevbpf @ 2026-04-09 2:40 UTC (permalink / raw)
To: Ioana Ciornei
Cc: netdev, andrew+netdev, davem, edumazet, kuba, pabeni, horms,
linux-kernel, petrm, willemb, linux-kselftest, shuah, liuhangbin
In-Reply-To: <20260407102058.867279-1-ioana.ciornei@nxp.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 7 Apr 2026 13:20:58 +0300 you wrote:
> The piece of code which processes the command line arguments and
> populates NETIFS based on them is really unobvious. Rewrite it so that
> the intention is clear and the code is easy to follow.
>
> Suggested-by: Petr Machata <petrm@nvidia.com>
> Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
>
> [...]
Here is the summary with links:
- [net-next,v2] selftests: forwarding: lib: rewrite processing of command line arguments
https://git.kernel.org/netdev/net-next/c/fff75dba7992
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox