linux-kernel - Re: Linux 4.4.174

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 9 Feb 2019 09:13:01 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Mark D Rustad <mrustad@...il.com>
Cc:     linux-kernel@...r.kernel.org,
        Andrew Morton <akpm@...ux-foundation.org>,
        torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net,
        Jiri Slaby <jslaby@...e.cz>
Subject: Re: Linux 4.4.174

On Fri, Feb 08, 2019 at 08:44:32PM -0800, Mark D Rustad wrote:
> On Feb 8, 2019, at 2:54 AM, Greg KH <gregkh@...uxfoundation.org> 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 :)