{"push_id":1362270278,"size":95,"distinct_size":95,"ref":"refs/heads/OOS-X","head":"b21b59693c9788eb7579d7f391855be7d351c49e","before":"e15fbae4a4b2df0591c7821d85456c79ba972001","commits":[{"sha":"cc05a7c828f6360053cf3ba0f32b1b2fa98f76f3","author":{"name":"Sultanxda","email":"2a26fc11866c4c85a6bb605251817c00bbab3213@gmail.com"},"message":"ARM: dts: 15055: Disable second crypto device\n\nCan cause instability.","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/cc05a7c828f6360053cf3ba0f32b1b2fa98f76f3"},{"sha":"ba91824bcb970f92bd377786a75db1345e95e37f","author":{"name":"Dov Levenglick","email":"08ca4f65a24904ac5fa2e9cad46c299ec52c9a4f@codeaurora.org"},"message":"mmc: add support for scheduling mmcqd on idle CPU\n\nIn order to boost mmc performance on various platforms,\nadd support for configuring whether set_wake_up_idle()\nshould be called on the mmc queue thread (mmcqd)\nThe decision will be set in each individual platform's\ndts file.\n\nCRs-Fixed: 787554\nChange-Id: I3989d3f5b8228785e6d3bc49c7eb01ebf2fa2f38\nSigned-off-by: Dov Levenglick <dovl@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/ba91824bcb970f92bd377786a75db1345e95e37f"},{"sha":"d7853a4740f7e1216c3f2d7a36668b005d0c81f3","author":{"name":"Sultanxda","email":"2a26fc11866c4c85a6bb605251817c00bbab3213@gmail.com"},"message":"ARM: dts: 15055: Schedule mmcqd on idle CPU","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/d7853a4740f7e1216c3f2d7a36668b005d0c81f3"},{"sha":"c1791a9ac7e394e829dd5104dfec25c5a1f843d9","author":{"name":"Stephen Smalley","email":"a113c662ba7e86bc1a8f97e28bfedcdc6b0de5bd@tycho.nsa.gov"},"message":"Enable setting security contexts on rootfs inodes.\n\nrootfs (ramfs) can support setting of security contexts\nby userspace due to the vfs fallback behavior of calling\nthe security module to set the in-core inode state\nfor security.* attributes when the filesystem does not\nprovide an xattr handler.  No xattr handler required\nas the inodes are pinned in memory and have no backing\nstore.\n\nThis is useful in allowing early userspace to label individual\nfiles within a rootfs while still providing a policy-defined\ndefault via genfs.\n\nChange-Id: Iea1998cdeabcdb09036c5ca36b9d16d24bae4a2e\nSigned-off-by: Stephen Smalley <sds@tycho.nsa.gov>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/c1791a9ac7e394e829dd5104dfec25c5a1f843d9"},{"sha":"9e3bc37fe7bd41d11f133e0c46b49ef7dbb9bcd8","author":{"name":"Stephen Smalley","email":"a113c662ba7e86bc1a8f97e28bfedcdc6b0de5bd@tycho.nsa.gov"},"message":"selinux: fix inode security list corruption\n\ncommit 923190d32de4428afbea5e5773be86bea60a9925 upstream.\n\nsb_finish_set_opts() can race with inode_free_security()\nwhen initializing inode security structures for inodes\ncreated prior to initial policy load or by the filesystem\nduring ->mount().   This appears to have always been\na possible race, but commit 3dc91d4 (\"SELinux:  Fix possible\nNULL pointer dereference in selinux_inode_permission()\")\nmade it more evident by immediately reusing the unioned\nlist/rcu element  of the inode security structure for call_rcu()\nupon an inode_free_security().  But the underlying issue\nwas already present before that commit as a possible use-after-free\nof isec.\n\nShivnandan Kumar reported the list corruption and proposed\na patch to split the list and rcu elements out of the union\nas separate fields of the inode_security_struct so that setting\nthe rcu element would not affect the list element.  However,\nthis would merely hide the issue and not truly fix the code.\n\nThis patch instead moves up the deletion of the list entry\nprior to dropping the sbsec->isec_lock initially.  Then,\nif the inode is dropped subsequently, there will be no further\nreferences to the isec.\n\nChange-Id: I7c56670bddbb896f159701651758d2e7f739dff8\nReported-by: Shivnandan Kumar <shivnandan.k@samsung.com>\nSigned-off-by: Stephen Smalley <sds@tycho.nsa.gov>\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/9e3bc37fe7bd41d11f133e0c46b49ef7dbb9bcd8"},{"sha":"bc5016ce0933aab8c1ff01d366afcd2cb2a72291","author":{"name":"Paul Moore","email":"b6fa22eec98a4c8b84fe025c1540e1eb27210cc2@redhat.com"},"message":"selinux: correctly label /proc inodes in use before the policy is loaded\n\ncommit f64410ec665479d7b4b77b7519e814253ed0f686 upstream.\n\nThis patch is based on an earlier patch by Eric Paris, he describes\nthe problem below:\n\n  \"If an inode is accessed before policy load it will get placed on a\n   list of inodes to be initialized after policy load.  After policy\n   load we call inode_doinit() which calls inode_doinit_with_dentry()\n   on all inodes accessed before policy load.  In the case of inodes\n   in procfs that means we'll end up at the bottom where it does:\n\n     /* Default to the fs superblock SID. */\n     isec->sid = sbsec->sid;\n\n     if ((sbsec->flags & SE_SBPROC) && !S_ISLNK(inode->i_mode)) {\n             if (opt_dentry) {\n                     isec->sclass = inode_mode_to_security_class(...)\n                     rc = selinux_proc_get_sid(opt_dentry,\n                                               isec->sclass,\n                                               &sid);\n                     if (rc)\n                             goto out_unlock;\n                     isec->sid = sid;\n             }\n     }\n\n   Since opt_dentry is null, we'll never call selinux_proc_get_sid()\n   and will leave the inode labeled with the label on the superblock.\n   I believe a fix would be to mimic the behavior of xattrs.  Look\n   for an alias of the inode.  If it can't be found, just leave the\n   inode uninitialized (and pick it up later) if it can be found, we\n   should be able to call selinux_proc_get_sid() ...\"\n\nOn a system exhibiting this problem, you will notice a lot of files in\n/proc with the generic \"proc_t\" type (at least the ones that were\naccessed early in the boot), for example:\n\n   # ls -Z /proc/sys/kernel/shmmax | awk '{ print $4 \" \" $5 }'\n   system_u:object_r:proc_t:s0 /proc/sys/kernel/shmmax\n\nHowever, with this patch in place we see the expected result:\n\n   # ls -Z /proc/sys/kernel/shmmax | awk '{ print $4 \" \" $5 }'\n   system_u:object_r:sysctl_kernel_t:s0 /proc/sys/kernel/shmmax\n\nChange-Id: I7742b4b7e53b45e4dd13d99c39553a927aa4a7e9\nCc: Eric Paris <eparis@redhat.com>\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nAcked-by: Eric Paris <eparis@redhat.com>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/bc5016ce0933aab8c1ff01d366afcd2cb2a72291"},{"sha":"6b5eabf893b54f0954e4dfa175d69398e137d464","author":{"name":"myfluxi","email":"95ab61bb01957fc548ef82d227666a28af3268a6@arcor.de"},"message":"msm: watchdog_v2: Print IRQ in bark handler\n\nChange-Id: I360b5741560b0bbbe846ab8b4fbc792bf9c3a35d","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/6b5eabf893b54f0954e4dfa175d69398e137d464"},{"sha":"cf423daecf96e312b08e4caad6af2a704ed50ff9","author":{"name":"Rusty Russell","email":"69f5932eb9977dcad4aeec4104f9f99d5dd1ae66@rustcorp.com.au"},"message":"kernel/hz.bc: ignore.\n\nChange-Id: I96e5465162eec64287b715b5e0df726a2636194d\nSigned-off-by: Rusty Russell <rusty@rustcorp.com.au>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/cf423daecf96e312b08e4caad6af2a704ed50ff9"},{"sha":"7a00651b94981575e7d79981c3c5dfe80124f103","author":{"name":"Devin Kim","email":"0108bb970c5015e8e018e4b54c1b585cb65b4984@lge.com"},"message":"mmc: workaround for read ahead issue\n\nWhen the sequential read is interrupted by a special operation (RPMB access,\nSecure Erase and Secure Trim) the read ahead feature does not function as\nintended. In that case, data from special operation is not removed from the\ninternal buffer. So when we read the next address, the reading data from the\nprevious operation instead of the address.\n\nTo avoid the issue, add dummy read and ignore the data in that case.\n\nChange-Id: I6c1a3285034c9e057879de601e1f80a4bed07edb\nSigned-off-by: Devin Kim <dojip.kim@lge.com>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/7a00651b94981575e7d79981c3c5dfe80124f103"},{"sha":"adbfbd0c78bfa69961386a9efe0e4ecc99de0b57","author":{"name":"Paul Turner","email":"65956f0277a169e2acdfe8eb55aaa1663653d482@google.com"},"message":"sched: Track the runnable average on a per-task entity basis\n\nInstead of tracking averaging the load parented by a cfs_rq, we can track\nentity load directly. With the load for a given cfs_rq then being the sum\nof its children.\n\nTo do this we represent the historical contribution to runnable average\nwithin each trailing 1024us of execution as the coefficients of a\ngeometric series.\n\nWe can express this for a given task t as:\n\n  runnable_sum(t) = \\Sum u_i * y^i, runnable_avg_period(t) = \\Sum 1024 * y^i\n  load(t) = weight_t * runnable_sum(t) / runnable_avg_period(t)\n\nWhere: u_i is the usage in the last i`th 1024us period (approximately 1ms)\n~ms and y is chosen such that y^k = 1/2.  We currently choose k to be 32 which\nroughly translates to about a sched period.\n\nChange-Id: Iafc090fe18ed1835cc501949e8ba1e4ed78c5de1\nSigned-off-by: Paul Turner <pjt@google.com>\nReviewed-by: Ben Segall <bsegall@google.com>\nSigned-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\nLink: http://lkml.kernel.org/r/20120823141506.372695337@google.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/adbfbd0c78bfa69961386a9efe0e4ecc99de0b57"},{"sha":"e281d4d85cdb6bb182b65b8f7533330b7128593d","author":{"name":"Ben Segall","email":"99eb0c7a4f3a18874efff9726ade52c2b7beb2eb@google.com"},"message":"sched: Maintain per-rq runnable averages\n\nSince runqueues do not have a corresponding sched_entity we instead embed a\nsched_avg structure directly.\n\nChange-Id: Ib2a80c77f6b4e017eaa72b31004630c7d95e4b94\nSigned-off-by: Ben Segall <bsegall@google.com>\nReviewed-by: Paul Turner <pjt@google.com>\nSigned-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\nLink: http://lkml.kernel.org/r/20120823141506.442637130@google.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/e281d4d85cdb6bb182b65b8f7533330b7128593d"},{"sha":"247d8b99e8974a43256e55815d549af07f06f32f","author":{"name":"Paul Turner","email":"65956f0277a169e2acdfe8eb55aaa1663653d482@google.com"},"message":"sched: Aggregate load contributed by task entities on parenting cfs_rq\n\nFor a given task t, we can compute its contribution to load as:\n\n  task_load(t) = runnable_avg(t) * weight(t)\n\nOn a parenting cfs_rq we can then aggregate:\n\n  runnable_load(cfs_rq) = \\Sum task_load(t), for all runnable children t\n\nMaintain this bottom up, with task entities adding their contributed load to\nthe parenting cfs_rq sum.  When a task entity's load changes we add the same\ndelta to the maintained sum.\n\nSigned-off-by: Paul Turner <pjt@google.com>\nReviewed-by: Ben Segall <bsegall@google.com>\nSigned-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\nLink: http://lkml.kernel.org/r/20120823141506.514678907@google.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/247d8b99e8974a43256e55815d549af07f06f32f"},{"sha":"6b0387025b7db1448bf8218590b04590c9940be7","author":{"name":"Paul Turner","email":"65956f0277a169e2acdfe8eb55aaa1663653d482@google.com"},"message":"sched: Maintain the load contribution of blocked entities\n\nWe are currently maintaining:\n\n  runnable_load(cfs_rq) = \\Sum task_load(t)\n\nFor all running children t of cfs_rq.  While this can be naturally updated for\ntasks in a runnable state (as they are scheduled); this does not account for\nthe load contributed by blocked task entities.\n\nThis can be solved by introducing a separate accounting for blocked load:\n\n  blocked_load(cfs_rq) = \\Sum runnable(b) * weight(b)\n\nObviously we do not want to iterate over all blocked entities to account for\ntheir decay, we instead observe that:\n\n  runnable_load(t) = \\Sum p_i*y^i\n\nand that to account for an additional idle period we only need to compute:\n\n  y*runnable_load(t).\n\nThis means that we can compute all blocked entities at once by evaluating:\n\n  blocked_load(cfs_rq)` = y * blocked_load(cfs_rq)\n\nFinally we maintain a decay counter so that when a sleeping entity re-awakens\nwe can determine how much of its load should be removed from the blocked sum.\n\nChange-Id: Ib0b29b3d1ca872a13d7236ed142156ef0a35dc9a\nSigned-off-by: Paul Turner <pjt@google.com>\nReviewed-by: Ben Segall <bsegall@google.com>\nSigned-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\nLink: http://lkml.kernel.org/r/20120823141506.585389902@google.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/6b0387025b7db1448bf8218590b04590c9940be7"},{"sha":"c615374d76a539653d96375556896cd2f3331280","author":{"name":"Paul Turner","email":"65956f0277a169e2acdfe8eb55aaa1663653d482@google.com"},"message":"sched: Add an rq migration call-back to sched_class\n\nSince we are now doing bottom up load accumulation we need explicit\nnotification when a task has been re-parented so that the old hierarchy can be\nupdated.\n\nAdds: migrate_task_rq(struct task_struct *p, int next_cpu)\n\n(The alternative is to do this out of __set_task_cpu, but it was suggested that\nthis would be a cleaner encapsulation.)\n\nChange-Id: Icc4111cd4159f804186dd7c05f0c36f4e368288e\nSigned-off-by: Paul Turner <pjt@google.com>\nReviewed-by: Ben Segall <bsegall@google.com>\nSigned-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\nLink: http://lkml.kernel.org/r/20120823141506.660023400@google.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/c615374d76a539653d96375556896cd2f3331280"},{"sha":"607be766e76b1753fbd00c5b98bb2397149e677c","author":{"name":"Paul Turner","email":"65956f0277a169e2acdfe8eb55aaa1663653d482@google.com"},"message":"sched: Account for blocked load waking back up\n\nWhen a running entity blocks we migrate its tracked load to\ncfs_rq->blocked_runnable_avg.  In the sleep case this occurs while holding\nrq->lock and so is a natural transition.  Wake-ups however, are potentially\nasynchronous in the presence of migration and so special care must be taken.\n\nWe use an atomic counter to track such migrated load, taking care to match this\nwith the previously introduced decay counters so that we don't migrate too much\nload.\n\nChange-Id: Ied949a2a42f68e4d4d16275351fd1240939dd519\nSigned-off-by: Paul Turner <pjt@google.com>\nReviewed-by: Ben Segall <bsegall@google.com>\nSigned-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\nLink: http://lkml.kernel.org/r/20120823141506.726077467@google.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/607be766e76b1753fbd00c5b98bb2397149e677c"},{"sha":"e624d99bed3263bc8694e6a91f6e1f198aa57a24","author":{"name":"Paul Turner","email":"65956f0277a169e2acdfe8eb55aaa1663653d482@google.com"},"message":"sched: Aggregate total task_group load\n\nMaintain a global running sum of the average load seen on each cfs_rq belonging\nto each task group so that it may be used in calculating an appropriate\nshares:weight distribution.\n\nChange-Id: If2726cb0037ddffce651ea17c46cbc4924cca7a2\nSigned-off-by: Paul Turner <pjt@google.com>\nReviewed-by: Ben Segall <bsegall@google.com>\nSigned-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\nLink: http://lkml.kernel.org/r/20120823141506.792901086@google.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/e624d99bed3263bc8694e6a91f6e1f198aa57a24"},{"sha":"d11705d608899153a0987caeae55847461e37613","author":{"name":"Paul Turner","email":"65956f0277a169e2acdfe8eb55aaa1663653d482@google.com"},"message":"sched: Compute load contribution by a group entity\n\nUnlike task entities who have a fixed weight, group entities instead own a\nfraction of their parenting task_group's shares as their contributed weight.\n\nCompute this fraction so that we can correctly account hierarchies and shared\nentity nodes.\n\nChange-Id: If61e926bb72f56c543b5b85841355f9f6997c51d\nSigned-off-by: Paul Turner <pjt@google.com>\nReviewed-by: Ben Segall <bsegall@google.com>\nSigned-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\nLink: http://lkml.kernel.org/r/20120823141506.855074415@google.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/d11705d608899153a0987caeae55847461e37613"},{"sha":"28d7dca5e0c813c0145b27c5806f87c5cc7c3894","author":{"name":"Paul Turner","email":"65956f0277a169e2acdfe8eb55aaa1663653d482@google.com"},"message":"sched: Normalize tg load contributions against runnable time\n\nEntities of equal weight should receive equitable distribution of cpu time.\nThis is challenging in the case of a task_group's shares as execution may be\noccurring on multiple cpus simultaneously.\n\nTo handle this we divide up the shares into weights proportionate with the load\non each cfs_rq.  This does not however, account for the fact that the sum of\nthe parts may be less than one cpu and so we need to normalize:\n  load(tg) = min(runnable_avg(tg), 1) * tg->shares\nWhere runnable_avg is the aggregate time in which the task_group had runnable\nchildren.\n\nChange-Id: I6f8d2ff1e61c1559c892ed9e2da670aed92dbbeb\nSigned-off-by: Paul Turner <pjt@google.com>\nReviewed-by: Ben Segall <bsegall@google.com>.\nSigned-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\nLink: http://lkml.kernel.org/r/20120823141506.930124292@google.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/28d7dca5e0c813c0145b27c5806f87c5cc7c3894"},{"sha":"d8b9b03b1bac6bc4f458a1097b9a8be86c757398","author":{"name":"Paul Turner","email":"65956f0277a169e2acdfe8eb55aaa1663653d482@google.com"},"message":"sched: Maintain runnable averages across throttled periods\n\nWith bandwidth control tracked entities may cease execution according to user\nspecified bandwidth limits.  Charging this time as either throttled or blocked\nhowever, is incorrect and would falsely skew in either direction.\n\nWhat we actually want is for any throttled periods to be \"invisible\" to\nload-tracking as they are removed from the system for that interval and\ncontribute normally otherwise.\n\nDo this by moderating the progression of time to omit any periods in which the\nentity belonged to a throttled hierarchy.\n\nChange-Id: I9d2c2d8a0cc984064c37432ecb262178ce0b3d32\nSigned-off-by: Paul Turner <pjt@google.com>\nReviewed-by: Ben Segall <bsegall@google.com>\nSigned-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\nLink: http://lkml.kernel.org/r/20120823141506.998912151@google.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/d8b9b03b1bac6bc4f458a1097b9a8be86c757398"},{"sha":"f3f1bfdba18dfafe2736fb82fc4acfbd4ebd79b7","author":{"name":"Paul Turner","email":"65956f0277a169e2acdfe8eb55aaa1663653d482@google.com"},"message":"sched: Replace update_shares weight distribution with per-entity computation\n\nNow that the machinery in place is in place to compute contributed load in a\nbottom up fashion; replace the shares distribution code within update_shares()\naccordingly.\n\nChange-Id: Ib53b4ee8d1c1d3e862ce5174d3b7e6ca12276400\nSigned-off-by: Paul Turner <pjt@google.com>\nReviewed-by: Ben Segall <bsegall@google.com>\nSigned-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\nLink: http://lkml.kernel.org/r/20120823141507.061208672@google.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/RJDTWO/android_kernel_oneplus_msm8974/commits/f3f1bfdba18dfafe2736fb82fc4acfbd4ebd79b7"}]}
{"actor":{"display_login":"RJDTWO"}}