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=-7.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS,USER_AGENT_GIT autolearn=unavailable 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 A2246C282C3 for ; Thu, 24 Jan 2019 19:58:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 66FC5218D0 for ; Thu, 24 Jan 2019 19:58:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548359882; bh=EW6em8OWyjk1H6XPADN+rpW4ZTTXrL1tUG0Bko97ZGo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=itbNCQdIim8dEDv2NfaTxe+t0dnfVyHSf/U9bdlG6QnHIgH7VYhMpbF8/WqSg/rnM n6iDzxtS+J008EVZEJfZLrtKzPa68AjboTYeKmqADAXunOhwXqbLLPhg398cy6YOzF zEghzS9S5NjwuyZ8anNuNPHc19GfUozouZVjV0xs= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732258AbfAXTes (ORCPT ); Thu, 24 Jan 2019 14:34:48 -0500 Received: from mail.kernel.org ([198.145.29.99]:34634 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730296AbfAXTer (ORCPT ); Thu, 24 Jan 2019 14:34:47 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 6728D218FC; Thu, 24 Jan 2019 19:34:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548358486; bh=EW6em8OWyjk1H6XPADN+rpW4ZTTXrL1tUG0Bko97ZGo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=JVP9kFhYLnvQiOA1ITaIS+FkJAu+8CMipSPrlYKWl4A0oR8g1vNQhv0a4wc/QeCWj GS34dR4Sj6/cG3CdrulA5fsAe4t373IJFL02+GFdM7qszWevQmN/FlDwnCtuXvyA/w zruc6qm5AHUYUpsZJiwEDReRNCiEBkUcWMBoprEM= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Paolo Abeni , Nikolay Aleksandrov , Roopa Prabhu , Eric Dumazet , "David S. Miller" , Matteo Croce Subject: [PATCH 4.19 009/106] net: clear skb->tstamp in bridge forwarding path Date: Thu, 24 Jan 2019 20:19:26 +0100 Message-Id: <20190124190206.974635854@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190124190206.342411005@linuxfoundation.org> References: <20190124190206.342411005@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org 4.19-stable review patch. If anyone has any objections, please let me know. ------------------ From: Paolo Abeni [ Upstream commit 41d1c8839e5f8cb781cc635f12791decee8271b7 ] Matteo reported forwarding issues inside the linux bridge, if the enslaved interfaces use the fq qdisc. Similar to commit 8203e2d844d3 ("net: clear skb->tstamp in forwarding paths"), we need to clear the tstamp field in the bridge forwarding path. Fixes: 80b14dee2bea ("net: Add a new socket option for a future transmit time.") Fixes: fb420d5d91c1 ("tcp/fq: move back to CLOCK_MONOTONIC") Reported-and-tested-by: Matteo Croce Signed-off-by: Paolo Abeni Acked-by: Nikolay Aleksandrov Acked-by: Roopa Prabhu Reviewed-by: Eric Dumazet Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman --- net/bridge/br_forward.c | 1 + 1 file changed, 1 insertion(+) --- a/net/bridge/br_forward.c +++ b/net/bridge/br_forward.c @@ -65,6 +65,7 @@ EXPORT_SYMBOL_GPL(br_dev_queue_push_xmit int br_forward_finish(struct net *net, struct sock *sk, struct sk_buff *skb) { + skb->tstamp = 0; return NF_HOOK(NFPROTO_BRIDGE, NF_BR_POST_ROUTING, net, sk, skb, NULL, skb->dev, br_dev_queue_push_xmit);