[PATCH 3.11 199/233] x86, x32: Correct invalid use of user timespec in the kernel

2014-02-07 Thread Luis Henriques
3.11.10.4 -stable review patch. If anyone has any objections, please let me know. -- From: PaX Team commit 2def2ef2ae5f3990aabdbe8a755911902707d268 upstream. The x32 case for the recvmsg() timout handling is broken: asmlinkage long compat_sys_recvmmsg(int fd, struct compat

[PATCH 3.5 74/88] x86, x32: Correct invalid use of user timespec in the kernel

2014-02-07 Thread Luis Henriques
3.5.7.30 -stable review patch. If anyone has any objections, please let me know. -- From: PaX Team commit 2def2ef2ae5f3990aabdbe8a755911902707d268 upstream. The x32 case for the recvmsg() timout handling is broken: asmlinkage long compat_sys_recvmmsg(int fd, struct compat_

[PATCH 3.4 04/37] x86, x32: Correct invalid use of user timespec in the kernel

2014-02-04 Thread Greg Kroah-Hartman
3.4-stable review patch. If anyone has any objections, please let me know. -- From: PaX Team commit 2def2ef2ae5f3990aabdbe8a755911902707d268 upstream. The x32 case for the recvmsg() timout handling is broken: asmlinkage long compat_sys_recvmmsg(int fd, struct compat_mmsghdr

[PATCH 3.10 009/104] x86, x32: Correct invalid use of user timespec in the kernel

2014-02-04 Thread Greg Kroah-Hartman
3.10-stable review patch. If anyone has any objections, please let me know. -- From: PaX Team commit 2def2ef2ae5f3990aabdbe8a755911902707d268 upstream. The x32 case for the recvmsg() timout handling is broken: asmlinkage long compat_sys_recvmmsg(int fd, struct compat_mmsghd

[PATCH 3.12 008/133] x86, x32: Correct invalid use of user timespec in the kernel

2014-02-04 Thread Greg Kroah-Hartman
3.12-stable review patch. If anyone has any objections, please let me know. -- From: PaX Team commit 2def2ef2ae5f3990aabdbe8a755911902707d268 upstream. The x32 case for the recvmsg() timout handling is broken: asmlinkage long compat_sys_recvmmsg(int fd, struct compat_mmsghd

[PATCH 3.13 003/140] x86, x32: Correct invalid use of user timespec in the kernel

2014-02-04 Thread Greg Kroah-Hartman
3.13-stable review patch. If anyone has any objections, please let me know. -- From: PaX Team commit 2def2ef2ae5f3990aabdbe8a755911902707d268 upstream. The x32 case for the recvmsg() timout handling is broken: asmlinkage long compat_sys_recvmmsg(int fd, struct compat_mmsghd

Re: x86, x32: Correct invalid use of user timespec in the kernel

2014-02-01 Thread Linus Torvalds
On Fri, Jan 31, 2014 at 2:37 PM, H. Peter Anvin wrote: > > Here is a patch for comments/review/opinions... it has only been > compile-tested. Looks sane to me from a superficial quick read-through. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in t

Re: x86, x32: Correct invalid use of user timespec in the kernel

2014-01-31 Thread H. Peter Anvin
On 01/31/2014 10:45 AM, Linus Torvalds wrote: > On Fri, Jan 31, 2014 at 10:06 AM, H. Peter Anvin wrote: >> >> My feeling is that {get,put}_compat_timespec() should at the very least >> have leading underscores to flag it as a low-level function, but better >> suggestions would be appreciated. > >

Re: x86, x32: Correct invalid use of user timespec in the kernel

2014-01-31 Thread H. Peter Anvin
On 01/31/2014 10:45 AM, Linus Torvalds wrote: > On Fri, Jan 31, 2014 at 10:06 AM, H. Peter Anvin wrote: >> >> My feeling is that {get,put}_compat_timespec() should at the very least >> have leading underscores to flag it as a low-level function, but better >> suggestions would be appreciated. > >

Re: x86, x32: Correct invalid use of user timespec in the kernel

2014-01-31 Thread H. Peter Anvin
On 01/31/2014 10:45 AM, Linus Torvalds wrote: > On Fri, Jan 31, 2014 at 10:06 AM, H. Peter Anvin wrote: >> >> My feeling is that {get,put}_compat_timespec() should at the very least >> have leading underscores to flag it as a low-level function, but better >> suggestions would be appreciated. > >

Re: x86, x32: Correct invalid use of user timespec in the kernel

2014-01-31 Thread Linus Torvalds
On Fri, Jan 31, 2014 at 10:06 AM, H. Peter Anvin wrote: > > My feeling is that {get,put}_compat_timespec() should at the very least > have leading underscores to flag it as a low-level function, but better > suggestions would be appreciated. Why not just remove it entirely, and change all users t

Re: x86, x32: Correct invalid use of user timespec in the kernel

2014-01-31 Thread H. Peter Anvin
On 01/31/2014 09:50 AM, Dave Jones wrote: > On Fri, Jan 31, 2014 at 02:54:53AM +, Linux Kernel wrote: > > > Commit: 2def2ef2ae5f3990aabdbe8a755911902707d268 > > > > ... > > > > - if (get_compat_timespec(&ktspec, timeout)) > > + if (compat_get_timespec(&ktspec, timeout)) > >

Re: x86, x32: Correct invalid use of user timespec in the kernel

2014-01-31 Thread Dave Jones
On Fri, Jan 31, 2014 at 02:54:53AM +, Linux Kernel wrote: > Commit: 2def2ef2ae5f3990aabdbe8a755911902707d268 > > ... > > -if (get_compat_timespec(&ktspec, timeout)) > +if (compat_get_timespec(&ktspec, timeout)) > return -EFAULT; > > datagrams = __sys

[PATCH 3.8 14/14] x86, x32: Correct invalid use of user timespec in the kernel

2014-01-31 Thread Kamal Mostafa
3.8.13.17 -stable review patch. If anyone has any objections, please let me know. -- From: PaX Team commit 2def2ef2ae5f3990aabdbe8a755911902707d268 upstream. The x32 case for the recvmsg() timout handling is broken: asmlinkage long compat_sys_recvmmsg(int fd, struct compat