{"push_id":631444379,"size":9,"distinct_size":9,"ref":"refs/heads/cm-12.0","head":"18f320fe703ee72859ddfad12a5df1d191bfe10c","before":"5415e155adbe775caa057279a362d4b4711083ca","commits":[{"sha":"ece85e221b8df4b9f3b6cdb0be762ef7f27cc209","author":{"email":"e3c980acc123aa903e30d63a9699ababf4e45af1@gmail.com","name":"Spegelius"},"message":"Jactive defconfig up to date... again\n\nChange-Id: I70e19838100dc57c17b6fbd17c420054553d5669","distinct":true,"url":"https://api.github.com/repos/iyahman/android_kernel_samsung_jf/commits/ece85e221b8df4b9f3b6cdb0be762ef7f27cc209"},{"sha":"04e6498839645fe34160f05bae9ea2c1b3ae519c","author":{"email":"a21938f5d463ddf41aa718934c205ca2cce8ebbc@redhat.com","name":"Rik van Riel"},"message":"add extra free kbytes tunable\n\nAdd a userspace visible knob to tell the VM to keep an extra amount\nof memory free, by increasing the gap between each zone's min and\nlow watermarks.\n\nThis is useful for realtime applications that call system\ncalls and have a bound on the number of allocations that happen\nin any short time period.  In this application, extra_free_kbytes\nwould be left at an amount equal to or larger than than the\nmaximum number of allocations that happen in any burst.\n\nIt may also be useful to reduce the memory use of virtual\nmachines (temporarily?), in a way that does not cause memory\nfragmentation like ballooning does.\n\n[ccross]\nRevived for use on old kernels where no other solution exists.\nThe tunable will be removed on kernels that do better at avoiding\ndirect reclaim.\n\nChange-Id: I765a42be8e964bfd3e2886d1ca85a29d60c3bb3e\nSigned-off-by: Rik van Riel<riel@redhat.com>\nSigned-off-by: Colin Cross <ccross@android.com>","distinct":true,"url":"https://api.github.com/repos/iyahman/android_kernel_samsung_jf/commits/04e6498839645fe34160f05bae9ea2c1b3ae519c"},{"sha":"17b7c3e40c2bdf5156c4790c4d90ceaaf40ccad4","author":{"email":"e642b69ed2fc111e09ffdc37feb733a52253340d@oracle.com","name":"Sasha Levin"},"message":"vfs: read file_handle only once in handle_to_path\n\nWe used to read file_handle twice. Once to get the amount of extra bytes, and\nonce to fetch the entire structure.\n\nThis may be problematic since we do size verifications only after the first\nread, so if the number of extra bytes changes in userspace between the first\nand second calls, we'll have an incoherent view of file_handle.\n\nInstead, read the constant size once, and copy that over to the final\nstructure without having to re-read it again.\n\nChange-Id: Ib05e5129629e27d5a05953098c5bc470fae40d2a\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":true,"url":"https://api.github.com/repos/iyahman/android_kernel_samsung_jf/commits/17b7c3e40c2bdf5156c4790c4d90ceaaf40ccad4"},{"sha":"99d34150a9151d5d5d311a680e7e9e179bcaaed4","author":{"email":"eec72676ad9a62f2727dfed6d270d98c0d02adec@linux.intel.com","name":"Kirill A. Shutemov"},"message":"mm: Fix NULL pointer dereference in madvise(MADV_WILLNEED) support\n\nSasha Levin found a NULL pointer dereference that is due to a missing\npage table lock, which in turn is due to the pmd entry in question being\na transparent huge-table entry.\n\nThe code - introduced in commit 1998cc048901 (\"mm: make\nmadvise(MADV_WILLNEED) support swap file prefetch\") - correctly checks\nfor this situation using pmd_none_or_trans_huge_or_clear_bad(), but it\nturns out that that function doesn't work correctly.\n\npmd_none_or_trans_huge_or_clear_bad() expected that pmd_bad() would\ntrigger if the transparent hugepage bit was set, but it doesn't do that\nif pmd_numa() is also set. Note that the NUMA bit only gets set on real\nNUMA machines, so people trying to reproduce this on most normal\ndevelopment systems would never actually trigger this.\n\nFix it by removing the very subtle (and subtly incorrect) expectation,\nand instead just checking pmd_trans_huge() explicitly.\n\nReported-by: Sasha Levin <sasha.levin@oracle.com>\nAcked-by: Andrea Arcangeli <aarcange@redhat.com>\n[ Additionally remove the now stale test for pmd_trans_huge() inside the\n  pmd_bad() case - Linus ]\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n\nChange-Id: I3f3763f236ef102de735297cd175cf514d40d28f","distinct":true,"url":"https://api.github.com/repos/iyahman/android_kernel_samsung_jf/commits/99d34150a9151d5d5d311a680e7e9e179bcaaed4"},{"sha":"dd443260309c9cabf13b8e4fe17420c7ebfabcea","author":{"email":"ad5ede63337b3f6ba0c8f4353e50bd01ded91d63@gmail.com","name":"Dan Pasanen"},"message":"Revert \"smart_mtp_se6e8fa: add gamma control\"\n\nThis reverts commit 354aebb8127c69c3c8c65ddb5cceea479b3fad2a.\n\nChange-Id: I7ed9c1b3bae80ba711cedd9daacc4bb5ee6c1ce5","distinct":true,"url":"https://api.github.com/repos/iyahman/android_kernel_samsung_jf/commits/dd443260309c9cabf13b8e4fe17420c7ebfabcea"},{"sha":"51f1831d20456c68a3cab7177ab08dddabaf2924","author":{"email":"cbed88164a314c0a7942650afc8c70730ee0039f@google.com","name":"Erik Kline"},"message":"net: ipv6: Add a sysctl to make optimistic addresses useful candidates\n\nAdd a sysctl that causes an interface's optimistic addresses\nto be considered equivalent to other non-deprecated addresses\nfor source address selection purposes.  Preferred addresses\nwill still take precedence over optimistic addresses, subject\nto other ranking in the source address selection algorithm.\n\nThis is useful where different interfaces are connected to\ndifferent networks from different ISPs (e.g., a cell network\nand a home wifi network).\n\nThe current behaviour complies with RFC 3484/6724, and it\nmakes sense if the host has only one interface, or has\nmultiple interfaces on the same network (same or cooperating\nadministrative domain(s), but not in the multiple distinct\nnetworks case.\n\nFor example, if a mobile device has an IPv6 address on an LTE\nnetwork and then connects to IPv6-enabled wifi, while the wifi\nIPv6 address is undergoing DAD, IPv6 connections will try use\nthe wifi default route with the LTE IPv6 address, and will get\nstuck until they time out.\n\nAlso, because optimistic nodes can receive frames, issue\nan RTM_NEWADDR as soon as DAD starts (with the IFA_F_OPTIMSTIC\nflag appropriately set).  A second RTM_NEWADDR is sent if DAD\ncompletes (the address flags have changed), otherwise an\nRTM_DELADDR is sent.\n\nAlso: add an entry in ip-sysctl.txt for optimistic_dad.\n\n[backport of net-next 7fd2561e4ebdd070ebba6d3326c4c5b13942323f]\n\nSigned-off-by: Erik Kline <ek@google.com>\nAcked-by: Lorenzo Colitti <lorenzo@google.com>\nAcked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nBug: 17769720\nChange-Id: I440a9b8c788db6767d191bbebfd2dff481aa9e0d","distinct":true,"url":"https://api.github.com/repos/iyahman/android_kernel_samsung_jf/commits/51f1831d20456c68a3cab7177ab08dddabaf2924"},{"sha":"2b03d6bc81092afd49556073a68b62b335b352d2","author":{"email":"cbed88164a314c0a7942650afc8c70730ee0039f@google.com","name":"Erik Kline"},"message":"net: ipv6: allow choosing optimistic addresses with use_optimistic\n\nThe use_optimistic sysctl makes optimistic IPv6 addresses\nequivalent to preferred addresses for source address selection\n(e.g., when calling connect()), but it does not allow an\napplication to bind to optimistic addresses. This behaviour is\ninconsistent - for example, it doesn't make sense for bind() to\nan optimistic address fail with EADDRNOTAVAIL, but connect() to\nchoose that address outgoing address on the same socket.\n\nBug: 17769720\nBug: 18609055\nChange-Id: I9de0d6c92ac45e29d28e318ac626c71806666f13\nSigned-off-by: Erik Kline <ek@google.com>\nSigned-off-by: Lorenzo Colitti <lorenzo@google.com>","distinct":true,"url":"https://api.github.com/repos/iyahman/android_kernel_samsung_jf/commits/2b03d6bc81092afd49556073a68b62b335b352d2"},{"sha":"91f93dbc96531307b8be6898696888acb5bfcd2a","author":{"email":"257d7d5bef225e0a56b3375b0c1e95c6bb0ab871@modio.se","name":"D.S. Ljungmark"},"message":"ipv6: Don't reduce hop limit for an interface\n\nA local route may have a lower hop_limit set than global routes do.\n\nRFC 3756, Section 4.2.7, \"Parameter Spoofing\"\n\n>   1.  The attacker includes a Current Hop Limit of one or another small\n>       number which the attacker knows will cause legitimate packets to\n>       be dropped before they reach their destination.\n\n>   As an example, one possible approach to mitigate this threat is to\n>   ignore very small hop limits.  The nodes could implement a\n>   configurable minimum hop limit, and ignore attempts to set it below\n>   said limit.\n\nChange-Id: Ie70d7d35ea94738209b525872e7e9022676e05b3\nSigned-off-by: D.S. Ljungmark <ljungmark@modio.se>\nAcked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>\n(cherry picked from commit 8740944a024265f118abca58f9a7b5ce7a32891d)","distinct":true,"url":"https://api.github.com/repos/iyahman/android_kernel_samsung_jf/commits/91f93dbc96531307b8be6898696888acb5bfcd2a"},{"sha":"18f320fe703ee72859ddfad12a5df1d191bfe10c","author":{"email":"bbc903f428c9fa0ef095f3106e009a6ee4ae11b4@gmail.com","name":"Iyahman"},"message":"Merge pull request #1 from CyanogenMod/cm-12.0\n\nmerge Cm 12.0 change","distinct":true,"url":"https://api.github.com/repos/iyahman/android_kernel_samsung_jf/commits/18f320fe703ee72859ddfad12a5df1d191bfe10c"}]}