Re: [RFC] Handle error writing UINT_MAX to u32 fields

2016-06-14 Thread subashab
On 2016-06-12 20:30, subas...@codeaurora.org wrote: The suggested change would extend the usable range of positive numbers by one bit only. As many systems are 64 bit this does not seem forward looking. I would prefer to have a routine that can handle 64 bit integers with limits (let's call it

Re: [RFC] Handle error writing UINT_MAX to u32 fields

2016-06-12 Thread subashab
The suggested change would extend the usable range of positive numbers by one bit only. As many systems are 64 bit this does not seem forward looking. I would prefer to have a routine that can handle 64 bit integers with limits (let's call it proc_doint64vec_minmax) which uses fields extra1 and

Re: [RFC] Handle error writing UINT_MAX to u32 fields

2016-06-10 Thread Heinrich Schuchardt
On 06/10/2016 04:40 AM, Subash Abhinov Kasiviswanathan wrote: > We have scripts which write to certain fields on 3.18 kernels but > this seems to be failing on 4.4 kernels. > An entry which we write to here is xfrm_aevent_rseqth which is u32. > > echo 4294967295 >

Re: [RFC] Handle error writing UINT_MAX to u32 fields

2016-06-10 Thread Heinrich Schuchardt
On 06/10/2016 04:40 AM, Subash Abhinov Kasiviswanathan wrote: > We have scripts which write to certain fields on 3.18 kernels but > this seems to be failing on 4.4 kernels. > An entry which we write to here is xfrm_aevent_rseqth which is u32. > > echo 4294967295 >

[RFC] Handle error writing UINT_MAX to u32 fields

2016-06-09 Thread Subash Abhinov Kasiviswanathan
We have scripts which write to certain fields on 3.18 kernels but this seems to be failing on 4.4 kernels. An entry which we write to here is xfrm_aevent_rseqth which is u32. echo 4294967295 > /proc/sys/net/core/xfrm_aevent_rseqth Commit 230633d109e35b0a24277498e773edeb79b4a331