[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <875z7asjfd.fsf@kurt>
Date: Fri, 16 Oct 2020 09:45:42 +0200
From: Kurt Kanzenbach <kurt@...utronix.de>
To: Christian Eggers <ceggers@...i.de>,
Vladimir Oltean <olteanv@...il.com>
Cc: Woojung Huh <woojung.huh@...rochip.com>,
Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Microchip Linux Driver Support <UNGLinuxDriver@...rochip.com>,
"David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net] net: dsa: ksz: fix padding size of skb
On Thu Oct 15 2020, Christian Eggers wrote:
> On Wednesday, 14 October 2020, 19:31:03 CEST, Vladimir Oltean wrote:
>> What problem are you actually trying to solve?
> After (hopefully) understanding the important bits, I would like to solve the
> problem that after calling __skb_put_padto() there may be no tailroom for the
> tail tag.
>
> The conditions where this can happen are quite special. You need a skb->len <
> ETH_ZLEN and the skb must be marked as cloned. One condition where this
> happens in practice is when the skb has been selected for TX time stamping in
> dsa_skb_tx_timestamp() [cloned] and L2 is used as transport for PTP [size <
> ETH_ZLEN]. But maybe cloned sk_buffs can also happen for other reasons.
Hmm. I've never observed any problems using DSA with L2 PTP time
stamping with this tail tag code. What's the impact exactly? Memory
corruption?
Thanks,
Kurt
Download attachment "signature.asc" of type "application/pgp-signature" (833 bytes)
Powered by blists - more mailing lists