Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752447AbbKQClo (ORCPT ); Mon, 16 Nov 2015 21:41:44 -0500 Received: from frisell.zx2c4.com ([192.95.5.64]:50777 "EHLO frisell.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751577AbbKQClm (ORCPT ); Mon, 16 Nov 2015 21:41:42 -0500 MIME-Version: 1.0 In-Reply-To: <1447712932.22599.77.camel@edumazet-glaptop2.roam.corp.google.com> References: <20151116203709.GA27178@oracle.com> <1447712932.22599.77.camel@edumazet-glaptop2.roam.corp.google.com> Date: Tue, 17 Nov 2015 03:41:35 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Routing loops & TTL tracking with tunnel devices From: "Jason A. Donenfeld" To: Eric Dumazet Cc: Sowmini Varadhan , Jiri Benc , David Miller , Netdev , LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 770 Lines: 16 Hi Eric, On Mon, Nov 16, 2015 at 11:28 PM, Eric Dumazet wrote: > There is very little chance we'll accept a new member in sk_buff, unless > proven needed. I actually have no intention of doing this! I'm wondering if there already is a member in sk_buff that moonlights as my desired ttl counter, or if there's another mechanism for avoiding routing loops. I want to work with what's already there, rather than meddling with the innards of important and memory sensitive structures such as sk_buff. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/