Received: by 2002:a05:6a10:1d13:0:0:0:0 with SMTP id pp19csp1678519pxb; Fri, 20 Aug 2021 11:07:43 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxwUFD0cbmzF3olvmXt+3V1qzhEPNNR74plO0ai6AhRIoRkK3WuGxrGVfbxTwFN8Lcl8JVW X-Received: by 2002:a02:cb46:: with SMTP id k6mr19064211jap.15.1629482863598; Fri, 20 Aug 2021 11:07:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1629482863; cv=none; d=google.com; s=arc-20160816; b=ht7H0BrTs8XzuGx7Ky1xo157FLxKN3b6ssd4iDFoKWdugCrZw/2BEfyjWcKi47nqgs z/iwXO0vzGiNCVAEBOK3VkV12lI1eB+w2ZK9Zm/HQT8cO1NIXhx8MBKyfSF6XUkBFimJ GtjE993cTg6qnqW1y0sxLQqCekuQr9Jz+g2eRXEbMLRFfCZCQoFC0PljB4HHfwKUwkRa 8iEChnPgmhR5Zl2erkVTlvcfgjrQr6kKg+Byk6fb7iXZsXs+d4ZDQh8n4VGGB/ulqGf/ MUlVbQ2vLzWMVn8vHzkp9/XlBQIKLhOAAY/kncQbzwwF2WOs4Ahk5GQF4S/2leSX+s5V HPMw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature:dkim-filter; bh=TawcIDwLw6//Gm4u2yn5lu5a4ZS6+2gDCjGqcHeuimU=; b=MjHMeoG5eA4Z9wuN2FpMT4jpEzUKf4URmueM6J3C80Nx8QDWcb0BZTXd4XF2Zh8o/B +bZKuKp5grfGK1Wj1dqik4TcHc4b01jFK24xBIlN0lhG8Ut83h9WjATxieKjWpN9bY4y T46EBDhtJ4O1fzOdA5sFUxn5t1b4YEmjO2AO+e6KMSMJTQG8UaIsE/1TclLoy6FyIbNi DGdLB6qVLNbet00ecpgHMFovciFmrb14WNd9ttYnj50qAj9esJzriWC1SqcGCFocstqc NYCnaY0ZhVZ8FN9AGuKHsFyBFodv9g/fPTgtf2NJm1FOH10OiWHfGBLplHIFD4WOYNr5 56WA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux.microsoft.com header.s=default header.b=K1VJwv5s; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.microsoft.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k17si7085969jao.14.2021.08.20.11.07.30; Fri, 20 Aug 2021 11:07:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linux.microsoft.com header.s=default header.b=K1VJwv5s; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.microsoft.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232629AbhHTSHN (ORCPT + 99 others); Fri, 20 Aug 2021 14:07:13 -0400 Received: from linux.microsoft.com ([13.77.154.182]:41774 "EHLO linux.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229560AbhHTSHM (ORCPT ); Fri, 20 Aug 2021 14:07:12 -0400 Received: from mail-pg1-f182.google.com (mail-pg1-f182.google.com [209.85.215.182]) by linux.microsoft.com (Postfix) with ESMTPSA id DC71320C33D5; Fri, 20 Aug 2021 11:06:33 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com DC71320C33D5 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1629482793; bh=TawcIDwLw6//Gm4u2yn5lu5a4ZS6+2gDCjGqcHeuimU=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=K1VJwv5ss64RbWMF/zk8eHP5BO1FsisgU3ah+UtmPELqhKukoR2Ii34ZVG6HnCupa oqeYkEKbI8xJEVM5S3ZCcAS+GfqTVm1a6OOYlmEFbSIF/iBRkffhJ0A59+R5ZjzbvU 06Cip3qkCzKVyer71G4vXMb2M4HDoMGhMIMHYOig= Received: by mail-pg1-f182.google.com with SMTP id r2so9945051pgl.10; Fri, 20 Aug 2021 11:06:33 -0700 (PDT) X-Gm-Message-State: AOAM533VKVF3Rvngcd/hQTsgx9DxfWhgALMm9JMeJEcJX/xt0KKvTQnH gHFWsJNOjcolADHRVn/Q3fyxNWjA3VTMC3iTS8g= X-Received: by 2002:aa7:9904:0:b0:3e1:a79a:222e with SMTP id z4-20020aa79904000000b003e1a79a222emr21030272pff.41.1629482793349; Fri, 20 Aug 2021 11:06:33 -0700 (PDT) MIME-Version: 1.0 References: <20210614022504.24458-1-mcroce@linux.microsoft.com> <871r71azjw.wl-maz@kernel.org> <202417ef-f8ae-895d-4d07-1f9f3d89b4a4@gmail.com> <87o8a49idp.wl-maz@kernel.org> <20210812121835.405d2e37@linux.microsoft.com> <874kbuapod.wl-maz@kernel.org> <87wnohqty1.wl-maz@kernel.org> <87fsv4qdzm.wl-maz@kernel.org> <87mtpcyrdv.wl-maz@kernel.org> <87h7fkyqpv.wl-maz@kernel.org> <87fsv4ypfn.wl-maz@kernel.org> In-Reply-To: From: Matteo Croce Date: Fri, 20 Aug 2021 20:05:57 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH net-next] stmmac: align RX buffers To: Marc Zyngier Cc: Eric Dumazet , Thierry Reding , netdev@vger.kernel.org, Linux Kernel Mailing List , linux-riscv , Giuseppe Cavallaro , Alexandre Torgue , "David S. Miller" , Jakub Kicinski , Palmer Dabbelt , Paul Walmsley , Drew Fustini , Emil Renner Berthing , Jon Hunter , Will Deacon Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 20, 2021 at 7:56 PM Matteo Croce wrote: > > On Fri, Aug 20, 2021 at 7:51 PM Marc Zyngier wrote: > > > > On Fri, 20 Aug 2021 18:35:45 +0100, > > Matteo Croce wrote: > > > > > > On Fri, Aug 20, 2021 at 7:24 PM Marc Zyngier wrote: > > > > > > > > On Fri, 20 Aug 2021 18:14:30 +0100, > > > > Matteo Croce wrote: > > > > > > > > > > On Fri, Aug 20, 2021 at 7:09 PM Marc Zyngier wrote: > > > > > > > > > > > > On Fri, 20 Aug 2021 17:38:14 +0100, > > > > > > Matteo Croce wrote: > > > > > > > > > > > > > > On Fri, Aug 20, 2021 at 6:26 PM Marc Zyngier wrote: > > > > > > > > > > > > > > > > On Fri, 20 Aug 2021 11:37:03 +0100, > > > > > > > > Matteo Croce wrote: > > > > > > > > > > > > > > > > > > On Thu, Aug 19, 2021 at 6:29 PM Marc Zyngier wrote: > > > > > > > > > > > > > > > > [...] > > > > > > > > > > > > > > > > > > diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac.h b/drivers/net/ethernet/stmicro/stmmac/stmmac.h > > > > > > > > > > index fcdb1d20389b..244aa6579ef4 100644 > > > > > > > > > > --- a/drivers/net/ethernet/stmicro/stmmac/stmmac.h > > > > > > > > > > +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac.h > > > > > > > > > > @@ -341,7 +341,7 @@ static inline unsigned int stmmac_rx_offset(struct stmmac_priv *priv) > > > > > > > > > > if (stmmac_xdp_is_enabled(priv)) > > > > > > > > > > return XDP_PACKET_HEADROOM + NET_IP_ALIGN; > > > > > > > > > > > > > > > > > > > > - return NET_SKB_PAD + NET_IP_ALIGN; > > > > > > > > > > + return 8 + NET_IP_ALIGN; > > > > > > > > > > } > > > > > > > > > > > > > > > > > > > > void stmmac_disable_rx_queue(struct stmmac_priv *priv, u32 queue); > > > > > > > > > > > > > > > > > > > > I don't see the system corrupting packets anymore. Is that exactly > > > > > > > > > > what you had in mind? This really seems to point to a basic buffer > > > > > > > > > > overflow. > > > > > > > > > > > > > > > > [...] > > > > > > > > > > > > > > > > > Sorry, I meant something like: > > > > > > > > > > > > > > > > > > - return NET_SKB_PAD + NET_IP_ALIGN; > > > > > > > > > + return 8; > > > > > > > > > > > > > > > > > > I had some hardware which DMA fails if the receive buffer was not word > > > > > > > > > aligned, but this seems not the case, as 8 + NET_IP_ALIGN = 10, and > > > > > > > > > it's not aligned too. > > > > > > > > > > > > > > > > No error in that case either, as expected. Given that NET_SKB_PAD is > > > > > > > > likely to expand to 64, it is likely a DMA buffer overflow which > > > > > > > > probably only triggers for large-ish packets. > > > > > > > > > > > > > > > > Now, we're almost at -rc7, and we don't have a solution in sight. > > > > > > > > > > > > > > > > Can we please revert this until we have an understanding of what is > > > > > > > > happening? I'll hopefully have more cycles to work on the issue once > > > > > > > > 5.14 is out, and hopefully the maintainers of this driver can chime in > > > > > > > > (they have been pretty quiet so far). > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > > > M. > > > > > > > > > > > > > > > > -- > > > > > > > > Without deviation from the norm, progress is not possible. > > > > > > > > > > > > > > Last try, what about adding only NET_IP_ALIGN and leaving NET_SKB_PAD? > > > > > > > > > > > > > > - return NET_SKB_PAD + NET_IP_ALIGN; > > > > > > > + return NET_IP_ALIGN; > > > > > > > > > > > > > > I think that alloc_skb adds another NET_SKB_PAD anyway. > > > > > > > > > > > > I don't see any packet corruption with this. However, this doesn't > > > > > > prove that this is correct either. What was the rational for adding > > > > > > NET_SKB_PAD the first place? > > > > > > > > > > > > > > > > I think it's wrong. The original offset was 0, and to align it to the > > > > > boundary we need to add just NET_IP_ALIGN, which is two. > > > > > NET_SKB_PAD is a much bigger value, (I think 64), which is used to > > > > > reserve space to prepend an header, e.g. with tunnels. > > > > > > > > How about the other adjustments that Eric mentioned regarding the size > > > > of the buffer? Aren't they required? > > > > > > > > > > I guess that if stmmac_rx_buf1_len() needed such adjustment, it would > > > be already broken when XDP is in use. > > > When you use XDP, stmmac_rx_offset() adds a pretty big headroom of 256 > > > byte, which would easily trigger an overflow if not accounted. > > > Did you try attaching a simple XDP program on a stock 5.13 kernel? > > > > Yes, as mentioned in [1], to which you replied... > > > > M. > > > > [1] https://lore.kernel.org/r/87wnohqty1.wl-maz@kernel.org > > > > Great. > So I doubt that the adjustment is needed. > Does it work with all the frame size? > Last check, are you sure that the bpf program was loaded in the driver and not as generic XDP? You can force it as native with "xdpdrv": ip link set eth xdpdrv object kernel_passall.o -- per aspera ad upstream