{"push_id":1785936913,"size":15,"distinct_size":15,"ref":"refs/heads/Marshmallow_jactivelteskt","head":"24868958ec6da3dab3fbfba2d6092e964152821d","before":"efa70f36165bb3de70a72918ad8c53de9241b607","commits":[{"sha":"3376c85919f3c0ef0894e41ee8b94ad54be87b31","author":{"name":"Anton Vorontsov","email":"39137935ce08a8aa7f57fe25ae946e3e7a3763c8@linaro.org"},"message":"mm : memcg : Add memory.pressure_level events\n\nWith this patch userland applications that want to maintain the\ninteractivity/memory allocation cost can use the pressure level\nnotifications.  The levels are defined like this:\n\nThe \"low\" level means that the system is reclaiming memory for new\nallocations.  Monitoring this reclaiming activity might be useful for\nmaintaining cache level.  Upon notification, the program (typically\n\"Activity Manager\") might analyze vmstat and act in advance (i.e.\nprematurely shutdown unimportant services).\n\nThe \"medium\" level means that the system is experiencing medium memory\npressure, the system might be making swap, paging out active file\ncaches, etc.  Upon this event applications may decide to further analyze\nvmstat/zoneinfo/memcg or internal memory usage statistics and free any\nresources that can be easily reconstructed or re-read from a disk.\n\nThe \"critical\" level means that the system is actively thrashing, it is\nabout to out of memory (OOM) or even the in-kernel OOM killer is on its\nway to trigger.  Applications should do whatever they can to help the\nsystem.  It might be too late to consult with vmstat or any other\nstatistics, so it's advisable to take an immediate action.\n\nThe events are propagated upward until the event is handled, i.e.  the\nevents are not pass-through.  Here is what this means: for example you\nhave three cgroups: A->B->C.  Now you set up an event listener on\ncgroups A, B and C, and suppose group C experiences some pressure.  In\nthis situation, only group C will receive the notification, i.e.  groups\nA and B will not receive it.  This is done to avoid excessive\n\"broadcasting\" of messages, which disturbs the system and which is\nespecially bad if we are low on memory or thrashing.  So, organize the\ncgroups wisely, or propagate the events manually (or, ask us to\nimplement the pass-through events, explaining why would you need them.)\n\nPerformance wise, the memory pressure notifications feature itself is\nlightweight and does not require much of bookkeeping, in contrast to the\nrest of memcg features.  Unfortunately, as of current memcg\nimplementation, pages accounting is an inseparable part and cannot be\nturned off.  The good news is that there are some efforts[1] to improve\nthe situation; plus, implementing the same, fully API-compatible[2]\ninterface for CONFIG_CGROUP_MEM_RES_CTLR=n case (e.g.  embedded) is also\na viable option, so it will not require any changes on the userland\nside.\n\n[1] http://permalink.gmane.org/gmane.linux.kernel.cgroups/6291\n[2] http://lkml.org/lkml/2013/2/21/454\n\n[akpm@linux-foundation.org: coding-style fixes]\n[akpm@linux-foundation.org: fix CONFIG_CGROPUPS=n warnings]\nSigned-off-by: Anton Vorontsov <anton.vorontsov@linaro.org>\nAcked-by: Kirill A. Shutemov <kirill@shutemov.name>\nAcked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\nCc: Tejun Heo <tj@kernel.org>\nCc: David Rientjes <rientjes@google.com>\nCc: Pekka Enberg <penberg@kernel.org>\nCc: Mel Gorman <mgorman@suse.de>\nCc: Glauber Costa <glommer@parallels.com>\nCc: Michal Hocko <mhocko@suse.cz>\nCc: Luiz Capitulino <lcapitulino@redhat.com>\nCc: Greg Thelen <gthelen@google.com>\nCc: Leonid Moiseichuk <leonid.moiseichuk@nokia.com>\nCc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>\nCc: Minchan Kim <minchan@kernel.org>\nCc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>\nCc: John Stultz <john.stultz@linaro.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n\nChange-Id: I4e703d3688c74466e02cf0f2b866e85043fe799d","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/3376c85919f3c0ef0894e41ee8b94ad54be87b31"},{"sha":"3d1f40cb263431a418d06059ad547942b8e2ca6d","author":{"name":"Vinayak Menon","email":"c6e79b2757471d38dfbeaf17f987a81f42208aac@codeaurora.org"},"message":"mm : vmpressure : Allow in-kernel clients to subscribe for events\n\nCurrently, vmpressure is tied to memcg and its events are\navailable only to userspace clients. This patch removes\nthe dependency on CONFIG_MEMCG and adds a mechanism for\nin-kernel clients to subscribe for vmpressure events (in\nfact raw vmpressure values are delivered instead of vmpressure\nlevels, to provide clients more flexibility to take actions\non custom pressure levels which are not currently defined\nby vmpressure module).\n\nChange-Id: I1500c098cde11010e463d67955e8a03feb193a67\nSigned-off-by: Vinayak Menon <vinmenon@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/3d1f40cb263431a418d06059ad547942b8e2ca6d"},{"sha":"2a236e25c5be4725c531437f75a3ee79aeb07718","author":{"name":"Vinayak Menon","email":"c6e79b2757471d38dfbeaf17f987a81f42208aac@codeaurora.org"},"message":"drivers : staging : android : lowmemorykiller : avoid false adaptive LMK triggers\n\nIn vmpressure notifier of LMK, shift_adj would have been set\nby a previous invocation of notifier, which is not followed by\na lowmem_shrink yet. Since vmpressure has improved, reset\nshift_adj to avoid false adaptive LMK trigger.\n\nChange-Id: I9e395d46cedd3730352c0082083d39d446748095\nSigned-off-by: Vinayak Menon <vinmenon@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/2a236e25c5be4725c531437f75a3ee79aeb07718"},{"sha":"1028dc9da535f93a84ccb6378f46c9e7698ebed1","author":{"name":"Kitakami","email":"236faad127953fa8c724866e2a7b5efb1deb08a7@gmail.com"},"message":"mm : Backport ZCache from QC kernel 3.18\n\nChange-Id: I3edff3a56cf6525f13430ab93309272d1faecfe1\n\nConflicts:\ninclude/linux/page-flags.h","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/1028dc9da535f93a84ccb6378f46c9e7698ebed1"},{"sha":"479b8228ed40087b45d599a2e1a1820ca75e1b8c","author":{"name":"Kitakami","email":"236faad127953fa8c724866e2a7b5efb1deb08a7@gmail.com"},"message":"drivers : cpufreq : Update intelliactive","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/479b8228ed40087b45d599a2e1a1820ca75e1b8c"},{"sha":"c7f89f7983db203295f381fd052830aa63ef75a1","author":{"name":"gugu0das","email":"5af1a2a408d42ebaa35fb607f06b5a620a9b9f46@gmail.com"},"message":"defconfig : Enable CONFIG_ZCACHE","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/c7f89f7983db203295f381fd052830aa63ef75a1"},{"sha":"fdd5144bf9143681ade448de3e97579050a809fd","author":{"name":"gugu0das","email":"5af1a2a408d42ebaa35fb607f06b5a620a9b9f46@gmail.com"},"message":"defconfig : Enable CONFIG_ZBUD","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/fdd5144bf9143681ade448de3e97579050a809fd"},{"sha":"9270ec99fd34fe59ec2738106b7a28d279a0fc4d","author":{"name":"gugu0das","email":"5af1a2a408d42ebaa35fb607f06b5a620a9b9f46@gmail.com"},"message":"mm : vmscan : Remove SetPageWasActive(page)","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/9270ec99fd34fe59ec2738106b7a28d279a0fc4d"},{"sha":"1621f85bf6d47ebab7137476db54f63911bf50e5","author":{"name":"Nikhilesh Reddy","email":"1e32cc90766364d327453cc38b968b137a000d78@codeaurora.org"},"message":"fs : fuse : Add support for shortcircuited read/write for files\n\nAdd support for shortcircuited read/write for files\nwhen enabled through a userspace init option of\nFUSE_SHORTCIRCUIT.\n\nWhen FUSE_SHORTCIRCUIT is enabled all the reads and writes\nto the fuse mount point go directly to the native filesystem\nrather than through the fuse daemon. All requsts that aren't\nread/write still go thought the userspace code.\n\nThis allows for significantly better performance on read and writes\nand the difference between fuse and the native lower filesystem is\nnegligible.\n\nChange-Id: I8258f356963505a2f8499f38879e9e36aba43ad4\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>\n\nfs:fuse: Ensure update of fuse inode attributes in shortcircuit\n\nEnsure that in shortcircuit mode the fuse inode attributes always\nreflect those of the native filesystem by forcing an attribute copy.\n\nChange-Id: Ie4d322c9b8e0d3b49d195801dab4cc86d8df11e2\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>\n\nfuse: Use iocb->ki_pos instead of pos for shortcircuit writes\n\nUse iocb->ki_pos instead of pos to handle the cases of files that are\nopened with O_APPEND. For example if multiple processes open the same\nfile with O_APPEND then the iocb->ki_pos will not be equal to the new\npos value that is updated with the file size(to guarantee appends even\nwhen the file has grown due to the writes by another process).\n\nWe should use iocb->pos here since the lower filesystem is expected to\nadjust for O_APPEND anyway and may need to adjust the size for the file\nchanges that occur due to some processes writing directly to the lower\nfilesystem.\n\nChange-Id: I279e3ea96cdfd020c45f4cd348f6e1b4bd48a3fb\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>\n\nfuse: Use BUG_ON to check pos validity in fuse_aio_write\n\nChange the check that iocb->ki_pos should be equal to pos\nto a BUG_ON from a WARN_ON to ensure we actually catch\nthe bug before it propagates down and causes other errors.\n\nChange-Id: Ie6d537f3182f638a50166b456226e9c10bb1e3d4\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/1621f85bf6d47ebab7137476db54f63911bf50e5"},{"sha":"6b1982cb014ab4a5c75077968d0d15814299d80d","author":{"name":"Daniel Rosenberg","email":"ba8cfe5d21fcfdde5eed8cabcaff0549d9612a2a@gmail.com"},"message":"fs : sdcardfs : Remove effectless config option\n\nCONFIG_SDCARD_FS_CI_SEARCH only guards a define for\nLOOKUP_CASE_INSENSITIVE, which is never used in the\nkernel. Remove both, along with the option matching\nthat supports it.\n\nChange-Id: I363a8f31de8ee7a7a934d75300cc9ba8176e2edf\nSigned-off-by: Daniel Rosenberg <drosen@google.com>\n\nConflicts:\n\tinclude/linux/namei.h","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/6b1982cb014ab4a5c75077968d0d15814299d80d"},{"sha":"9d7d29f90316caa54728b59eda8425d926b4fcd2","author":{"name":"Kent Overstreet","email":"c197b69fb6ea1daf1135913a0ef58da30de5e611@google.com"},"message":"block : Add bio_for_each_segment_all()\n\n__bio_for_each_segment() iterates bvecs from the specified index\ninstead of bio->bv_idx.  Currently, the only usage is to walk all the\nbvecs after the bio has been advanced by specifying 0 index.\n\nFor immutable bvecs, we need to split these apart;\nbio_for_each_segment() is going to have a different implementation.\nThis will also help document the intent of code that's using it -\nbio_for_each_segment_all() is only legal to use for code that owns the\nbio.\n\nChange-Id: I74e57c70e0df81c00be1e1d7fee32ae6374e3cab\nSigned-off-by: Kent Overstreet <koverstreet@google.com>\nSigned-off-by: Paul Keith <javelinanddart@gmail.com>\nCC: Jens Axboe <axboe@kernel.dk>\nCC: Neil Brown <neilb@suse.de>\nCC: Boaz Harrosh <bharrosh@panasas.com>","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/9d7d29f90316caa54728b59eda8425d926b4fcd2"},{"sha":"3f6f100394643df38b57560872686ce445fb03d9","author":{"name":"Kent Overstreet","email":"c197b69fb6ea1daf1135913a0ef58da30de5e611@google.com"},"message":"block : Add submit_bio_wait(), Remove from md\n\nRandom cleanup - this code was duplicated and it's not really specific\nto md.\n\nAlso added the ability to return the actual error code.\n\nChange-Id: Ie7535672a2ecb5f810fa4da546c1e395843ab130\nSigned-off-by: Kent Overstreet <koverstreet@google.com>\nSigned-off-by: Paul Keith <javelinanddart@gmail.com>\nCC: Jens Axboe <axboe@kernel.dk>\nCC: NeilBrown <neilb@suse.de>\nAcked-by: Tejun Heo <tj@kernel.org>","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/3f6f100394643df38b57560872686ce445fb03d9"},{"sha":"376eda2049ec817a96f856e601e1d525798e9b1b","author":{"name":"Xiaojun Sang","email":"2dc0774bd7308bab634efe4d5a19a2fc19a72888@codeaurora.org"},"message":"sound : core : compress_offload : Fix unsigned integer overflow check\n\nParameter fragments and fragment_size are type of u32. U32_MAX is\nthe correct check.\n\nCRs-Fixed: 1014726\nChange-Id: Ia6d4755408646ac4a75724f3c6f2177651875da3\nSigned-off-by: Xiaojun Sang <xsang@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/376eda2049ec817a96f856e601e1d525798e9b1b"},{"sha":"57ad97252bab57f8715c8c60aa5b8c6fe86295f0","author":{"name":"Alan Stern","email":"5c4cbde65af01ad64f5b2177d0cd78ab5b01e5a1@rowland.harvard.edu"},"message":"drivers : usb : Fix invalid memory access in hub_activate()\n\nCommit 8520f38099cc (\"USB: change hub initialization sleeps to\ndelayed_work\") changed the hub_activate() routine to make part of it\nrun in a workqueue.  However, the commit failed to take a reference to\nthe usb_hub structure or to lock the hub interface while doing so.  As\na result, if a hub is plugged in and quickly unplugged before the work\nroutine can run, the routine will try to access memory that has been\ndeallocated.  Or, if the hub is unplugged while the routine is\nrunning, the memory may be deallocated while it is in active use.\n\nThis patch fixes the problem by taking a reference to the usb_hub at\nthe start of hub_activate() and releasing it at the end (when the work\nis finished), and by locking the hub interface while the work routine\nis running.  It also adds a check at the start of the routine to see\nif the hub has already been disconnected, in which nothing should be\ndone.\n\nSigned-off-by: Alan Stern <stern@rowland.harvard.edu>\nReported-by: Alexandru Cornea <alexandru.cornea@intel.com>\nTested-by: Alexandru Cornea <alexandru.cornea@intel.com>\nFixes: 8520f38099cc (\"USB: change hub initialization sleeps to delayed_work\")\nCC: <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nBug: 28712303\nChange-Id: Ie696f13c4fa28dd549d459ea607cf27b53610be6","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/57ad97252bab57f8715c8c60aa5b8c6fe86295f0"},{"sha":"24868958ec6da3dab3fbfba2d6092e964152821d","author":{"name":"Mohamad Ayyash","email":"a63011e6db47c5624401b2ef01e42a84436c0cfe@google.com"},"message":"net : netfilter : xt_qtaguid : Replace %p with %pK to prevent leaking kernel address\n\nBUG: 27532522\nChange-Id: Ic0710a9a8cfc682acd88ecf3bbfeece2d798c4a4\nSigned-off-by: Mohamad Ayyash <mkayyash@google.com>","distinct":true,"url":"https://api.github.com/repos/tomasz1986/android_kernel_samsung_msm8974/commits/24868958ec6da3dab3fbfba2d6092e964152821d"}]}
{"actor":{"display_login":"tomasz1986"}}