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]
Message-ID: <CANn89i+rSEJ3Rqd5JW-w7aLzETMX89Qgg3wne9Ae7WWDBe3yZg@mail.gmail.com>
Date:   Fri, 24 May 2019 08:00:34 -0700
From:   Eric Dumazet <edumazet@...gle.com>
To:     Kefeng Wang <wangkefeng.wang@...wei.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH] kernel: sysctl: change ipfrag_high/low_thresh to CTL_ULONG

On Fri, May 24, 2019 at 7:30 AM Kefeng Wang <wangkefeng.wang@...wei.com> wrote:
>
> 3e67f106f619 ("inet: frags: break the 2GB limit for frags storage"),
> changes ipfrag_high/low_thread 'type' from int to long, using CTL_ULONG
> instead of CTL_INT to keep consistent.


What about  compatibility with existing applications ?
Will there sysctl() fail if they provide 32bit variable ?

/proc/sys/net  files are text files, but sysctl() system call has been
discouraged for more than a decade.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ