{"push_id":1051186390,"size":67,"distinct_size":67,"ref":"refs/heads/aosp-3.4-updates","head":"fcaa3d0b8b4a32e0f2e5e27d2a5885abe1398d00","before":"9b389946270aa75c4735d59077813ac2c11dc502","commits":[{"sha":"debeeed3e383db4800af8f53575828697a49c1a5","author":{"email":"1ff1d5ceb421971f93e6626b02a9591b29d7600e@thejh.net","name":"Jann Horn"},"message":"fs: take i_mutex during prepare_binprm for set[ug]id executables\n\ncommit 8b01fc86b9f425899f8a3a8fc1c47d73c2c20543 upstream.\n\nThis prevents a race between chown() and execve(), where chowning a\nsetuid-user binary to root would momentarily make the binary setuid\nroot.\n\nThis patch was mostly written by Linus Torvalds.\n\nChange-Id: I1535a9dc4d9fd2de0f1670ea647929c44240095a\nSigned-off-by: Jann Horn <jann@thejh.net>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n[lizf: Backported to 3.4:\n - adjust context\n - remove task_no_new_priv and user namespace stuff\n - open-code file_inode()\n - s/READ_ONCE/ACCESS_ONCE]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/debeeed3e383db4800af8f53575828697a49c1a5"},{"sha":"8f8c2cd84de788c31ad323c6f619f0cd290b7df1","author":{"email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org","name":"Kees Cook"},"message":"seccomp: split filter prep from check and apply\n\nIn preparation for adding seccomp locking, move filter creation away\nfrom where it is checked and applied. This will allow for locking where\nno memory allocation is happening. The validation, filter attachment,\nand seccomp mode setting can all happen under the future locks.\n\nFor extreme defensiveness, I've added a BUG_ON check for the calculated\nsize of the buffer allocation in case BPF_MAXINSN ever changes, which\nshouldn't ever happen. The compiler should actually optimize out this\ncheck since the test above it makes it impossible.\n\nSigned-off-by: Kees Cook <keescook@chromium.org>\nReviewed-by: Oleg Nesterov <oleg@redhat.com>\nReviewed-by: Andy Lutomirski <luto@amacapital.net>\n\nConflicts:\n\tkernel/seccomp.c","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/8f8c2cd84de788c31ad323c6f619f0cd290b7df1"},{"sha":"586931d9f4c7340a3c7a4f3a051a56220cc41daf","author":{"email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org","name":"Kees Cook"},"message":"seccomp: introduce writer locking\n\nNormally, task_struct.seccomp.filter is only ever read or modified by\nthe task that owns it (current). This property aids in fast access\nduring system call filtering as read access is lockless.\n\nUpdating the pointer from another task, however, opens up race\nconditions. To allow cross-thread filter pointer updates, writes to the\nseccomp fields are now protected by the sighand spinlock (which is shared\nby all threads in the thread group). Read access remains lockless because\npointer updates themselves are atomic.  However, writes (or cloning)\noften entail additional checking (like maximum instruction counts)\nwhich require locking to perform safely.\n\nIn the case of cloning threads, the child is invisible to the system\nuntil it enters the task list. To make sure a child can't be cloned from\na thread and left in a prior state, seccomp duplication is additionally\nmoved under the sighand lock. Then parent and child are certain have\nthe same seccomp state when they exit the lock.\n\nBased on patches by Will Drewry and David Drysdale.\n\nSigned-off-by: Kees Cook <keescook@chromium.org>\nReviewed-by: Oleg Nesterov <oleg@redhat.com>\nReviewed-by: Andy Lutomirski <luto@amacapital.net>\n\nConflicts:\n\tkernel/fork.c","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/586931d9f4c7340a3c7a4f3a051a56220cc41daf"},{"sha":"ab4ac6e476af76e46e64a736ac71e11070ad772c","author":{"email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org","name":"Kees Cook"},"message":"seccomp: allow mode setting across threads\n\nThis changes the mode setting helper to allow threads to change the\nseccomp mode from another thread. We must maintain barriers to keep\nTIF_SECCOMP synchronized with the rest of the seccomp state.\n\nSigned-off-by: Kees Cook <keescook@chromium.org>\nReviewed-by: Oleg Nesterov <oleg@redhat.com>\nReviewed-by: Andy Lutomirski <luto@amacapital.net>\n\nConflicts:\n\tkernel/seccomp.c","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/ab4ac6e476af76e46e64a736ac71e11070ad772c"},{"sha":"fbbe478c3bd88f4d937821b9e001a9a05bb2ea36","author":{"email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org","name":"Kees Cook"},"message":"seccomp: implement SECCOMP_FILTER_FLAG_TSYNC\n\nApplying restrictive seccomp filter programs to large or diverse\ncodebases often requires handling threads which may be started early in\nthe process lifetime (e.g., by code that is linked in). While it is\npossible to apply permissive programs prior to process start up, it is\ndifficult to further restrict the kernel ABI to those threads after that\npoint.\n\nThis change adds a new seccomp syscall flag to SECCOMP_SET_MODE_FILTER for\nsynchronizing thread group seccomp filters at filter installation time.\n\nWhen calling seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC,\nfilter) an attempt will be made to synchronize all threads in current's\nthreadgroup to its new seccomp filter program. This is possible iff all\nthreads are using a filter that is an ancestor to the filter current is\nattempting to synchronize to. NULL filters (where the task is running as\nSECCOMP_MODE_NONE) are also treated as ancestors allowing threads to be\ntransitioned into SECCOMP_MODE_FILTER. If prctrl(PR_SET_NO_NEW_PRIVS,\n...) has been set on the calling thread, no_new_privs will be set for\nall synchronized threads too. On success, 0 is returned. On failure,\nthe pid of one of the failing threads will be returned and no filters\nwill have been applied.\n\nThe race conditions against another thread are:\n- requesting TSYNC (already handled by sighand lock)\n- performing a clone (already handled by sighand lock)\n- changing its filter (already handled by sighand lock)\n- calling exec (handled by cred_guard_mutex)\nThe clone case is assisted by the fact that new threads will have their\nseccomp state duplicated from their parent before appearing on the tasklist.\n\nHolding cred_guard_mutex means that seccomp filters cannot be assigned\nwhile in the middle of another thread's exec (potentially bypassing\nno_new_privs or similar). The call to de_thread() may kill threads waiting\nfor the mutex.\n\nChanges across threads to the filter pointer includes a barrier.\n\nBased on patches by Will Drewry.\n\nSuggested-by: Julien Tinnes <jln@chromium.org>\nSigned-off-by: Kees Cook <keescook@chromium.org>\nReviewed-by: Oleg Nesterov <oleg@redhat.com>\nReviewed-by: Andy Lutomirski <luto@amacapital.net>\n\nConflicts:\n\tinclude/linux/seccomp.h\n\tinclude/uapi/linux/seccomp.h","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/fbbe478c3bd88f4d937821b9e001a9a05bb2ea36"},{"sha":"ec9e5cf62385b62e67f7c95b32cab4464939fc01","author":{"email":"f55ad94e336f3a28322d0a25d280221ea9daf7a3@google.com","name":"Robert Sesek"},"message":"seccomp: Use atomic operations that are present in kernel 3.4.\n\nSigned-off-by: Robert Sesek <rsesek@google.com>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/ec9e5cf62385b62e67f7c95b32cab4464939fc01"},{"sha":"2a137329b751d22b7cd1c839fd92062d60017021","author":{"email":"fb53b2ddb8d141e0cb39d7c67c2f81b6bc2eb0f7@gmail.com","name":"David Herrmann"},"message":"HID: input: generic hidinput_input_event handler\n\nThe hidinput_input_event() callback converts input events written from\nuserspace into HID reports and sends them to the device. We currently\nimplement this in every HID transport driver, even though most of them do\nthe same.\n\nThis provides a generic hidinput_input_event() implementation which is\nmostly copied from usbhid. It uses a delayed worker to allow multiple LED\nevents to be collected into a single output event.\nWe use the custom ->request() transport driver callback to allow drivers\nto adjust the outgoing report and handle the request asynchronously. If no\ncustom ->request() callback is available, we fall back to the generic raw\noutput report handler (which is synchronous).\n\nDrivers can still provide custom hidinput_input_event() handlers (see\nlogitech-dj) if the generic implementation doesn't fit their needs.\n\nConflicts:\n\tdrivers/hid/hid-input.c\n\nSigned-off-by: David Herrmann <dh.herrmann@gmail.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>\nSigned-off-by: Michael Wright <michaelwr@google.com>\nChange-Id: I89ccc3f675b3e8a7bbd812a6ebe12588d737cfd6","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/2a137329b751d22b7cd1c839fd92062d60017021"},{"sha":"23dd11c0fb95223e95abbe6eceae0a360c3ea16e","author":{"email":"380081620a7947c89c11153c5513f34019caa923@android.com","name":"Colin Cross"},"message":"freezer: shorten freezer sleep time using exponential backoff\n\nAll tasks can easily be frozen in under 10 ms, switch to using\nan initial 1 ms sleep followed by exponential backoff until\n8 ms.  Also convert the printed time to ms instead of centiseconds.\n\nChange-Id: I7b198b16eefb623c2b0fc45dce50d9bca320afdc\nAcked-by: Pavel Machek <pavel@ucw.cz>\nAcked-by: Tejun Heo <tj@kernel.org>\nSigned-off-by: Colin Cross <ccross@android.com>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/23dd11c0fb95223e95abbe6eceae0a360c3ea16e"},{"sha":"8e3762bd7dc6d677dc40d3d7cee99bb6ac922ada","author":{"email":"ff359ca7f9aedbb05cd6aa3d17e7b3b3ad3b25c9@google.com","name":"Ruchi Kandoi"},"message":"power: Avoids bogus error messages for the suspend aborts.\n\nAvoids printing bogus error message \"tasks refusing to freeze\", in cases\nwhere pending wakeup source caused the suspend abort.\n\nSigned-off-by: Ruchi Kandoi <kandoiruchi@google.com>\nChange-Id: I913ad290f501b31cd536d039834c8d24c6f16928","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/8e3762bd7dc6d677dc40d3d7cee99bb6ac922ada"},{"sha":"075a80c344a4a3302fd25cd64cf0883995d8b5df","author":{"email":"110fdadc76b6bce16977f568bdb4723eaed6fb3f@gentoo.org","name":"Sergei Trofimovich"},"message":"um: add missing declaration of 'getrlimit()' and friends\n\ncommit fdfa4c952844fce881df8c76de9c7180cbe913ab upstream.\ncommit 809d29070ffcf808e86f37e9e1971cd2b8caaf49 in stable/3.4.y.\n\narch/um/os-Linux/start_up.c: In function 'check_coredump_limit':\narch/um/os-Linux/start_up.c:338:16: error: storage size of 'lim' isn't known\narch/um/os-Linux/start_up.c:339:2: error: implicit declaration of function 'getrlimit' [-Werror=implicit-function-declaration]\n\nBug: 15413527\nChange-Id: I81d930d9636bfc95e0c2140f2901628dc609df79\nSigned-off-by: Sergei Trofimovich <slyfox@gentoo.org>\nCC: Jeff Dike <jdike@addtoit.com>\nCC: Richard Weinberger <richard@nod.at>\nCC: Al Viro <viro@zeniv.linux.org.uk>\nCC: user-mode-linux-devel@lists.sourceforge.net\nCC: user-mode-linux-user@lists.sourceforge.net\nCC: linux-kernel@vger.kernel.org\nSigned-off-by: Richard Weinberger <richard@nod.at>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/075a80c344a4a3302fd25cd64cf0883995d8b5df"},{"sha":"8888eee3580a83bfd9686b7e88fd24912e57d901","author":{"email":"30ac7e9d34cbeb0437860186ca5724301c19a274@android.com","name":"Rom Lemarchand"},"message":"staging: android: ashmem: add missing include\n\nInclude <linux/types.h> into ashmem.h to ensure referenced types are defined\n\nSigned-off-by: Rom Lemarchand <romlem@android.com>\nChange-Id: If82d92caa6c148ab2182a681637fc8e17c44346d","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/8888eee3580a83bfd9686b7e88fd24912e57d901"},{"sha":"74d7cea0a6e85ddd3c4673dedfd687a03ed51d7b","author":{"email":"cdd9fa42ea415a7599cd10720eaffbcd5c02e90a@chromium.org","name":"Petr Cermak"},"message":"fs/proc/task_mmu.c: add user-space support for resetting mm->hiwater_rss (peak RSS)\n\nPeak resident size of a process can be reset back to the process's\ncurrent rss value by writing \"5\" to /proc/pid/clear_refs.  The driving\nuse-case for this would be getting the peak RSS value, which can be\nretrieved from the VmHWM field in /proc/pid/status, per benchmark\niteration or test scenario.\n\nOrigin:\nhttps://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=695f055936938c674473ea071ca7359a863551e7\n\n[akpm@linux-foundation.org: clarify behaviour in documentation]\nSigned-off-by: Petr Cermak <petrcermak@chromium.org>\nCc: Bjorn Helgaas <bhelgaas@google.com>\nCc: Primiano Tucci <primiano@chromium.org>\nCc: Petr Cermak <petrcermak@chromium.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nChange-Id: I06f83ce2d3d003ff67aced16d2710e4f88eb3af4","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/74d7cea0a6e85ddd3c4673dedfd687a03ed51d7b"},{"sha":"73968e33f8fd33c5a39fc4646f326ab3c2b27858","author":{"email":"86995a091f8a1385082bd10715048b52ee386a6a@google.com","name":"Lorenzo Colitti"},"message":"net: ipv6: make \"ip -6 route get mark xyz\" work.\n\nCurrently, \"ip -6 route get mark xyz\" ignores the mark passed in\nby userspace. Make it honour the mark, just like IPv4 does.\n\n[net-next commit 2e47b291953c35afa4e20a65475954c1a1b9afe1]\n\nChange-Id: Ief6cd1e1b7e43dc0d008b7e692be62cadc5cc7ca\nSigned-off-by: Lorenzo Colitti <lorenzo@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/73968e33f8fd33c5a39fc4646f326ab3c2b27858"},{"sha":"8f4792752e8108d238d67dbc49b71da802eec586","author":{"email":"30ac7e9d34cbeb0437860186ca5724301c19a274@android.com","name":"Rom Lemarchand"},"message":"Revert \"Grants system server access to /proc/<pid>/oom_adj for Android applications.\"\n\nThis reverts commit aa3305f2ba5976a95637c69c63409fdf007e1414.\n\nBug: 19636629\nChange-Id: I1b8ff0f71dd60c7c17faf2de371ef6a2ce9e5f96","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/8f4792752e8108d238d67dbc49b71da802eec586"},{"sha":"51c0d42dd90973759043aaf0ce7135ba1d1bbf2e","author":{"email":"30ac7e9d34cbeb0437860186ca5724301c19a274@android.com","name":"Rom Lemarchand"},"message":"proc: make oom adjustment files user read-only\n\nMake oom_adj and oom_score_adj user read-only.\n\nBug: 19636629\nChange-Id: I055bb172d5b4d3d856e25918f3c5de8edf31e4a3\nSigned-off-by: Rom Lemarchand <romlem@google.com>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/51c0d42dd90973759043aaf0ce7135ba1d1bbf2e"},{"sha":"8a7b8967612195b2ffa151123d82f1395a9e0ef0","author":{"email":"7864bb1e0e12322ea18ea731d051b95b75140567@6wind.com","name":"Nicolas Dichtel"},"message":"selinux/nlmsg: add XFRM_MSG_NEWSPDINFO\n\ncommit 2b7834d3e1b828429faa5dc41a480919e52d3f31 upstream (net-next).\n\nThis new command is missing.\n\nChange-Id: If511000c19aa9af7220ff775d88ace9834b35dcb\nFixes: 880a6fab8f6b (\"xfrm: configure policy hash table thresholds by netlink\")\nReported-by: Christophe Gouault <christophe.gouault@6wind.com>\nSigned-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/8a7b8967612195b2ffa151123d82f1395a9e0ef0"},{"sha":"a5e6e9edda2a8ac5579fa3bd12d4d7ed50738d33","author":{"email":"88a1d58bf22a647dce58dd91f9595600dceabba9@redhat.com","name":"Paul Moore"},"message":"selinux: add SOCK_DIAG_BY_FAMILY to the list of netlink message types\n\ncommit 6a96e15096da6e7491107321cfa660c7c2aa119d upstream.\n\nThe SELinux AF_NETLINK/NETLINK_SOCK_DIAG socket class was missing the\nSOCK_DIAG_BY_FAMILY definition which caused SELINUX_ERR messages when\nthe ss tool was run.\n\n # ss\n Netid  State  Recv-Q Send-Q  Local Address:Port   Peer Address:Port\n u_str  ESTAB  0      0                  * 14189             * 14190\n u_str  ESTAB  0      0                  * 14145             * 14144\n u_str  ESTAB  0      0                  * 14151             * 14150\n {...}\n # ausearch -m SELINUX_ERR\n ----\n time->Thu Jan 23 11:11:16 2014\n type=SYSCALL msg=audit(1390493476.445:374):\n  arch=c000003e syscall=44 success=yes exit=40\n  a0=3 a1=7fff03aa11f0 a2=28 a3=0 items=0 ppid=1852 pid=1895\n  auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0\n  tty=pts0 ses=1 comm=\"ss\" exe=\"/usr/sbin/ss\"\n  subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=(null)\n type=SELINUX_ERR msg=audit(1390493476.445:374):\n  SELinux:  unrecognized netlink message type=20 for sclass=32\n\nChange-Id: I22218ec620bc3ee6396145f1c2ad8ed222648309\nSigned-off-by: Paul Moore <pmoore@redhat.com>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/a5e6e9edda2a8ac5579fa3bd12d4d7ed50738d33"},{"sha":"810d48175390a070a01bc4a4894092f18b01dffa","author":{"email":"2a6854f3b9949c43de11e7c9c8445bf4929ab953@spreadtrum.com","name":"rahul.khandelwal"},"message":"subsystem: CPU FREQUENCY DRIVERS- Set cpu_load calculation on current frequency\n\nIn timer, cpu_load is calcuated on target_freq.\ncpu_load = loadadjfreq / pcpu->target_freq;\nBut cpu is actually running on current freq i.e. pcpu->policy->cur. So cpu_load\nshould be calculated on current frequency.\ncpu_load = loadadjfreq / pcpu->policy->cur;\n\nChange-Id: I89db6b68e9f82aa52077f6bf7d819dab74265790\nSigned-off-by: rahul.khandelwal <rahul.khandelwal@spreadtrum.com>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/810d48175390a070a01bc4a4894092f18b01dffa"},{"sha":"d01b2c8f4a6f63aaaf4688b41321304b40a01b33","author":{"email":"ba324ca7b1c77fc20bb970d5aff6eea9377918a5@roeck-us.net","name":"Guenter Roeck"},"message":"seccomp: Replace BUG(!spin_is_locked()) with assert_spin_lock\n\nCurrent upstream kernel hangs with mips and powerpc targets in\nuniprocessor mode if SECCOMP is configured.\n\nBisect points to commit dbd952127d11 (\"seccomp: introduce writer locking\").\nTurns out that code such as\n\tBUG_ON(!spin_is_locked(&list_lock));\ncan not be used in uniprocessor mode because spin_is_locked() always\nreturns false in this configuration, and that assert_spin_locked()\nexists for that very purpose and must be used instead.\n\nFixes: dbd952127d11 (\"seccomp: introduce writer locking\")\nCc: Kees Cook <keescook@chromium.org>\nSigned-off-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Kees Cook <keescook@chromium.org>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/d01b2c8f4a6f63aaaf4688b41321304b40a01b33"},{"sha":"3cff11886cbb7850b24c27a71adeffe705b8e3e0","author":{"email":"ff359ca7f9aedbb05cd6aa3d17e7b3b3ad3b25c9@google.com","name":"Ruchi Kandoi"},"message":"suspend: Return error when pending wakeup source is found.\n\nIf a wakeup source is found to be pending in the last stage of suspend\nafter syscore suspend then the device doesn't suspend but the error is\nnot propogated which causes an error in the accounting for the number\nof suspend aborts and successful suspends.\n\nChange-Id: Ib63b4ead755127eaf03e3b303aab3c782ad02ed1\nSigned-off-by: Ruchi Kandoi <kandoiruchi@google.com>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/3cff11886cbb7850b24c27a71adeffe705b8e3e0"}]}