From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D36B4C43457 for ; Thu, 8 Oct 2020 23:40:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 791B12224C for ; Thu, 8 Oct 2020 23:40:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="MdEQ8wHY" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731098AbgJHXks (ORCPT ); Thu, 8 Oct 2020 19:40:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57292 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731078AbgJHXks (ORCPT ); Thu, 8 Oct 2020 19:40:48 -0400 Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2CAFEC0613D2 for ; Thu, 8 Oct 2020 16:40:48 -0700 (PDT) Received: by mail-pf1-x432.google.com with SMTP id y14so5271848pfp.13 for ; Thu, 08 Oct 2020 16:40:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Udjn1bvkZ4meZbMXj7IPyV+N7NltxAtY/GaXzekbmYw=; b=MdEQ8wHYUW6g0sHwmFgeY6CfVeTPhc47FBHmDJRvscDz1i4UmgbMOGd63Cf4VHJabQ 1BW0YGbLW2rsjwadXiAaBlXROR/azoYKS7T/2ZXGk/NZP3Ls3CuIGK4OxTl2RP0CZiXD oDCp0ODrB8h0sgmLirw40DkW3wl6Dcsflv5odUjZO1aD1QVdQxMB01pYryn9bJVKnYcW O9I3U3yf+5Rn7BWscc/pHR95AVK8Zn2o02S47iacdHKL6g2LCEOLC5qu68e7wiUkWRgD JzcciVRPA/XA64dsSmDQt7bPtjQDEMlIDv4x3MWTe9YKYFI9EuIZ8gVLVSHnBCS4Rp4y HHbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Udjn1bvkZ4meZbMXj7IPyV+N7NltxAtY/GaXzekbmYw=; b=CTtCfWN6pRU2XI2QZTq95Fq4OHxPiOZqasb10aIeCo1b661l66A9/TdZdc7yifJmmo 7TujEV8ejVaguwr60YHn1C/9T73piucl0Nkvocsc2tE6NOG0D7J2pLzie7NV3kVOMdWM cUlFKsBAHOIW9oVcmcfEWgSw3g3rDoHaNAMJKgnk5MEBpRd7Zof9nIsvbZTdvUoDLZRB Oas28UVcZQY4XVx3DMowusxmV3YxCXGj02O8QljuoDAR4ldJX9YI6/F3fDWPZPL6u3v1 eDC2cb9hmovTBqAs8ra9wKljTbpohXuB2NIiP3b4Q+30AIaVD5CwYUUWMDI88QnNrkzF UlKg== X-Gm-Message-State: AOAM533UtWlxw8G7UeXstVc4aq8ioz+Bw2NszYEZINofrIYDrsZUvU4L xIQCmql4bZ8dJ6jYsD9v9xjBSfIXDcrFgwN5G9Y= X-Google-Smtp-Source: ABdhPJyVaj90e3JRini8mZtD+iFti3Pxz9kLoveteQbzFyRVvh1qxL37C6tbslh7aP2mf9tpVL8tWECwdKM2SWrqY60= X-Received: by 2002:a17:90a:aa91:: with SMTP id l17mr1370226pjq.198.1602200447705; Thu, 08 Oct 2020 16:40:47 -0700 (PDT) MIME-Version: 1.0 References: <20201008012154.11149-1-xiyou.wangcong@gmail.com> In-Reply-To: From: Xie He Date: Thu, 8 Oct 2020 16:40:36 -0700 Message-ID: Subject: Re: [Patch net] ip_gre: set dev->hard_header_len properly To: Willem de Bruijn Cc: Cong Wang , Network Development , syzbot , William Tu Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Thu, Oct 8, 2020 at 2:54 PM Xie He wrote: > > OK. If the t->encap_hlen header needs to be placed before the GRE > header, then I think the ipgre_header function should leave some space > before the GRE header to place the t->encap_hlen header, rather than > leaving space after the GRE header. I found another possible issue. Shouldn't we update hard_header_len every time t->tun_hlen and t->hlen are updated in ipgre_link_update?