{"push_id":3029101873,"size":31,"distinct_size":31,"ref":"refs/heads/cm-14.1-new","head":"41e1f7fa675e46591cd3cacf65c9f1815cecd4b2","before":"ad24cb738c192a968b6fd77a194d8a4fae9eb99a","commits":[{"sha":"0de7b82d1b56d4bccf40e4aa6d9991ab6ee96722","author":{"name":"Luis Gonzalez Fernandez","email":"c538f4d4f774f9d6a7f435437a4d71bdb52c90c3@gmail.com"},"message":"PM / QoS: Add return code to pm_qos_get_value function.\n\npm_qos_get_value don't return a return code in all cases. It's sure that\nanything interesting happend after BUG() but this prevent any compilation\nwarning.\n\n[rjw: Chaneged the new return value to PM_QOS_DEFAULT_VALUE.]\n\nChange-Id: I4aaf952a6a66ee3d7601c530be54fc30a280b388\nSigned-off-by: Luis Gonzalez Fernandez <luisgf@gmail.com>\nSigned-off-by: Rafael J. Wysocki <rjw@sisk.pl>\nSigned-off-by: Marco Zanin (B--B) <mrczn.bb@gmail.com>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/0de7b82d1b56d4bccf40e4aa6d9991ab6ee96722"},{"sha":"22d70c71dd0e40b0b09a5cb6e6bb194f4ec5b009","author":{"name":"Daniel Thompson","email":"4421c302a8f2019ff02452a16ddbdd37770f814c@linaro.org"},"message":"BACKPORT: ARM: 8091/2: add get_user() support for 8 byte types\n\nRecent contributions, including to DRM and binder, introduce 64-bit\nvalues in their interfaces. A common motivation for this is to allow\nthe same ABI for 32- and 64-bit userspaces (and therefore also a shared\nABI for 32/64 hybrid userspaces). Anyhow, the developers would like to\navoid gotchas like having to use copy_from_user().\n\nThis feature is already implemented on x86-32 and the majority of other\n32-bit architectures. The current list of get_user_8 hold out\narchitectures are: arm, avr32, blackfin, m32r, metag, microblaze,\nmn10300, sh.\n\nCredit:\n\n    My name sits rather uneasily at the top of this patch. The v1 and\n    v2 versions of the patch were written by Rob Clark and to produce v4\n    I mostly copied code from Russell King and H. Peter Anvin. However I\n    have mangled the patch sufficiently that *blame* is rightfully mine\n    even if credit should more widely shared.\n\nChangelog:\n\nv5: updated to use the ret macro (requested by Russell King)\nv4: remove an inlined add on big endian systems (spotted by Russell King),\n    used __ARMEB__ rather than BIG_ENDIAN (to match rest of file),\n    cleared r3 on EFAULT during __get_user_8.\nv3: fix a couple of checkpatch issues\nv2: pass correct size to check_uaccess, and better handling of narrowing\n    double word read with __get_user_xb() (Russell King's suggestion)\nv1: original\n\nChange-Id: I41787d73f0844c15b6bd0424a5f83cafaba8b508\nSigned-off-by: Rob Clark <robdclark@gmail.com>\nSigned-off-by: Daniel Thompson <daniel.thompson@linaro.org>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>\n[flex1911: backport to 3.4: use \"mov pc\" instruction instead of\n           nonexistent here \"ret\" macro]\nSigned-off-by: Artem Borisov <dedsa2002@gmail.com>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/22d70c71dd0e40b0b09a5cb6e6bb194f4ec5b009"},{"sha":"691f00aee4634ddaa8739b2e74e88aff9a8771d4","author":{"name":"Anshul Garg","email":"433adf4e000ef006e7ed86a6a87b34fca89b9b00@samsung.com"},"message":"Input: optimize events_per_packet count calculation\n\nThis patch avoids unnecessary operations while estimating events per\npacket for an input device when event type is not set.\n\nChange-Id: I913be1e5356d5ca7d3047e6b0413069993c2921c\nSigned-off-by: Anshul Garg <anshul.g@samsung.com>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nGit-commit: baf332c0f1cede26e9c2af6276b36b4c3a36e34a\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nSigned-off-by: Matt Wagantall <mattw@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/691f00aee4634ddaa8739b2e74e88aff9a8771d4"},{"sha":"9234bb0111d692984f4e929a943b4ef5a9322472","author":{"name":"Subash Abhinov Kasiviswanathan","email":"1dc9a55fbcba59128627e933e7c9fd67d2a78e24@codeaurora.org"},"message":"net: Copy ndisc_nodetype from original skb in skb_clone\n\nskb_clone does not copy all fields from original skb. Fields\nwhich are uninitialized may cause unexpected behavior when they\nare passed down to network stack. In case ndisc_nodetype is set\nto a random value for a router advertisement, kernel looks at this\nfield and drops it assuming that this packet originates from a\nnode and not a router.\n\nFix this by copying the ndisc_nodetype from the original skb\nrather than relying on an uninitialized cloned skb.\n\nBug: 24810548\nChange-Id: I9686e31808c94a3bbf309007f521c0e06bac2e96\nSigned-off-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>\nSigned-off-by: Ravi Vembu <raviv@motorola.com>\nReviewed-on: http://gerrit.mot.com/792652\nSLTApproved: Slta Waiver <sltawvr@motorola.com>\nSME-Granted: SME Approvals Granted\nSubmit-Approved: Jira Key <jirakey@motorola.com>\nTested-by: Jira Key <jirakey@motorola.com>\nReviewed-by: Jayachandran Chinnakkannu <jayc@motorola.com>\nReviewed-by: Christopher Fries <cfries@motorola.com>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/9234bb0111d692984f4e929a943b4ef5a9322472"},{"sha":"1aaf6cf63a4fee872d6e2eaa404c2f41776be029","author":{"name":"Colin Cross","email":"380081620a7947c89c11153c5513f34019caa923@android.com"},"message":"timekeeping: fix 32-bit overflow in get_monotonic_boottime\n\nfixed upstream in v3.6 by ec145babe754f9ea1079034a108104b6001e001c\n\nget_monotonic_boottime adds three nanonsecond values stored\nin longs, followed by an s64.  If the long values are all\nclose to 1e9 the first three additions can overflow and\nbecome negative when added to the s64.  Cast the first\nvalue to s64 so that all additions are 64 bit.\n\nChange-Id: Id90beaf652571841b33cc6613d4744df33f5f007\nSigned-off-by: Colin Cross <ccross@android.com>\n[jstultz: Fished this out of the AOSP commong.git tree. This was\nfixed upstream in v3.6 by ec145babe754f9ea1079034a108104b6001e001c]\nSigned-off-by: John Stultz <john.stultz@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/1aaf6cf63a4fee872d6e2eaa404c2f41776be029"},{"sha":"22d2937cf32c3638c341b76c9fe50f112de9d620","author":{"name":"Tahsin Erdogan","email":"10f5d60ce5fa6fe3c789dd71c5d6567abd91f3fa@google.com"},"message":"block: Make CFQ default to IOPS mode on SSDs\n\nCFQ idling causes reduced IOPS throughput on non-rotational disks.\nSince disk head seeking is not applicable to SSDs, it doesn't really\nhelp performance by anticipating future near-by IO requests.\n\nBy turning off idling (and switching to IOPS mode), we allow other\nprocesses to dispatch IO requests down to the driver and so increase IO\nthroughput.\n\nFollowing FIO benchmark results were taken on a cloud SSD offering with\nidling on and off:\n\nIdling     iops    avg-lat(ms)    stddev            bw\n------------------------------------------------------\n    On     7054    90.107         38.697     28217KB/s\n   Off    29255    21.836         11.730    117022KB/s\n\nfio --name=temp --size=100G --time_based --ioengine=libaio \\\n    --randrepeat=0 --direct=1 --invalidate=1 --verify=0 \\\n    --verify_fatal=0 --rw=randread --blocksize=4k --group_reporting=1 \\\n    --filename=/dev/sdb --runtime=10 --iodepth=64 --numjobs=10\n\nAnd the following is from a local SSD run:\n\nIdling     iops    avg-lat(ms)    stddev            bw\n------------------------------------------------------\n    On    19320    33.043         14.068     77281KB/s\n   Off    21626    29.465         12.662     86507KB/s\n\nfio --name=temp --size=5G --time_based --ioengine=libaio \\\n    --randrepeat=0 --direct=1 --invalidate=1 --verify=0 \\\n    --verify_fatal=0 --rw=randread --blocksize=4k --group_reporting=1 \\\n    --filename=/fio_data --runtime=10 --iodepth=64 --numjobs=10\n\nChange-Id: I2311c1b349092d5d6afe5200037f6aeccf506e04\nReviewed-by: Nauman Rafique <nauman@google.com>\nSigned-off-by: Tahsin Erdogan <tahsin@google.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/22d2937cf32c3638c341b76c9fe50f112de9d620"},{"sha":"39f168fb13c32182a7b77965ab3faaf3fad6058c","author":{"name":"KAMEZAWA Hiroyuki","email":"634f508bd7c47cf0ee4126243675c3e598920fbc@jp.fujitsu.com"},"message":"memcg: fix/change behavior of shared anon at moving task\n\nThis patch changes memcg's behavior at task_move().\n\nAt task_move(), the kernel scans a task's page table and move the changes\nfor mapped pages from source cgroup to target cgroup.  There has been a\nbug at handling shared anonymous pages for a long time.\n\nBefore patch:\n  - The spec says 'shared anonymous pages are not moved.'\n  - The implementation was 'shared anonymoys pages may be moved'.\n    If page_mapcount <=2, shared anonymous pages's charge were moved.\n\nAfter patch:\n  - The spec says 'all anonymous pages are moved'.\n  - The implementation is 'all anonymous pages are moved'.\n\nConsidering usage of memcg, this will not affect user's experience.\n'shared anonymous' pages only exists between a tree of processes which\ndon't do exec().  Moving one of process without exec() seems not sane.\nFor example, libcgroup will not be affected by this change.  (Anyway, no\none noticed the implementation for a long time...)\n\nBelow is a discussion log:\n\n - current spec/implementation are complex\n - Now, shared file caches are moved\n - It adds unclear check as page_mapcount(). To do correct check,\n   we should check swap users, etc.\n - No one notice this implementation behavior. So, no one get benefit\n   from the design.\n - In general, once task is moved to a cgroup for running, it will not\n   be moved....\n - Finally, we have control knob as memory.move_charge_at_immigrate.\n\nHere is a patch to allow moving shared pages, completely. This makes\nmemcg simpler and fix current broken code.\n\nChange-Id: Ied31c4b7ecd1376057da468c9150582e2d52819f\nSuggested-by: Hugh Dickins <hughd@google.com>\nSigned-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\nAcked-by: Michal Hocko <mhocko@suse.cz>\nCc: Johannes Weiner <hannes@cmpxchg.org>\nCc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>\nCc: Glauber Costa <glommer@parallels.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/39f168fb13c32182a7b77965ab3faaf3fad6058c"},{"sha":"8d8a9d4aee424eea1a0a9dd279ad4ba01e6fedf2","author":{"name":"Paresh Nakhe","email":"42bf55596e7c6c191ef3c69c3b9e702b607bf4ea@codeaurora.org"},"message":"binder: NULL pointer reference\n\nThis fix handles a possible NULL pointer reference in\ndebug message.\n\nCRs-fixed: 642883\nChange-Id: Ide78f281ec0cff5cbd8231b85c305d13a892854e\nSigned-off-by: Paresh Nakhe <pnakhe@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/8d8a9d4aee424eea1a0a9dd279ad4ba01e6fedf2"},{"sha":"fe5a3f372943f9e3128d7c7530492cdf6543a99b","author":{"name":"myfluxi","email":"45d857216ef082c1ddfd5d3991b4f3d23f51761f@arcor.de"},"message":"arm: irq: Tone down kernel logging\n\nChange-Id: Ie31190bd65d1379de41e1ca2573aa65e785de1b6","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/fe5a3f372943f9e3128d7c7530492cdf6543a99b"},{"sha":"c7f8419ef92b42dff04ff56f53c8be2bf7da784c","author":{"name":"vijay kumar","email":"b8faca8f45c84d5881cc3a71a4ee4299af07e530@codeaurora.org"},"message":"scripts/dtc/libfdt: add integer overflow checks\n\nThis patch applies the same changes in the original commit\nbelow to the dtc to keep both sources in sync.\n\noriginal commit:\n    lib: fdt: add integer overflow checks\n\n    added integer overflow checks to avoid buffer over reads/write\n    while using the fdt header fields.\n\n    CRs-fixed: 705078.\n    Change-Id: I062ee9e0610eeeeea32dd95695b18aa9dbca06ea\n\nBug: 19136881\nChange-Id: I14df1e23cd635d4c222eb30a1474d1455036d756\nSigned-off-by: Patrick Tjin <pattjin@google.com>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/c7f8419ef92b42dff04ff56f53c8be2bf7da784c"},{"sha":"2c907f7b34163f83f5866a1e012e89bc25822924","author":{"name":"Stephen Smalley","email":"d6e1285e1c84d3d5885c2124fdacc780e9fc0a94@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: Ifc7e2dad167e79c2319139e22042513fd3130be2\nSigned-off-by: Stephen Smalley <sds@tycho.nsa.gov>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/2c907f7b34163f83f5866a1e012e89bc25822924"},{"sha":"e723b63b2d1509e30f5753a8a86ff84abf67b4c8","author":{"name":"Junxiao Bi","email":"adb0658383f88ec6beb1fb7689ba0dac7c1c4882@oracle.com"},"message":"writeback: fix race that cause writeback hung\n\nThere is a race between mark inode dirty and writeback thread, see the\nfollowing scenario.  In this case, writeback thread will not run though\nthere is dirty_io.\n\n__mark_inode_dirty()                                          bdi_writeback_workfn()\n\t...                                                       \t...\n\tspin_lock(&inode->i_lock);\n\t...\n\tif (bdi_cap_writeback_dirty(bdi)) {\n\t    <<< assume wb has dirty_io, so wakeup_bdi is false.\n\t    <<< the following inode_dirty also have wakeup_bdi false.\n\t    if (!wb_has_dirty_io(&bdi->wb))\n\t\t    wakeup_bdi = true;\n\t}\n\tspin_unlock(&inode->i_lock);\n\t                                                            <<< assume last dirty_io is removed here.\n\t                                                            pages_written = wb_do_writeback(wb);\n\t                                                            ...\n\t                                                            <<< work_list empty and wb has no dirty_io,\n\t                                                            <<< delayed_work will not be queued.\n\t                                                            if (!list_empty(&bdi->work_list) ||\n\t                                                                (wb_has_dirty_io(wb) && dirty_writeback_interval))\n\t                                                                queue_delayed_work(bdi_wq, &wb->dwork,\n\t                                                                    msecs_to_jiffies(dirty_writeback_interval * 10));\n\tspin_lock(&bdi->wb.list_lock);\n\tinode->dirtied_when = jiffies;\n\t<<< new dirty_io is added.\n\tlist_move(&inode->i_wb_list, &bdi->wb.b_dirty);\n\tspin_unlock(&bdi->wb.list_lock);\n\n\t<<< though there is dirty_io, but wakeup_bdi is false,\n\t<<< so writeback thread will not be waked up and\n\t<<< the new dirty_io will not be flushed.\n\tif (wakeup_bdi)\n\t    bdi_wakeup_thread_delayed(bdi);\n\nWriteback will run until there is a new flush work queued.  This may cause\na lot of dirty pages stay in memory for a long time.\n\nSigned-off-by: Junxiao Bi <junxiao.bi@oracle.com>\nReviewed-by: Jan Kara <jack@suse.cz>\nCc: Fengguang Wu <fengguang.wu@intel.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nChange-Id: I973fcba5381881a003a035ffff48f64348660079","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/e723b63b2d1509e30f5753a8a86ff84abf67b4c8"},{"sha":"1970330c6d5ba95a7050c181b4600e54c436115d","author":{"name":"Al Viro","email":"de609eb4d5d70b1d38ec6642adbfc33a2781f63c@zeniv.linux.org.uk"},"message":"nick kvfree() from apparmor\n\ntoo many places open-code it\n\nConflicts:\n\tmm/util.c\n\nBug: 17871993\nChange-Id: I007f4b663d7af564b2ce4009f5e13eeeeb82929a\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>\nGit-commit: 39f1f78d53b9bcbca91967380c5f0f2305a5c55f\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\n[jgebben@codeaurora.org: Remove redundant apparmor code not present upstream]\nSigned-off-by: Jeremy Gebben <jgebben@codeaurora.org>\nSigned-off-by: Naveen Ramaraj <nramaraj@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/1970330c6d5ba95a7050c181b4600e54c436115d"},{"sha":"ff7a4cd6741f9c9cfb41f9bb52587566909a621c","author":{"name":"David Rientjes","email":"d8cd2994e15bc61ddb2b113030bda55eebc3a0fe@google.com"},"message":"mm, oom: base root bonus on current usage\n\ncommit 778c14affaf94a9e4953179d3e13a544ccce7707 upstream.\n\nA 3% of system memory bonus is sometimes too excessive in comparison to\nother processes.\n\nWith commit a63d83f427fb (\"oom: badness heuristic rewrite\"), the OOM\nkiller tries to avoid killing privileged tasks by subtracting 3% of\noverall memory (system or cgroup) from their per-task consumption.  But\nas a result, all root tasks that consume less than 3% of overall memory\nare considered equal, and so it only takes 33+ privileged tasks pushing\nthe system out of memory for the OOM killer to do something stupid and\nkill dhclient or other root-owned processes.  For example, on a 32G\nmachine it can't tell the difference between the 1M agetty and the 10G\nfork bomb member.\n\nThe changelog describes this 3% boost as the equivalent to the global\novercommit limit being 3% higher for privileged tasks, but this is not\nthe same as discounting 3% of overall memory from _every privileged task\nindividually_ during OOM selection.\n\nReplace the 3% of system memory bonus with a 3% of current memory usage\nbonus.\n\nBy giving root tasks a bonus that is proportional to their actual size,\nthey remain comparable even when relatively small.  In the example\nabove, the OOM killer will discount the 1M agetty's 256 badness points\ndown to 179, and the 10G fork bomb's 262144 points down to 183500 points\nand make the right choice, instead of discounting both to 0 and killing\nagetty because it's first in the task list.\n\nChange-Id: I17b076ed08b870da73fdd39b3187b687e82b972e\nSigned-off-by: David Rientjes <rientjes@google.com>\nReported-by: Johannes Weiner <hannes@cmpxchg.org>\nAcked-by: Johannes Weiner <hannes@cmpxchg.org>\nCc: Michal Hocko <mhocko@suse.cz>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/ff7a4cd6741f9c9cfb41f9bb52587566909a621c"},{"sha":"1516d5af4787b19ff0a8c493620faa6b04843f3a","author":{"name":"Liam Mark","email":"34a322c05ccf7a69003b3e288dfc60055c6d0c33@codeaurora.org"},"message":"mm: vmscan: support complete shrinker reclaim\n\nEnsure that shrinkers are given the option to completely drop\ntheir caches even when their caches are smaller than the batch size.\n\nThis change helps improve memory headroom by ensuring that under\nsignificant memory pressure shrinkers can drop all of their caches.\n\nThis change only attempts to more aggressively call the shrinkers\nduring background memory reclaim inorder to avoid hurting the\nperforamnce of direct memory reclaim.\n\nChange-Id: I8dbc29c054add639e4810e36fd2c8a063e5c52f3\nSigned-off-by: Liam Mark <lmark@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/1516d5af4787b19ff0a8c493620faa6b04843f3a"},{"sha":"bf2224fcea57193fed2ea3b976ef00ff1184ca64","author":{"name":"Jan Kara","email":"596727c8a0ea4db3ba2ceceedccbacd3d7b371b8@suse.cz"},"message":"posix_acl: Clear SGID bit when setting file permissions\n\nWhen file permissions are modified via chmod(2) and the user is not in\nthe owning group or capable of CAP_FSETID, the setgid bit is cleared in\ninode_change_ok().  Setting a POSIX ACL via setxattr(2) sets the file\npermissions as well as the new ACL, but doesn't clear the setgid bit in\na similar way; this allows to bypass the check in chmod(2).  Fix that.\n\nReferences: CVE-2016-7097\nReviewed-by: Christoph Hellwig <hch@lst.de>\nReviewed-by: Jeff Layton <jlayton@redhat.com>\nSigned-off-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Andreas Gruenbacher <agruenba@redhat.com>\nGit-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/\nlinux.git\nGit-commit: 073931017b49d9458aa351605b43a7e34598caef\nChange-Id: Idf7cd8d0fb030fedeabd46254e4c4a9c08bce8b5\n[d-cagle@codeaurora.org: Resolve merge conflicts and style]\nSigned-off-by: Dennis Cagle <d-cagle@codeaurora.org>\n[stummala@codeaurora.org: Resolve merge conflicts on existing files and\nskip files fs/ceph/acl.c, fs/hfsplus/posix_acl.c and fs/jfs/acl.c from\noriginal change as those files are not present/fix is not applicable on\n3.10 kernel]\nSigned-off-by: Sahitya Tummala <stummala@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/bf2224fcea57193fed2ea3b976ef00ff1184ca64"},{"sha":"a8107b024897c35b6025563207b0d084e81db8a1","author":{"name":"Lorenzo Colitti","email":"86995a091f8a1385082bd10715048b52ee386a6a@google.com"},"message":"net: diag: split inet_diag_dump_one_icsk into two\n\nCurrently, inet_diag_dump_one_icsk finds a socket and then dumps\nits information to userspace. Split it into a part that finds the\nsocket and a part that dumps the information.\n\n[Backport of net-next b613f56ec9baf30edf5d9d607b822532a273dad7]\n\nChange-Id: I6b570c35a4928ea072de3e31f9f3ca89668a5244\nSigned-off-by: Lorenzo Colitti <lorenzo@google.com>\nAcked-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/a8107b024897c35b6025563207b0d084e81db8a1"},{"sha":"d742761ab0f634681c219305c1c043e403f580dc","author":{"name":"Lorenzo Colitti","email":"86995a091f8a1385082bd10715048b52ee386a6a@google.com"},"message":"net: diag: Support SOCK_DESTROY for inet sockets.\n\nThis passes the SOCK_DESTROY operation to the underlying protocol\ndiag handler, or returns -EOPNOTSUPP if that handler does not\ndefine a destroy operation.\n\nMost of this patch is just renaming functions. This is not\nstrictly necessary, but it would be fairly counterintuitive to\nhave the code to destroy inet sockets be in a function whose name\nstarts with inet_diag_get.\n\n[Backport of net-next 6eb5d2e08f071c05ecbe135369c9ad418826cab2]\n\nChange-Id: I70a700ec66e0ea8526a17137ba6cb5a3f2dce45f\nSigned-off-by: Lorenzo Colitti <lorenzo@google.com>\nAcked-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/d742761ab0f634681c219305c1c043e403f580dc"},{"sha":"29c433bbf14c14eb55d3041ab5cfac3c55cfd285","author":{"name":"Lorenzo Colitti","email":"86995a091f8a1385082bd10715048b52ee386a6a@google.com"},"message":"net: diag: Support destroying TCP sockets.\n\nThis implements SOCK_DESTROY for TCP sockets. It causes all\nblocking calls on the socket to fail fast with ECONNABORTED and\ncauses a protocol close of the socket. It informs the other end\nof the connection by sending a RST, i.e., initiating a TCP ABORT\nas per RFC 793. ECONNABORTED was chosen for consistency with\nFreeBSD.\n\n[Backport of net-next c1e64e298b8cad309091b95d8436a0255c84f54a]\n\nChange-Id: Ic5410d3a2f39db28a322c30f4b3b2bffd35ec2de\nSigned-off-by: Lorenzo Colitti <lorenzo@google.com>\nAcked-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/29c433bbf14c14eb55d3041ab5cfac3c55cfd285"},{"sha":"611da8b7a3fec1a36c95d995d8e7a83fe0cb89dc","author":{"name":"Lorenzo Colitti","email":"86995a091f8a1385082bd10715048b52ee386a6a@google.com"},"message":"net: tcp: deal with listen sockets properly in tcp_abort.\n\nWhen closing a listen socket, tcp_abort currently calls\ntcp_done without clearing the request queue. If the socket has a\nchild socket that is established but not yet accepted, the child\nsocket is then left without a parent, causing a leak.\n\nFix this by setting the socket state to TCP_CLOSE and calling\ninet_csk_listen_stop with the socket lock held, like tcp_close\ndoes.\n\nTested using net_test. With this patch, calling SOCK_DESTROY on a\nlisten socket that has an established but not yet accepted child\nsocket results in the parent and the child being closed, such\nthat they no longer appear in sock_diag dumps.\n\n[Backport of net-next 2010b93e9317cc12acd20c4aed385af7f9d1681e]\n\nChange-Id: Iaccc56465f159144566b579dbebbbb6e1e943bc7\nReported-by: Eric Dumazet <eric.dumazet@gmail.com>\nSigned-off-by: Lorenzo Colitti <lorenzo@google.com>\nAcked-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/FraEgg/android_kernel_samsung_exynos5420/commits/611da8b7a3fec1a36c95d995d8e7a83fe0cb89dc"}]}
{"actor":{"display_login":"FraEgg"}}