| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4B222771.7010901@suse.cz> Date: Fri, 11 Dec 2009 12:05:21 +0100 From: Jiri Slaby <jslaby@...e.cz> To: Linus Torvalds <torvalds@...ux-foundation.org> CC: LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>, Neil Horman <nhorman@...driver.com>, Oleg Nesterov <oleg@...hat.com> Subject: [git pull -resend] pull request for writable limits for 2.6.33-rc0 Hi, is there something wrong with the patchset? Did the email make it into your inbox at all? On 12/09/2009 08:25 PM, Jiri Slaby wrote: > Hi, > > I messed up the subject last time. > > Now I rebased the tree to resolve conflicts, please pull. > > --- > The following changes since commit 2588465badb648a50cd19623f0dd0063c90d4e31: > Linus Torvalds (1): > Merge branch 'bkl-arch-for-linus' of > git://git.kernel.org/.../tip/linux-2.6-tip > > are available in the git repository at: > > git://decibel.fi.muni.cz/~xslaby/linux writable_limits > > Jiri Slaby (25): > SECURITY: selinux, fix update_rlimit_cpu parameter > SECURITY: add task_struct to setrlimit > core: add task_struct to update_rlimit_cpu > core: split sys_setrlimit > core: allow setrlimit to non-current tasks > core: optimize setrlimit for current task > FS: proc, switch limits reading to fops > FS: proc, make limits writable > core: do security check under task_lock > core: rename setrlimit to do_setrlimit > resource: move kernel functions inside __KERNEL__ > core: posix-cpu-timers, cleanup rlimits usage > resource: add helpers for fetching rlimits > IA64: use helpers for rlimits > PPC: use helpers for rlimits > S390: use helpers for rlimits > SPARC: use helpers for rlimits > X86: use helpers for rlimits > FS: use helpers for rlimits > MM: use helpers for rlimits > core: use helpers for rlimits > misc: use helpers for rlimits > core: implement getprlimit and setprlimit syscalls > COMPAT: add get/put_compat_rlimit > x86: add ia32 compat prlimit syscalls > > Neil Horman (1): > unistd: add __NR_[get|set]prlimit syscall numbers > > Oleg Nesterov (1): > sys_setrlimit: make sure ->rlim_max never grows > > arch/ia64/kernel/perfmon.c | 2 +- > arch/ia64/kernel/sys_ia64.c | 2 +- > arch/ia64/mm/init.c | 2 +- > arch/powerpc/mm/mmap_64.c | 4 +- > arch/powerpc/platforms/cell/spufs/coredump.c | 2 +- > arch/s390/mm/mmap.c | 4 +- > arch/sparc/kernel/sys_sparc_64.c | 6 +- > arch/x86/ia32/ia32_aout.c | 2 +- > arch/x86/ia32/ia32entry.S | 2 + > arch/x86/include/asm/unistd_32.h | 4 +- > arch/x86/include/asm/unistd_64.h | 4 + > arch/x86/kernel/syscall_table_32.S | 2 + > arch/x86/mm/mmap.c | 4 +- > drivers/infiniband/core/umem.c | 2 +- > drivers/infiniband/hw/ipath/ipath_user_pages.c | 3 +- > fs/attr.c | 2 +- > fs/binfmt_aout.c | 2 +- > fs/binfmt_flat.c | 2 +- > fs/exec.c | 8 +- > fs/fcntl.c | 2 +- > fs/file.c | 2 +- > fs/proc/array.c | 4 +- > fs/proc/base.c | 101 ++++++++++++++-- > fs/select.c | 2 +- > include/asm-generic/unistd.h | 6 +- > include/linux/Kbuild | 2 +- > include/linux/posix-timers.h | 2 +- > include/linux/resource.h | 10 ++- > include/linux/sched.h | 22 ++++ > include/linux/security.h | 9 +- > include/linux/syscalls.h | 4 + > ipc/mqueue.c | 2 +- > ipc/shm.c | 3 +- > kernel/compat.c | 91 +++++++++++--- > kernel/fork.c | 10 +- > kernel/perf_event.c | 2 +- > kernel/posix-cpu-timers.c | 52 ++++---- > kernel/sched.c | 4 +- > kernel/sched_rt.c | 5 +- > kernel/signal.c | 2 +- > kernel/sys.c | 161 > +++++++++++++++++++---- > mm/filemap.c | 2 +- > mm/mlock.c | 12 +- > mm/mmap.c | 13 +- > mm/mremap.c | 2 +- > security/capability.c | 3 +- > security/security.c | 5 +- > security/selinux/hooks.c | 10 +- > 48 files changed, 451 insertions(+), 153 deletions(-) -- js suse labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists