Re: [PATCH net-next 1/5] pppoe: fix PPPOEIOCSFWD compat handling

2018-08-30 Thread Guillaume Nault
On Wed, Aug 29, 2018 at 04:03:26PM +0200, Arnd Bergmann wrote: > Support for handling the PPPOEIOCSFWD ioctl in compat mode was added in > linux-2.5.69 along with hundreds of other commands, but was always broken > sincen only the structure is compatible, but the command number is not, > due to

Re: [PATCH net-next 4/5] ppp: move PPPIOCSPASS32/PPPIOCSACTIVE32 to ppp_generic.c

2018-08-30 Thread Guillaume Nault
On Wed, Aug 29, 2018 at 04:03:29PM +0200, Arnd Bergmann wrote: > PPPIOCSPASS and PPPIOCSACTIVE are implemented in ppp_generic and isdn_ppp, > but the latter one doesn't work for compat mode in general, so we can > move these two into the generic code. > > Again, the best implementation I could

Re: [PATCH net-next 3/5] ppp: move PPPIOCSCOMPRESS32 to ppp-generic.c

2018-08-30 Thread Guillaume Nault
On Wed, Aug 29, 2018 at 04:03:28PM +0200, Arnd Bergmann wrote: > PPPIOCSCOMPRESS is only implemented in ppp_generic, so it's best to move > the compat handling there. My first approach was to keep it in a new > ppp_compat_ioctl() function, but it turned out to be much simpler to do > it in the

Re: [PATCH net-next 5/5] ppp: handle PPPIOCGIDLE for 64-bit time_t

2018-08-30 Thread Guillaume Nault
On Wed, Aug 29, 2018 at 04:03:30PM +0200, Arnd Bergmann wrote: > The ppp_idle structure is defined in terms of __kernel_time_t, which is > defined as 'long' on all architectures, and this usage is not affected > by the y2038 problem since it transports a time interval rather than an > absolute

Re: [PATCH net-next 5/5] ppp: handle PPPIOCGIDLE for 64-bit time_t

2018-08-30 Thread Arnd Bergmann
On Thu, Aug 30, 2018 at 1:06 PM Guillaume Nault wrote: > On Wed, Aug 29, 2018 at 04:03:30PM +0200, Arnd Bergmann wrote: > > @@ -743,10 +744,17 @@ static long ppp_ioctl(struct file *file, unsigned int > > cmd, unsigned long arg) > > err = 0; > > break; > > > > -