/* * Glibc independent futex library for testing kernel functionality. * Shamelessly stolen from Darren Hart * http://git.kernel.org/cgit/linux/kernel/git/dvhart/futextest.git/ */ #ifndef _FUTEX_H #define _FUTEX_H #include #include #include #include #include /** * futex() - SYS_futex syscall wrapper * @uaddr: address of first futex * @op: futex op code * @val: typically expected value of uaddr, but varies by op * @timeout: typically an absolute struct timespec (except where noted * otherwise). Overloaded by some ops * @uaddr2: address of second futex for some ops\ * @val3: varies by op * @opflags: flags to be bitwise OR'd with op, such as FUTEX_PRIVATE_FLAG * * futex() is used by all the following futex op wrappers. It can also be * used for misuse and abuse testing. Generally, the specific op wrappers * should be used instead. It is a macro instead of an static inline function as * some of the types over overloaded (timeout is used for nr_requeue for * example). * * These argument descriptions are the defaults for all * like-named arguments in the following wrappers except where noted below. */ #define futex(uaddr, op, val, timeout, uaddr2, val3, opflags) \ syscall(SYS_futex, uaddr, op | opflags, val, timeout, uaddr2, val3) /** * futex_wait() - block on uaddr with optional timeout * @timeout: relative timeout */ static inline int futex_wait(u_int32_t *uaddr, u_int32_t val, struct timespec *timeout, int opflags) { return futex(uaddr, FUTEX_WAIT, val, timeout, NULL, 0, opflags); } /** * futex_wake() - wake one or more tasks blocked on uaddr * @nr_wake: wake up to this many tasks */ static inline int futex_wake(u_int32_t *uaddr, int nr_wake, int opflags) { return futex(uaddr, FUTEX_WAKE, nr_wake, NULL, NULL, 0, opflags); } /** * futex_lock_pi() - block on uaddr as a PI mutex */ static inline int futex_lock_pi(u_int32_t *uaddr, struct timespec *timeout, int opflags) { return futex(uaddr, FUTEX_LOCK_PI, 0, timeout, NULL, 0, opflags); } /** * futex_unlock_pi() - release uaddr as a PI mutex, waking the top waiter */ static inline int futex_unlock_pi(u_int32_t *uaddr, int opflags) { return futex(uaddr, FUTEX_UNLOCK_PI, 0, NULL, NULL, 0, opflags); } /** * futex_cmp_requeue() - requeue tasks from uaddr to uaddr2 * @nr_wake: wake up to this many tasks * @nr_requeue: requeue up to this many tasks */ static inline int futex_cmp_requeue(u_int32_t *uaddr, u_int32_t val, u_int32_t *uaddr2, int nr_wake, int nr_requeue, int opflags) { return futex(uaddr, FUTEX_CMP_REQUEUE, nr_wake, nr_requeue, uaddr2, val, opflags); } #ifndef HAVE_PTHREAD_ATTR_SETAFFINITY_NP #include static inline int pthread_attr_setaffinity_np(pthread_attr_t *attr, size_t cpusetsize, cpu_set_t *cpuset) { attr = attr; cpusetsize = cpusetsize; cpuset = cpuset; return 0; } #endif /* User input sanitation */ #define futexbench_sanitize_numeric(__n) abs((__n)) #endif /* _FUTEX_H */ vents?id=54791b276b4000b307339f269d3bf7db877d536f'>events/clk.h
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2017-01-30 14:28:22 -0800
committerDavid S. Miller <davem@davemloft.net>2017-01-30 14:28:22 -0800
commit54791b276b4000b307339f269d3bf7db877d536f (patch)
tree1c2616bd373ce5ea28aac2a53e32f5b5834901ce /include/trace/events/clk.h
parent5d0e7705774dd412a465896d08d59a81a345c1e4 (diff)
parent047487241ff59374fded8c477f21453681f5995c (diff)
Merge branch 'sparc64-non-resumable-user-error-recovery'
Liam R. Howlett says: ==================== sparc64: Recover from userspace non-resumable PIO & MEM errors A non-resumable error from userspace is able to cause a kernel panic or trap loop due to the setup and handling of the queued traps once in the kernel. This patch series addresses both of these issues. The queues are fixed by simply zeroing the memory before use. PIO errors from userspace will result in a SIGBUS being sent to the user process. The MEM errors form userspace will result in a SIGKILL and also cause the offending pages to be claimed so they are no longer used in future tasks. SIGKILL is used to ensure that the process does not try to coredump and result in an attempt to read the memory again from within kernel space. Although there is a HV call to scrub the memory (mem_scrub), there is no easy way to guarantee that the real memory address(es) are not used by other tasks. Clearing the error with mem_scrub would zero the memory and cause the other processes to proceed with bad data. The handling of other non-resumable errors remain unchanged and will cause a panic. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/trace/events/clk.h')