netdev - Re: [PATCH net-next] net: xfrm: Change u32 sysctl entries to use proc

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: <20160908055117.GM31137@gauss.secunet.com>
Date:   Thu, 8 Sep 2016 07:51:17 +0200
From:   Steffen Klassert <steffen.klassert@...unet.com>
To:     David Miller <davem@...emloft.net>
CC:     <subashab@...eaurora.org>, <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next] net: xfrm: Change u32 sysctl entries to use
 proc_douintvec

On Wed, Sep 07, 2016 at 05:25:18PM -0700, David Miller wrote:
> From: Subash Abhinov Kasiviswanathan <subashab@...eaurora.org>
> Date: Tue,  6 Sep 2016 18:09:31 -0600
> 
> > proc_dointvec limits the values to INT_MAX in u32 sysctl entries.
> > proc_douintvec allows to write upto UINT_MAX.
> > 
> > Signed-off-by: Subash Abhinov Kasiviswanathan <subashab@...eaurora.org>
> 
> I am assuming Steffen will pick this up.

proc_douintvec is not in the ipsec-next tree. The ipsec-next
tree is currently based on net-next from Aug 9. The patch
that introduces proc_douintvec came in on Aug 25.

I can take it after the pull request for ipsec-next, that
I plan to do today. Alternatively, you can take it directly
into net-next. It does not interfere anything that I
have in ipsec-next. In case you want to take it directly:

Acked-by: Steffen Klassert <steffen.klassert@...unet.com>