linux-toradex.git/include/linux/compat.h, branch v4.8-rc1

compat: add in_compat_syscall to ask whether we're in a compat syscall

2016-03-22T22:36:02+00:00

A lot of code currently abuses is_compat_task to determine this.

Signed-off-by: Andy Lutomirski 
Cc: "David S. Miller" 
Cc: "H. Peter Anvin" 
Cc: "Theodore Ts'o" 
Cc: Andreas Dilger 
Cc: Clemens Ladisch 
Cc: David Airlie 
Cc: David Herrmann 
Cc: David Miller 
Cc: Dmitry Torokhov 
Cc: Eric Paris 
Cc: Herbert Xu 
Cc: Ingo Molnar 
Acked-by: Jiri Kosina 
Cc: Matt Fleming 
Cc: Neil Horman 
Cc: Oded Gabbay 
Cc: Oleg Drokin 
Cc: Oleg Nesterov 
Cc: Paul Moore 
Cc: Sam Ravnborg 
Cc: Steffen Klassert 
Cc: Thomas Gleixner 
Cc: Vlad Yasevich 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

vfs: vfs: Define new syscalls preadv2,pwritev2

2016-03-04T17:20:10+00:00

New syscalls that take an flag argument.   No flags are added yet in this
patch.

Signed-off-by: Milosz Tanski 
[hch: rebased on top of my kiocb changes]
Signed-off-by: Christoph Hellwig 
Reviewed-by: Stephen Bates 
Tested-by: Stephen Bates 
Acked-by: Jeff Moyer 
Signed-off-by: Al Viro

include, lib: add __printf attributes to several function prototypes

2015-07-17T23:39:53+00:00

Using __printf attributes helps to detect several format string issues
at compile time (even though -Wformat-security is currently disabled in
Makefile).  For example it can detect when formatting a pointer as a
number, like the issue fixed in commit a3fa71c40f18 ("wl18xx: show
rx_frames_per_rates as an array as it really is"), or when the arguments
do not match the format string, c.f.  for example commit 5ce1aca81435
("reiserfs: fix __RASSERT format string").

To prevent similar bugs in the future, add a __printf attribute to every
function prototype which needs one in include/linux/ and lib/.  These
functions were mostly found by using gcc's -Wsuggest-attribute=format
flag.

Signed-off-by: Nicolas Iooss 
Cc: Greg Kroah-Hartman 
Cc: Felipe Balbi 
Cc: Joel Becker 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

compat: Declare compat_sys_sigpending and compat_sys_sigprocmask prototypes

2015-01-27T09:37:53+00:00

__ARCH_WANT_SYS_SIGPENDING or __ARCH_WANT_SYS_SIGPROGMASK may be defined
for compat support but the corresponding prototypes are missing from
linux/compat.h.

Signed-off-by: Catalin Marinas 
Acked-by: Andrew Morton 
Cc: Arnd Bergmann

syscalls: implement execveat() system call

2014-12-13T20:42:51+00:00

This patchset adds execveat(2) for x86, and is derived from Meredydd
Luff's patch from Sept 2012 (https://lkml.org/lkml/2012/9/11/528).

The primary aim of adding an execveat syscall is to allow an
implementation of fexecve(3) that does not rely on the /proc filesystem,
at least for executables (rather than scripts).  The current glibc version
of fexecve(3) is implemented via /proc, which causes problems in sandboxed
or otherwise restricted environments.

Given the desire for a /proc-free fexecve() implementation, HPA suggested
(https://lkml.org/lkml/2006/7/11/556) that an execveat(2) syscall would be
an appropriate generalization.

Also, having a new syscall means that it can take a flags argument without
back-compatibility concerns.  The current implementation just defines the
AT_EMPTY_PATH and AT_SYMLINK_NOFOLLOW flags, but other flags could be
added in future -- for example, flags for new namespaces (as suggested at
https://lkml.org/lkml/2006/7/11/474).

Related history:
 - https://lkml.org/lkml/2006/12/27/123 is an example of someone
   realizing that fexecve() is likely to fail in a chroot environment.
 - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514043 covered
   documenting the /proc requirement of fexecve(3) in its manpage, to
   "prevent other people from wasting their time".
 - https://bugzilla.redhat.com/show_bug.cgi?id=241609 described a
   problem where a process that did setuid() could not fexecve()
   because it no longer had access to /proc/self/fd; this has since
   been fixed.

This patch (of 4):

Add a new execveat(2) system call.  execveat() is to execve() as openat()
is to open(): it takes a file descriptor that refers to a directory, and
resolves the filename relative to that.

In addition, if the filename is empty and AT_EMPTY_PATH is specified,
execveat() executes the file to which the file descriptor refers.  This
replicates the functionality of fexecve(), which is a system call in other
UNIXen, but in Linux glibc it depends on opening "/proc/self/fd/" (and
so relies on /proc being mounted).

The filename fed to the executed program as argv[0] (or the name of the
script fed to a script interpreter) will be of the form "/dev/fd/"
(for an empty filename) or "/dev/fd//", effectively
reflecting how the executable was found.  This does however mean that
execution of a script in a /proc-less environment won't work; also, script
execution via an O_CLOEXEC file descriptor fails (as the file will not be
accessible after exec).

Based on patches by Meredydd Luff.

Signed-off-by: David Drysdale 
Cc: Meredydd Luff 
Cc: Shuah Khan 
Cc: "Eric W. Biederman" 
Cc: Andy Lutomirski 
Cc: Alexander Viro 
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Cc: "H. Peter Anvin" 
Cc: Kees Cook 
Cc: Arnd Bergmann 
Cc: Rich Felker 
Cc: Christoph Hellwig 
Cc: Michael Kerrisk 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Merge branch 'x86-x32-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

2014-04-02T19:51:41+00:00

Pull compat time conversion changes from Peter Anvin:
 "Despite the branch name this is really neither an x86 nor an
  x32-specific patchset, although it the implementation of the
  discussions that followed the x32 security hole a few months ago.

  This removes get/put_compat_timespec/val() and replaces them with
  compat_get/put_timespec/val() which are savvy as to the current status
  of COMPAT_USE_64BIT_TIME.

  It removes several unused and/or incorrect/misleading functions (like
  compat_put_timeval_convert which doesn't in fact do any conversion)
  and also replaces several open-coded implementations what is now
  called compat_convert_timespec() with that function"

* 'x86-x32-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
  compat: Fix sparse address space warnings
  compat: Get rid of (get|put)_compat_time(val|spec)

compat: include linux/unistd.h within linux/compat.h

2014-03-20T15:42:14+00:00

linux/compat.h does not include linux/unistd.h but the compat.h header
file contains various conditional

 #ifdef __ARCH_WANT_COMPAT_...
 asmlinkage long compat...()
 #endif

compat system call function declarations.
If linux/unistd.h isn't included it depends on previous includes if those
__ARCH_WANT_COMPAT_... defines are defined or not. So add an additional
linux/unistd.h include.

Should fix this compile error on tile:

include/uapi/asm-generic/unistd.h:195:1: error: 'compat_sys_getdents64' undeclared
make[3]: *** [arch/tile/kernel/compat.o] Error 1

Reported-by: Geert Uytterhoeven 
Acked-by: Geert Uytterhoeven 
Acked-by: Chris Metcalf 
Signed-off-by: Heiko Carstens

mm/compat: convert to COMPAT_SYSCALL_DEFINE with changing parameter types

2014-03-06T15:30:47+00:00

In order to allow the COMPAT_SYSCALL_DEFINE macro generate code that
performs proper zero and sign extension convert all 64 bit parameters
to their corresponding 32 bit compat counterparts.

Signed-off-by: Heiko Carstens

kexec/compat: convert to COMPAT_SYSCALL_DEFINE with changing parameter types

2014-03-06T15:30:46+00:00

In order to allow the COMPAT_SYSCALL_DEFINE macro generate code that
performs proper zero and sign extension convert all 64 bit parameters
to their corresponding 32 bit compat counterparts.

Signed-off-by: Heiko Carstens

net/compat: convert to COMPAT_SYSCALL_DEFINE with changing parameter types

2014-03-06T15:30:45+00:00

In order to allow the COMPAT_SYSCALL_DEFINE macro generate code that
performs proper zero and sign extension convert all 64 bit parameters
to their corresponding 32 bit compat counterparts.

Signed-off-by: Heiko Carstens