Re: [RFC] ubsan: signed integer overflow in setitimer()

2017-06-06 Thread Thomas Gleixner
On Tue, 6 Jun 2017, Xishi Qiu wrote: > On 2017/6/4 23:06, Thomas Gleixner wrote: > > On Thu, 1 Jun 2017, Xishi Qiu wrote: > > > > Cc'ed John Stultz > > > >> Hi, this is the test case, and then I got ubsan error > >> (signed integer overflow) report, so the root cause is from > >> user or kernel?

Re: [RFC] ubsan: signed integer overflow in setitimer()

2017-06-06 Thread Thomas Gleixner
On Tue, 6 Jun 2017, Xishi Qiu wrote: > On 2017/6/4 23:06, Thomas Gleixner wrote: > > On Thu, 1 Jun 2017, Xishi Qiu wrote: > > > > Cc'ed John Stultz > > > >> Hi, this is the test case, and then I got ubsan error > >> (signed integer overflow) report, so the root cause is from > >> user or kernel?

Re: [RFC] ubsan: signed integer overflow in setitimer()

2017-06-06 Thread Xishi Qiu
On 2017/6/4 23:06, Thomas Gleixner wrote: > On Thu, 1 Jun 2017, Xishi Qiu wrote: > > Cc'ed John Stultz > >> Hi, this is the test case, and then I got ubsan error >> (signed integer overflow) report, so the root cause is from >> user or kernel? Shall we change something in timeval_valid()? >> >>

Re: [RFC] ubsan: signed integer overflow in setitimer()

2017-06-06 Thread Xishi Qiu
On 2017/6/4 23:06, Thomas Gleixner wrote: > On Thu, 1 Jun 2017, Xishi Qiu wrote: > > Cc'ed John Stultz > >> Hi, this is the test case, and then I got ubsan error >> (signed integer overflow) report, so the root cause is from >> user or kernel? Shall we change something in timeval_valid()? >> >>

Re: [RFC] ubsan: signed integer overflow in setitimer()

2017-06-04 Thread Thomas Gleixner
On Thu, 1 Jun 2017, Xishi Qiu wrote: Cc'ed John Stultz > Hi, this is the test case, and then I got ubsan error > (signed integer overflow) report, so the root cause is from > user or kernel? Shall we change something in timeval_valid()? > > > struct itimerval new_value; > int ret; > >

Re: [RFC] ubsan: signed integer overflow in setitimer()

2017-06-04 Thread Thomas Gleixner
On Thu, 1 Jun 2017, Xishi Qiu wrote: Cc'ed John Stultz > Hi, this is the test case, and then I got ubsan error > (signed integer overflow) report, so the root cause is from > user or kernel? Shall we change something in timeval_valid()? > > > struct itimerval new_value; > int ret; > >

[RFC] ubsan: signed integer overflow in setitimer()

2017-06-01 Thread Xishi Qiu
Hi, this is the test case, and then I got ubsan error (signed integer overflow) report, so the root cause is from user or kernel? Shall we change something in timeval_valid()? struct itimerval new_value; int ret; new_value.it_interval.tv_sec = 140673496649799L; new_value.it_interval.tv_usec =

[RFC] ubsan: signed integer overflow in setitimer()

2017-06-01 Thread Xishi Qiu
Hi, this is the test case, and then I got ubsan error (signed integer overflow) report, so the root cause is from user or kernel? Shall we change something in timeval_valid()? struct itimerval new_value; int ret; new_value.it_interval.tv_sec = 140673496649799L; new_value.it_interval.tv_usec =