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: 
 <174248163252.1791127.9515297719544787878.git-patchwork-notify@kernel.org>
Date: Thu, 20 Mar 2025 14:40:32 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Simon Wunderlich <sw@...onwunderlich.de>
Cc: davem@...emloft.net, kuba@...nel.org, netdev@...r.kernel.org,
 pabeni@...hat.com, b.a.t.m.a.n@...ts.open-mesh.org, sven@...fation.org,
 stable@...r.kernel.org
Subject: Re: [PATCH net 1/1] batman-adv: Ignore own maximum aggregation size
 during RX

Hello:

This patch was applied to netdev/net.git (main)
by Simon Wunderlich <sw@...onwunderlich.de>:

On Tue, 18 Mar 2025 16:00:35 +0100 you wrote:
> From: Sven Eckelmann <sven@...fation.org>
> 
> An OGMv1 and OGMv2 packet receive processing were not only limited by the
> number of bytes in the received packet but also by the nodes maximum
> aggregation packet size limit. But this limit is relevant for TX and not
> for RX. It must not be enforced by batadv_(i)v_ogm_aggr_packet to avoid
> loss of information in case of a different limit for sender and receiver.
> 
> [...]

Here is the summary with links:
  - [net,1/1] batman-adv: Ignore own maximum aggregation size during RX
    https://git.kernel.org/netdev/net/c/548b0c5de761

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



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ