Received: by 2002:a05:6a10:1d13:0:0:0:0 with SMTP id pp19csp1658994pxb; Fri, 20 Aug 2021 10:38:38 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxA6u3OiVrm51ePyPN2kSYkVWdfL+TPSzOLYcDxx/vUHdtePS3BJimHNmofnoJua1c8c8qj X-Received: by 2002:a05:6602:584:: with SMTP id v4mr16684195iox.85.1629481118099; Fri, 20 Aug 2021 10:38:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1629481118; cv=none; d=google.com; s=arc-20160816; b=BkX4lIr4pgrRg7PxuTrw1HShhPmQG3TpLgeXxBM26CXg9gL7nN5cs+5wQA7jk61dSb bLjq/oJ321i9//yGz8UCaQjlRifm67EkhHItZB/Wr6NeIsN29gQtmbBsejuUQruqzFuZ baIb1kJdL+quXc4WhHvAoxVohK1U8iP++/ew2kVgxEX+hG4eQtVg76JmOvxomK5dBEHA CqnhK2S+BAiplyD5mDRP0rdcl3Dz4NStdTwG4zDKa3A+ImyePSEkHQc2h+WTzeBq4OPz QqGdW/Kqym4OgjjxSw3yctl/9iATou8byLFWXNVMcR8ImTJUh4neN0eY0s/FNs8ftP1/ KYug== 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=dkfEmMb69UrtMjAtZDzM024/xNYhw2xqJs/2HMtdXmc=; b=xUZ8UwLZ3Md6nwQOhY+yphxLsmWXcWaPDIN8eE1y5fbJazo4VHqfdGF4Jrn7owQtve ksY7O8JHwF3Fk7sMkmNg12jbYk5KV01T9W8JDKB4koJR5PJHPwb3xxsCqWrSm8Neh2qW 1K+GkujXfncqIFWgpTNuHieBA73cNfhTbpmD/UxlqnoySql1/qgxGmDpHbKtd6dU0nVD /+qNcfMGwriB3OIMA1cU3vnq1uc3HN0Qw1TP1CLq6mdhsG3sZBm3PFQ7bejstE/kZJPz j668kMF0a/DkL/gYpt3gdXoV3EnBweXJzCVWbp+mpYwzyfroP/pEPXv68O4h3Q9BwdUC Kv7Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux.microsoft.com header.s=default header.b=fKJaNRe8; 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 a4si1369153ilt.54.2021.08.20.10.38.25; Fri, 20 Aug 2021 10:38:38 -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=fKJaNRe8; 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 S234148AbhHTRhA (ORCPT + 99 others); Fri, 20 Aug 2021 13:37:00 -0400 Received: from linux.microsoft.com ([13.77.154.182]:38542 "EHLO linux.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233320AbhHTRhA (ORCPT ); Fri, 20 Aug 2021 13:37:00 -0400 Received: from mail-pf1-f180.google.com (mail-pf1-f180.google.com [209.85.210.180]) by linux.microsoft.com (Postfix) with ESMTPSA id CDEE620C33CF; Fri, 20 Aug 2021 10:36:21 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com CDEE620C33CF DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1629480981; bh=dkfEmMb69UrtMjAtZDzM024/xNYhw2xqJs/2HMtdXmc=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=fKJaNRe8+MCJB0KJLYLvuDKp8miNx/jC+Jp6ZFrZ/FSt75nUdzW7vqaje/ZCxEddS X1RCR3Q0xhrifCeUBjS8HIIGUazF5dt53FF+RHgPhOhZShRZ/Vtn8JJ0xnojFiss25 j5aeXUNKAwvg/MfJ61hfAyj8lo1T6rLcfqiYLK3I= Received: by mail-pf1-f180.google.com with SMTP id i21so9216743pfd.8; Fri, 20 Aug 2021 10:36:21 -0700 (PDT) X-Gm-Message-State: AOAM533XXowtFxrlGkytLP4elrr3pMoEliRu4bpa5blSaS5g06dI6Ggo ULtAuy4v7g96piWkiZN5krq/eZn1hnsjKYJQjFc= X-Received: by 2002:a63:fe41:: with SMTP id x1mr19382794pgj.272.1629480981404; Fri, 20 Aug 2021 10:36:21 -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> In-Reply-To: <87h7fkyqpv.wl-maz@kernel.org> From: Matteo Croce Date: Fri, 20 Aug 2021 19:35:45 +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: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? -- per aspera ad upstream