{"push_id":1211959938,"size":44,"distinct_size":44,"ref":"refs/heads/m6.0.1","head":"460969fbf20a541c18c966dbc2331afb37cb200b","before":"8ad6d4d21f2694ebd498c9a6f9fe9b28567563aa","commits":[{"sha":"bda374abd5fa165490d5935905b018528835b416","author":{"name":"Rafael J. Wysocki","email":"eb3c82195bc87396d74859a40992e20b7267b462@intel.com"},"message":"PM / sleep: Add state field to pm_states[] entries\n\ncommit 27ddcc6596e50cb8f03d2e83248897667811d8f6 upstream.\n\nTo allow sleep states corresponding to the \"mem\", \"standby\" and\n\"freeze\" lables to be different from the pm_states[] indexes of\nthose strings, introduce struct pm_sleep_state, consisting of\na string label and a state number, and turn pm_states[] into an\narray of objects of that type.\n\nThis modification should not lead to any functional changes.\n\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nCc: Brian Norris <computersforpeace@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/bda374abd5fa165490d5935905b018528835b416"},{"sha":"a49aeaac39ca02031b4ff293c73c9d184ec98f8a","author":{"name":"Rafael J. Wysocki","email":"eb3c82195bc87396d74859a40992e20b7267b462@intel.com"},"message":"PM / sleep: Use valid_state() for platform-dependent sleep states only\n\ncommit 43e8317b0bba1d6eb85f38a4a233d82d7c20d732 upstream.\n\nUse the observation that, for platform-dependent sleep states\n(PM_SUSPEND_STANDBY, PM_SUSPEND_MEM), a given state is either\nalways supported or always unsupported and store that information\nin pm_states[] instead of calling valid_state() every time we\nneed to check it.\n\nAlso do not use valid_state() for PM_SUSPEND_FREEZE, which is always\nvalid, and move the pm_test_level validity check for PM_SUSPEND_FREEZE\ndirectly into enter_state().\n\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nCc: Brian Norris <computersforpeace@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/a49aeaac39ca02031b4ff293c73c9d184ec98f8a"},{"sha":"06f4ea6c8a60e016eb172e64de3dd19488735449","author":{"name":"Florian Westphal","email":"dbfaf6a80dfd937969ef4cfe4989863cfe354fce@strlen.de"},"message":"netfilter: nf_conntrack: avoid large timeout for mid-stream pickup\n\ncommit 6547a221871f139cc56328a38105d47c14874cbe upstream.\n\nWhen loose tracking is enabled (default), non-syn packets cause\ncreation of new conntracks in established state with default timeout for\nestablished state (5 days).  This causes the table to fill up with UNREPLIED\nwhen the 'new ack' packet happened to be the last-ack of a previous,\nalready timed-out connection.\n\nConsider:\n\nA 192.168.x.52792 > 10.184.y.80: F, 426:426(0) ack 9237 win 255\nB 10.184.y.80 > 192.168.x.52792: ., ack 427 win 123\n<61 second pause>\nC 10.184.y.80 > 192.168.x.52792: F, 9237:9237(0) ack 427 win 123\nD 192.168.x.52792 > 10.184.y.80: ., ack 9238 win 255\n\nB moves conntrack to CLOSE_WAIT and will kill it after 60 second timeout,\nC is ignored (FIN set), but last packet (D) causes new ct with 5-days timeout.\n\nUse UNACK timeout (5 minutes) instead to get rid of these entries sooner\nwhen in ESTABLISHED state without having seen traffic in both directions.\n\nSigned-off-by: Florian Westphal <fw@strlen.de>\nAcked-by: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>\nSigned-off-by: Pablo Neira Ayuso <pablo@netfilter.org>\nCc: Florian Koch <florian.koch1981@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/06f4ea6c8a60e016eb172e64de3dd19488735449"},{"sha":"c9209fba41a3f2380a5e3b83c62fe4652b2e5ac8","author":{"name":"Will Deacon","email":"b2e33b86f3f248a395aadfb8ef1908ac314f4233@arm.com"},"message":"ARM: 7748/1: oabi: handle faults when loading swi instruction from userspace\n\ncommit 1aa2b3b7a6c4f3dbd3671171113a20e6a6190e3b upstream.\n\nRunning an OABI_COMPAT kernel on an SMP platform can lead to fun and\ngames with page aging.\n\nIf one CPU issues a swi instruction immediately before another CPU\ndecides to mkold the page containing the swi instruction, then we will\nfault attempting to load the instruction during the vector_swi handler\nin order to retrieve its immediate field. Since this fault is not\ncurrently dealt with by our exception tables, this results in a panic:\n\n  Unable to handle kernel paging request at virtual address 4020841c\n  pgd = c490c000\n  [4020841c] *pgd=84451831, *pte=bf05859d, *ppte=00000000\n  Internal error: Oops: 17 [#1] PREEMPT SMP ARM\n  Modules linked in: hid_sony(O)\n  CPU: 1    Tainted: G        W  O  (3.4.0-perf-gf496dca-01162-gcbcc62b #1)\n  PC is at vector_swi+0x28/0x88\n  LR is at 0x40208420\n\nThis patch wraps all of the swi instruction loads with the USER macro\nand provides a shared exception table entry which simply rewinds the\nsaved user PC and returns from the system call (without setting tbl, so\nthere's no worries with tracing or syscall restarting). Returning to\nuserspace will re-enter the page fault handler, from where we will\nprobably send SIGSEGV to the current task.\n\nReported-by: Wang, Yalin <yalin.wang@sonymobile.com>\nReviewed-by: Nicolas Pitre <nico@linaro.org>\nSigned-off-by: Will Deacon <will.deacon@arm.com>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>\nCc: Sheng Yong <shengyong1@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/c9209fba41a3f2380a5e3b83c62fe4652b2e5ac8"},{"sha":"8da8c4b0e03c3f2a22f0c43ebc30af20fa3fa5bc","author":{"name":"Heikki Krogerus","email":"3c62c34689f9dfbaa6fbe874458f441fc5ace1cc@linux.intel.com"},"message":"serial: 8250_dma: check the result of TX buffer mapping\n\ncommit d4089a332883ad969700aac5dd4dd5f1c4fee825 upstream.\n\nUsing dma_mapping_error() to make sure the mapping did not\nfail.\n\nSigned-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>\nCc: \"Petallo, MauriceX R\" <mauricex.r.petallo@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/8da8c4b0e03c3f2a22f0c43ebc30af20fa3fa5bc"},{"sha":"a2e192182f3aacc48d22514a7332e4e1578fe7c0","author":{"name":"Jan Kara","email":"7bb7087018cc5fef3c041f6f038f586664845dbf@suse.cz"},"message":"ext2: Fix fs corruption in ext2_get_xip_mem()\n\ncommit 7ba3ec5749ddb61f79f7be17b5fd7720eebc52de upstream.\n\nCommit 8e3dffc651cb \"Ext2: mark inode dirty after the function\ndquot_free_block_nodirty is called\" unveiled a bug in __ext2_get_block()\ncalled from ext2_get_xip_mem(). That function called ext2_get_block()\nmistakenly asking it to map 0 blocks while 1 was intended. Before the\nabove mentioned commit things worked out fine by luck but after that commit\nwe started returning that we allocated 0 blocks while we in fact\nallocated 1 block and thus allocation was looping until all blocks in\nthe filesystem were exhausted.\n\nFix the problem by properly asking for one block and also add assertion\nin ext2_get_blocks() to catch similar problems.\n\nReported-and-tested-by: Andiry Xu <andiry.xu@gmail.com>\nSigned-off-by: Jan Kara <jack@suse.cz>\nCc: Wang Nan <wangnan0@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/a2e192182f3aacc48d22514a7332e4e1578fe7c0"},{"sha":"6cb415b0c8644d04274f08a317ae9716b4491d8f","author":{"name":"Soren Brinkmann","email":"33f40dd66893b55edbfa29cb1b4b76fc26c24299@xilinx.com"},"message":"arm: multi_v7_defconfig: Enable Zynq UART driver\n\ncommit 90de827b9c238f8d8209bc7adc70190575514315 upstream.\n\nSigned-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com>\nSigned-off-by: Michal Simek <michal.simek@xilinx.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/6cb415b0c8644d04274f08a317ae9716b4491d8f"},{"sha":"c7f6119224f4326d148481105e3c15ba0bf04224","author":{"name":"Oleg Nesterov","email":"66df68a59e3b21ba65b9e7f3fee04bb7abd7ddc2@redhat.com"},"message":"oom_kill: change oom_kill.c to use for_each_thread()\n\ncommit 1da4db0cd5c8a31d4468ec906b413e75e604b465 upstream.\n\nChange oom_kill.c to use for_each_thread() rather than the racy\nwhile_each_thread() which can loop forever if we race with exit.\n\nNote also that most users were buggy even if while_each_thread() was\nfine, the task can exit even _before_ rcu_read_lock().\n\nFortunately the new for_each_thread() only requires the stable\ntask_struct, so this change fixes both problems.\n\nSigned-off-by: Oleg Nesterov <oleg@redhat.com>\nReviewed-by: Sergey Dyasly <dserrg@gmail.com>\nTested-by: Sergey Dyasly <dserrg@gmail.com>\nReviewed-by: Sameer Nanda <snanda@chromium.org>\nCc: \"Eric W. Biederman\" <ebiederm@xmission.com>\nCc: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Mandeep Singh Baines <msb@chromium.org>\nCc: \"Ma, Xindong\" <xindong.ma@intel.com>\nReviewed-by: Michal Hocko <mhocko@suse.cz>\nCc: \"Tu, Xiaobing\" <xiaobing.tu@intel.com>\nAcked-by: David Rientjes <rientjes@google.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Li Zefan <lizefan@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/c7f6119224f4326d148481105e3c15ba0bf04224"},{"sha":"3ccfa5fa00422b5753ab655be80f160bf995e5ed","author":{"name":"Oleg Nesterov","email":"66df68a59e3b21ba65b9e7f3fee04bb7abd7ddc2@redhat.com"},"message":"oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()\n\ncommit ad96244179fbd55b40c00f10f399bc04739b8e1f upstream.\n\nAt least out_of_memory() calls has_intersects_mems_allowed() without\neven rcu_read_lock(), this is obviously buggy.\n\nAdd the necessary rcu_read_lock().  This means that we can not simply\nreturn from the loop, we need \"bool ret\" and \"break\".\n\nWhile at it, swap the names of task_struct's (the argument and the\nlocal).  This cleans up the code a little bit and avoids the unnecessary\ninitialization.\n\nSigned-off-by: Oleg Nesterov <oleg@redhat.com>\nReviewed-by: Sergey Dyasly <dserrg@gmail.com>\nTested-by: Sergey Dyasly <dserrg@gmail.com>\nReviewed-by: Sameer Nanda <snanda@chromium.org>\nCc: \"Eric W. Biederman\" <ebiederm@xmission.com>\nCc: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Mandeep Singh Baines <msb@chromium.org>\nCc: \"Ma, Xindong\" <xindong.ma@intel.com>\nReviewed-by: Michal Hocko <mhocko@suse.cz>\nCc: \"Tu, Xiaobing\" <xiaobing.tu@intel.com>\nAcked-by: David Rientjes <rientjes@google.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Li Zefan <lizefan@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/3ccfa5fa00422b5753ab655be80f160bf995e5ed"},{"sha":"48ca1d01084e2ec82adc50c404db15710910c7e0","author":{"name":"Oleg Nesterov","email":"66df68a59e3b21ba65b9e7f3fee04bb7abd7ddc2@redhat.com"},"message":"oom_kill: add rcu_read_lock() into find_lock_task_mm()\n\ncommit 4d4048be8a93769350efa31d2482a038b7de73d0 upstream.\n\nfind_lock_task_mm() expects it is called under rcu or tasklist lock, but\nit seems that at least oom_unkillable_task()->task_in_mem_cgroup() and\nmem_cgroup_out_of_memory()->oom_badness() can call it lockless.\n\nPerhaps we could fix the callers, but this patch simply adds rcu lock\ninto find_lock_task_mm().  This also allows to simplify a bit one of its\ncallers, oom_kill_process().\n\nSigned-off-by: Oleg Nesterov <oleg@redhat.com>\nCc: Sergey Dyasly <dserrg@gmail.com>\nCc: Sameer Nanda <snanda@chromium.org>\nCc: \"Eric W. Biederman\" <ebiederm@xmission.com>\nCc: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Mandeep Singh Baines <msb@chromium.org>\nCc: \"Ma, Xindong\" <xindong.ma@intel.com>\nReviewed-by: Michal Hocko <mhocko@suse.cz>\nCc: \"Tu, Xiaobing\" <xiaobing.tu@intel.com>\nAcked-by: David Rientjes <rientjes@google.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Li Zefan <lizefan@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/48ca1d01084e2ec82adc50c404db15710910c7e0"},{"sha":"a26d518645bb64771fd962d11dc7ef68edc5be47","author":{"name":"Oleg Nesterov","email":"66df68a59e3b21ba65b9e7f3fee04bb7abd7ddc2@redhat.com"},"message":"vm_is_stack: use for_each_thread() rather then buggy while_each_thread()\n\ncommit 4449a51a7c281602d3a385044ab928322a122a02 upstream.\n\nAleksei hit the soft lockup during reading /proc/PID/smaps.  David\ninvestigated the problem and suggested the right fix.\n\nwhile_each_thread() is racy and should die, this patch updates\nvm_is_stack().\n\nSigned-off-by: Oleg Nesterov <oleg@redhat.com>\nReported-by: Aleksei Besogonov <alex.besogonov@gmail.com>\nTested-by: Aleksei Besogonov <alex.besogonov@gmail.com>\nSuggested-by: David Rientjes <rientjes@google.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Li Zefan <lizefan@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/a26d518645bb64771fd962d11dc7ef68edc5be47"},{"sha":"392bec83b90786f5785973d01c3434951a18be2f","author":{"name":"Greg Kroah-Hartman","email":"4931344b09d7a7d3573e8b1ebec918e229ead9bf@linuxfoundation.org"},"message":"Linux 3.10.56","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/392bec83b90786f5785973d01c3434951a18be2f"},{"sha":"1118567f03df4c1efdf0026712240884c83d1b78","author":{"name":"Jan Kara","email":"7bb7087018cc5fef3c041f6f038f586664845dbf@suse.cz"},"message":"udf: Avoid infinite loop when processing indirect ICBs\n\ncommit c03aa9f6e1f938618e6db2e23afef0574efeeb65 upstream.\n\nWe did not implement any bound on number of indirect ICBs we follow when\nloading inode. Thus corrupted medium could cause kernel to go into an\ninfinite loop, possibly causing a stack overflow.\n\nFix the possible stack overflow by removing recursion from\n__udf_read_inode() and limit number of indirect ICBs we follow to avoid\ninfinite loops.\n\nSigned-off-by: Jan Kara <jack@suse.cz>\nCc: Chuck Ebbert <cebbert.lkml@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/1118567f03df4c1efdf0026712240884c83d1b78"},{"sha":"c0ceb0a8c7c1da69ea90d40ea74d36f1f48660c1","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"perf: fix perf bug in fork()\n\ncommit 6c72e3501d0d62fc064d3680e5234f3463ec5a86 upstream.\n\nOleg noticed that a cleanup by Sylvain actually uncovered a bug; by\ncalling perf_event_free_task() when failing sched_fork() we will not yet\nhave done the memset() on ->perf_event_ctxp[] and will therefore try and\n'free' the inherited contexts, which are still in use by the parent\nprocess.  This is bad..\n\nSuggested-by: Oleg Nesterov <oleg@redhat.com>\nReported-by: Oleg Nesterov <oleg@redhat.com>\nReported-by: Sylvain 'ythier' Hitier <sylvain.hitier@gmail.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Ingo Molnar <mingo@kernel.org>\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/roguesyko/the_reaper_shamu/commits/c0ceb0a8c7c1da69ea90d40ea74d36f1f48660c1"},{"sha":"3865e69494d802c92a7ae3e92bb9f414aa0f2310","author":{"name":"Josh Triplett","email":"2d27c8320aa3eefe09ead96ce62c361629bc5ad6@joshtriplett.org"},"message":"init/Kconfig: Fix HAVE_FUTEX_CMPXCHG to not break up the EXPERT menu\n\ncommit 62b4d2041117f35ab2409c9f5c4b8d3dc8e59d0f upstream.\n\ncommit 03b8c7b623c80af264c4c8d6111e5c6289933666 (\"futex: Allow\narchitectures to skip futex_atomic_cmpxchg_inatomic() test\") added the\nHAVE_FUTEX_CMPXCHG symbol right below FUTEX.  This placed it right in\nthe middle of the options for the EXPERT menu.  However,\nHAVE_FUTEX_CMPXCHG does not depend on EXPERT or FUTEX, so Kconfig stops\nplacing items in the EXPERT menu, and displays the remaining several\nEXPERT items (starting with EPOLL) directly in the General Setup menu.\n\nSince both users of HAVE_FUTEX_CMPXCHG only select it \"if FUTEX\", make\nHAVE_FUTEX_CMPXCHG itself depend on FUTEX.  With this change, the\nsubsequent items display as part of the EXPERT menu again; the EMBEDDED\nmenu now appears as the next top-level item in the General Setup menu,\nwhich makes General Setup much shorter and more usable.\n\nSigned-off-by: Josh Triplett <josh@joshtriplett.org>\nAcked-by: Randy Dunlap <rdunlap@infradead.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/3865e69494d802c92a7ae3e92bb9f414aa0f2310"},{"sha":"6500ce2dbdbe105bc2f38b931e2f381d95594681","author":{"name":"Steven Rostedt (Red Hat)","email":"9f626a07de58780741a9085807c77fd646ef3459@goodmis.org"},"message":"ring-buffer: Fix infinite spin in reading buffer\n\ncommit 24607f114fd14f2f37e3e0cb3d47bce96e81e848 upstream.\n\nCommit 651e22f2701b \"ring-buffer: Always reset iterator to reader page\"\nfixed one bug but in the process caused another one. The reset is to\nupdate the header page, but that fix also changed the way the cached\nreads were updated. The cache reads are used to test if an iterator\nneeds to be updated or not.\n\nA ring buffer iterator, when created, disables writes to the ring buffer\nbut does not stop other readers or consuming reads from happening.\nAlthough all readers are synchronized via a lock, they are only\nsynchronized when in the ring buffer functions. Those functions may\nbe called by any number of readers. The iterator continues down when\nits not interrupted by a consuming reader. If a consuming read\noccurs, the iterator starts from the beginning of the buffer.\n\nThe way the iterator sees that a consuming read has happened since\nits last read is by checking the reader \"cache\". The cache holds the\nlast counts of the read and the reader page itself.\n\nCommit 651e22f2701b changed what was saved by the cache_read when\nthe rb_iter_reset() occurred, making the iterator never match the cache.\nThen if the iterator calls rb_iter_reset(), it will go into an\ninfinite loop by checking if the cache doesn't match, doing the reset\nand retrying, just to see that the cache still doesn't match! Which\nshould never happen as the reset is suppose to set the cache to the\ncurrent value and there's locks that keep a consuming reader from\nhaving access to the data.\n\nFixes: 651e22f2701b \"ring-buffer: Always reset iterator to reader page\"\nSigned-off-by: Steven Rostedt <rostedt@goodmis.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/6500ce2dbdbe105bc2f38b931e2f381d95594681"},{"sha":"477588f7c469c88bef3c12bed57fdd566db7335c","author":{"name":"Waiman Long","email":"65679e2ce00c6e0cc2dfd4b35628d2fc0318e447@hp.com"},"message":"mm, thp: move invariant bug check out of loop in __split_huge_page_map\n\ncommit f8303c2582b889351e261ff18c4d8eb197a77db2 upstream.\n\nIn __split_huge_page_map(), the check for page_mapcount(page) is\ninvariant within the for loop.  Because of the fact that the macro is\nimplemented using atomic_read(), the redundant check cannot be optimized\naway by the compiler leading to unnecessary read to the page structure.\n\nThis patch moves the invariant bug check out of the loop so that it will\nbe done only once.  On a 3.16-rc1 based kernel, the execution time of a\nmicrobenchmark that broke up 1000 transparent huge pages using munmap()\nhad an execution time of 38,245us and 38,548us with and without the\npatch respectively.  The performance gain is about 1%.\n\nSigned-off-by: Waiman Long <Waiman.Long@hp.com>\nAcked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>\nCc: Andrea Arcangeli <aarcange@redhat.com>\nCc: Mel Gorman <mgorman@suse.de>\nCc: Rik van Riel <riel@redhat.com>\nCc: Scott J Norton <scott.norton@hp.com>\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/roguesyko/the_reaper_shamu/commits/477588f7c469c88bef3c12bed57fdd566db7335c"},{"sha":"dc19a0a653f83da80dd207e6329f48faa69b6d8a","author":{"name":"Mel Gorman","email":"7e4a4144b35252848d9a801e3e6fca62e0cbe9e6@suse.de"},"message":"mm: numa: Do not mark PTEs pte_numa when splitting huge pages\n\ncommit abc40bd2eeb77eb7c2effcaf63154aad929a1d5f upstream.\n\nThis patch reverts 1ba6e0b50b (\"mm: numa: split_huge_page: transfer the\nNUMA type from the pmd to the pte\"). If a huge page is being split due\na protection change and the tail will be in a PROT_NONE vma then NUMA\nhinting PTEs are temporarily created in the protected VMA.\n\n VM_RW|VM_PROTNONE\n|-----------------|\n      ^\n      split here\n\nIn the specific case above, it should get fixed up by change_pte_range()\nbut there is a window of opportunity for weirdness to happen. Similarly,\nif a huge page is shrunk and split during a protection update but before\npmd_numa is cleared then a pte_numa can be left behind.\n\nInstead of adding complexity trying to deal with the case, this patch\nwill not mark PTEs NUMA when splitting a huge page. NUMA hinting faults\nwill not be triggered which is marginal in comparison to the complexity\nin dealing with the corner cases during THP split.\n\nSigned-off-by: Mel Gorman <mgorman@suse.de>\nAcked-by: Rik van Riel <riel@redhat.com>\nAcked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>\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/roguesyko/the_reaper_shamu/commits/dc19a0a653f83da80dd207e6329f48faa69b6d8a"},{"sha":"b6c53ab9113257f0078b727da9294380a105225b","author":{"name":"Hans Verkuil","email":"aeb1fa9b7f4f5be44f239b597abfb2c97d8cd0b0@cisco.com"},"message":"media: vb2: fix VBI/poll regression\n\ncommit 58d75f4b1ce26324b4d809b18f94819843a98731 upstream.\n\nThe recent conversion of saa7134 to vb2 unconvered a poll() bug that\nbroke the teletext applications alevt and mtt. These applications\nexpect that calling poll() without having called VIDIOC_STREAMON will\ncause poll() to return POLLERR. That did not happen in vb2.\n\nThis patch fixes that behavior. It also fixes what should happen when\npoll() is called when STREAMON is called but no buffers have been\nqueued. In that case poll() will also return POLLERR, but only for\ncapture queues since output queues will always return POLLOUT\nanyway in that situation.\n\nThis brings the vb2 behavior in line with the old videobuf behavior.\n\nSigned-off-by: Hans Verkuil <hans.verkuil@cisco.com>\nAcked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nSigned-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/b6c53ab9113257f0078b727da9294380a105225b"},{"sha":"f9811a265d2e679a2971a37157627668a0b33a58","author":{"name":"NeilBrown","email":"2d905a3497a379bccf401a15c6d441d61e66863c@suse.de"},"message":"md/raid5: disable 'DISCARD' by default due to safety concerns.\n\ncommit 8e0e99ba64c7ba46133a7c8a3e3f7de01f23bd93 upstream.\n\nIt has come to my attention (thanks Martin) that 'discard_zeroes_data'\nis only a hint.  Some devices in some cases don't do what it\nsays on the label.\n\nThe use of DISCARD in RAID5 depends on reads from discarded regions\nbeing predictably zero.  If a write to a previously discarded region\nperforms a read-modify-write cycle it assumes that the parity block\nwas consistent with the data blocks.  If all were zero, this would\nbe the case.  If some are and some aren't this would not be the case.\nThis could lead to data corruption after a device failure when\ndata needs to be reconstructed from the parity.\n\nAs we cannot trust 'discard_zeroes_data', ignore it by default\nand so disallow DISCARD on all raid4/5/6 arrays.\n\nAs many devices are trustworthy, and as there are benefits to using\nDISCARD, add a module parameter to over-ride this caution and cause\nDISCARD to work if discard_zeroes_data is set.\n\nIf a site want to enable DISCARD on some arrays but not on others they\nshould select DISCARD support at the filesystem level, and set the\nraid456 module parameter.\n    raid456.devices_handle_discard_safely=Y\n\nAs this is a data-safety issue, I believe this patch is suitable for\n-stable.\nDISCARD support for RAID456 was added in 3.7\n\nCc: Shaohua Li <shli@kernel.org>\nCc: \"Martin K. Petersen\" <martin.petersen@oracle.com>\nCc: Mike Snitzer <snitzer@redhat.com>\nCc: Heinz Mauelshagen <heinzm@redhat.com>\nAcked-by: Martin K. Petersen <martin.petersen@oracle.com>\nAcked-by: Mike Snitzer <snitzer@redhat.com>\nFixes: 620125f2bf8ff0c4969b79653b54d7bcc9d40637\nSigned-off-by: NeilBrown <neilb@suse.de>\n[bwh: Backported to 3.10: adjust context]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/roguesyko/the_reaper_shamu/commits/f9811a265d2e679a2971a37157627668a0b33a58"}]}
{"actor":{"display_login":"roguesyko"}}