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=-5.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham 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 C76A1C282C2 for ; Wed, 13 Feb 2019 07:48:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8AF46222C2 for ; Wed, 13 Feb 2019 07:48:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1550044095; bh=J5+YQZNHiUEsQpHZYR1XGrqUK1eplI2fDOdYxwyTkQ0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=kZHjlJlQwx8Qbnz1oGs71pdz1wyA737YiZ7ND4TwhBlZZmYjSVUh9LvenSASyAJDj bBZ3S0vz1yIRabDdRdwAQr2IoIcM2BtglXyfEq3vz+sIKtVkMszwlJqP+bOnAfcN6x 3SykDu4MYSzCyvP/d9gtj54dlBZ3j2qqfflmJDDY= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731819AbfBMHsP (ORCPT ); Wed, 13 Feb 2019 02:48:15 -0500 Received: from mail.kernel.org ([198.145.29.99]:58560 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730851AbfBMHsO (ORCPT ); Wed, 13 Feb 2019 02:48:14 -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 84F65222BA; Wed, 13 Feb 2019 07:48:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1550044094; bh=J5+YQZNHiUEsQpHZYR1XGrqUK1eplI2fDOdYxwyTkQ0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=GaPxl0eDIVu4dquSj+xW46FFESRNb7AOmZaUiO3/QIn56xNuR+hhlSwU4AspqnE8J 8RdcnhVyECH4OU200pc6LMmxNG1QluXPzKtlrLDpnBq47hAMDxHWQsP6s2EQcqamWq 2pg5boNAxgVuFEr59xtFv1SaDyDRmiKKjkrmFBEM= Date: Wed, 13 Feb 2019 08:48:11 +0100 From: Greg KH To: Mark D Rustad Cc: linux-kernel@vger.kernel.org, Andrew Morton , torvalds@linux-foundation.org, stable@vger.kernel.org, lwn@lwn.net, Jiri Slaby Subject: Re: Linux 4.4.174 Message-ID: <20190213074811.GC3246@kroah.com> References: <20190208105422.GA32328@kroah.com> <20190208105431.GB32328@kroah.com> <870EE9C6-3748-498C-B6E8-33724168C605@gmail.com> <20190209081301.GB30034@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.3 (2019-02-01) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Tue, Feb 12, 2019 at 08:13:11PM -0800, Mark D Rustad wrote: > On Feb 9, 2019, at 12:13 AM, Greg KH wrote: > > > On Fri, Feb 08, 2019 at 08:44:32PM -0800, Mark D Rustad wrote: > > > On Feb 8, 2019, at 2:54 AM, Greg KH wrote: > > > > > > > diff --git a/Documentation/networking/ip-sysctl.txt > > > > b/Documentation/networking/ip-sysctl.txt > > > > index 2ea4c45cf1c8..7c229f59016f 100644 > > > > --- a/Documentation/networking/ip-sysctl.txt > > > > +++ b/Documentation/networking/ip-sysctl.txt > > > > @@ -112,14 +112,11 @@ min_adv_mss - INTEGER > > > > > > > > IP Fragmentation: > > > > > > > > -ipfrag_high_thresh - INTEGER > > > > - Maximum memory used to reassemble IP fragments. When > > > > - ipfrag_high_thresh bytes of memory is allocated for this purpose, > > > > - the fragment handler will toss packets until ipfrag_low_thresh > > > > - is reached. This also serves as a maximum limit to namespaces > > > > - different from the initial one. > > > > - > > > > -ipfrag_low_thresh - INTEGER > > > > +ipfrag_high_thresh - LONG INTEGER > > > > + Maximum memory used to reassemble IP fragments. > > > > + > > > > +ipfrag_low_thresh - LONG INTEGER > > > > + (Obsolete since linux-4.17) > > > > > > It seems very strange to say that it is obsolete since 4.17 in a 4.4 > > > kernel. > > > > 4.17 is a point in time :) > > Of course I understand, but some random non-kernel-developer tuning a kernel > may be pretty puzzled. I don't know right off the top something brief that > would be more generally meaningful, but maybe someone might. What does > obsolete mean in this context? It exists but does nothing? It exists and > does something but will eventually go away? Fair enough, want to provide a patch with the real kernel version this happened in? thanks, greg k-h