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 A1354C433E7 for ; Fri, 9 Oct 2020 19:42:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6A26B22282 for ; Fri, 9 Oct 2020 19:42:08 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="LTmi7rtj" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390736AbgJITmH (ORCPT ); Fri, 9 Oct 2020 15:42:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45510 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390731AbgJITmH (ORCPT ); Fri, 9 Oct 2020 15:42:07 -0400 Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 64A3AC0613D2 for ; Fri, 9 Oct 2020 12:42:06 -0700 (PDT) Received: by mail-pg1-x530.google.com with SMTP id 7so8008600pgm.11 for ; Fri, 09 Oct 2020 12:42:06 -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=tqM3sVoz/RCFxKyfLOaHZdxgdM0zEd9Rfvsck3IllYc=; b=LTmi7rtjDzBpwQJDhsoQrQSeBidkMcdnaKeR9uSpAUHSSvDkvlWeImoa6nWRcAHtUc GM6SlP8kCiUEhIhWx8J8SReSek92/7Q2orgDsEpSGakSmbKunuBMBK9Cajg0asZ3XQ8m osf4cj6G3WnqXxm5z2n19eBqxtFGYgEA7y+l82mt7jNfNEh/1i/GFbXV4ssvhlLvi/hA MM2JJsBwDB0p3gYK2klhwkdxrmz3Euj6aSdsaLjd1llsl2XlaxrHXEmaU4rqgeKVF3V8 FnrztK11anQ+lSNryQQax1StX8L1EwWNCWW2B3asqoKMV9al1eVrDjZdKhPuQzg1uw8c kh7Q== 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=tqM3sVoz/RCFxKyfLOaHZdxgdM0zEd9Rfvsck3IllYc=; b=WTQ0Jbwrmu4AD/DrJpsTOIKbfiw/fiOOUOw8kH8oLQ4bcZ8KoxjkTA9W10Vk4Ro7z1 N46hPUF6V5YMncRQMGaNqQfomtT6SR7EeWJKxL4XbsNeMYgopC4Sfvq9ZGb3Sb/kPEQ4 q+m883R6bg+z9/okxN0x5AS67Y9wLtcu7lLI3aCSRNSNuEnLXpoC7O5M6zOcyOa3Bffy 4SSX4bMPidluXoneTtxT3kYF/yIYp320CKyHA8uI3HOgJ+tpsScUKRhaKylPQVFEAFmY C6Ekf4SVmUVaGmtyYPuuA/DOOQ9xBvgU5l9+HQuP09kqCVO6enyum5d8aPz09ZreEK/Y Pw6Q== X-Gm-Message-State: AOAM532JHvIJClb1FCQCZzfmBdLa3t9K5B1alUweXSeHSDqhGjz8+qpq Gd70D7N9LvfcKjGIMJd+6cId5CFxVpD5H407C1w= X-Google-Smtp-Source: ABdhPJzuFT5V+MaliefWl2E/pZllrIdseLePw3wI+LU7ILtk8bmGkhxtCiZ01pXETz2zbivSKq34NKpqiw3anZhbeVc= X-Received: by 2002:a17:90a:bf92:: with SMTP id d18mr6287236pjs.210.1602272525964; Fri, 09 Oct 2020 12:42:05 -0700 (PDT) MIME-Version: 1.0 References: <20201008012154.11149-1-xiyou.wangcong@gmail.com> In-Reply-To: From: Xie He Date: Fri, 9 Oct 2020 12:41:55 -0700 Message-ID: Subject: Re: [Patch net] ip_gre: set dev->hard_header_len properly To: Cong Wang Cc: Willem de Bruijn , Network Development , syzbot , William Tu Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Fri, Oct 9, 2020 at 10:44 AM Cong Wang wrote: > > On Thu, Oct 8, 2020 at 4:40 PM Xie He wrote: > > > > 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? > > Good catch. It should be updated there like ->needed_headroom. > I will update my patch. Thanks. But there is still something that I don't understand. What is needed_headroom used for? If we are requesting space for t->encap_hlen and t->tun_hlen in hard_header_len. Do we still need to use needed_headroom? Also, if we update hard_header_len or needed_headroom in ipgre_link_update, would there be racing issues if they are updated while skbs are being sent? If these are indeed issues, it might not be easy to fix this driver. Willem, do you have any thoughts?