Received: by 10.213.65.68 with SMTP id h4csp563260imn; Tue, 20 Mar 2018 09:41:42 -0700 (PDT) X-Google-Smtp-Source: AG47ELs/7IOv0pHsWoq7R4SgYSJfJJv6dfuCug0GzJfKZCZztnUBLIePGNt/vFWManNZFj+RfljL X-Received: by 2002:a17:902:6a17:: with SMTP id m23-v6mr17099157plk.342.1521564102407; Tue, 20 Mar 2018 09:41:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521564102; cv=none; d=google.com; s=arc-20160816; b=PJZqRs9fPQ/4UWmwq9GEcHst99lOKcN/0+c9q+HknbcfytCOvQzD55+8MyH5yhrUEK vO1pXTPsZv3QMcwDRYsmQSkA3UIn49ciBKI3sY9+wanT87U1vTUlvu42cPPxcMT3p5aC sguAzBycho/DEXKZZJJD9UPvj62ZSno7PpckWRG5cMLQhCWm1KnVrhMw+XZ4NTmjS0vV nVvbTe2YekVOG87AvwtiEOiwbCLC+xud45SfMt1Q/cXcXDSnpP6ATonu7ScBhPC1nTX0 o+o+I9U0MKyzxRzjxhkYxgoojtevAmoIFVd9euUMWoTR6Zeooo8bJ6ooLz+OW2Zz/V6i yXow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :references:subject:cc:to:mime-version:user-agent:from:date :message-id:dkim-signature:arc-authentication-results; bh=+NxH8Np0iqmiAROOKcpSloOeRGpm0WzYPfaOxY2CV08=; b=DFe6O8b+p7hJmkNpMIrtwmYxdqyyBOFeyrKtKvirRHlgdeI1fJgHhJtK1ChEb7AcQ9 Oj1POTIRHcN7LHXoOsrny/osYXYvlP+U3OZpAR/ekze5+wMddkLmhPsQzu4Kl7K+UhuO f421ZqffoYO4yJzPh01CLW7/x/o6Q9Ydn3EZftuY1PXRIhsxpFtrqzzbQkVJIgwWzrN6 jyAPEKJV25lr/tNw6+2xsyc8nvEIIth79S7sQl2hURhrq4/shKRIE4TkjHYKlJfVC6tJ ICIkraeiyIq4e77KX6+uHXbl6mRI7291Lz5vzwqbytVm2SPvgPDRrbcqsOWwEEAEsDPp jxwg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@oracle.com header.s=corp-2017-10-26 header.b=GpkzebEc; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=oracle.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u66si1529833pfu.375.2018.03.20.09.41.27; Tue, 20 Mar 2018 09:41:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@oracle.com header.s=corp-2017-10-26 header.b=GpkzebEc; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=oracle.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751824AbeCTQj7 (ORCPT + 99 others); Tue, 20 Mar 2018 12:39:59 -0400 Received: from userp2130.oracle.com ([156.151.31.86]:59184 "EHLO userp2130.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751317AbeCTQjz (ORCPT ); Tue, 20 Mar 2018 12:39:55 -0400 Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w2KGWTNe111145; Tue, 20 Mar 2018 16:39:52 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=message-id : date : from : mime-version : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2017-10-26; bh=+NxH8Np0iqmiAROOKcpSloOeRGpm0WzYPfaOxY2CV08=; b=GpkzebEcpeUyiu2Zz9szmBlZfNhk0XiTV2zMdct22LpuTKWjGgOyq6VjwB0DC8qTfoCj Po+mPj2yh0E+Jpl6G9xIjSbTBVahAyqJb+ON8vGiHpJy7ml5sSZvyT5KGouitgpAjrh9 lTv5bD6vLXcA0hLKm/wNMHKz1Gm7eLIkUYXH7AUNdDS1gAuWW/49d9LhsRZqxxUmFr/j mQyrcva5r96FRYSAeLaYfIvn+FQIK0OItj+oyfbLb/Nyj+pDrj4o1HgqmKvaAWvydDKB IZvwUnOyL99VH9RTylUYkqYda5R3Yuh+e3Hz7Ju+wgRSpNaLiMfZC82MAe/nDZFxj8u1 FA== Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp2130.oracle.com with ESMTP id 2gu5wj829d-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 20 Mar 2018 16:39:52 +0000 Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id w2KGdpPj028838 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 20 Mar 2018 16:39:51 GMT Received: from abhmp0011.oracle.com (abhmp0011.oracle.com [141.146.116.17]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id w2KGdpW9015046; Tue, 20 Mar 2018 16:39:51 GMT Received: from [10.0.2.223] (/213.57.127.2) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 20 Mar 2018 09:39:50 -0700 Message-ID: <5AB13953.3000606@ORACLE.COM> Date: Tue, 20 Mar 2018 18:39:47 +0200 From: Liran Alon User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: David Miller CC: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, idan.brown@ORACLE.COM, yuval.shaia@ORACLE.COM Subject: Re: [PATCH] net: dev_forward_skb(): Scrub packet's per-netns info only when crossing netns References: <5AB12A0E.2060704@ORACLE.COM> <20180320.120036.1999626754164343704.davem@davemloft.net> <5AB132C5.5010806@ORACLE.COM> <20180320.123401.2138083793709750726.davem@davemloft.net> In-Reply-To: <20180320.123401.2138083793709750726.davem@davemloft.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8838 signatures=668695 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803200127 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/03/18 18:34, David Miller wrote: > From: Liran Alon > Date: Tue, 20 Mar 2018 18:11:49 +0200 > >> 1. Do we want to make a flag for every bug that is user-space visible? >> I think there is place for consideration on a per-case basis. I still >> don't see how a user can utilize this behaviour. He is basically >> loosing information (skb->mark) without this patch. > > And maybe people trying to work in this situation have added code to > get the mark set some other way, or to validate that it is in fact > zero after passing through, which we would break with this change. > > If it's set to zero now, it's reasonable to expect it to be zero. > > By changing it to non-zero, different rules and routes will match > and this for sure has potential to break things. > OK. What is your opinion in regards if it's OK to put the flag enabling this "fix" in /proc/sys/net/core? Do you think it's sufficient?