GitHub PushEvent at 2014-06-12 08:01:36
Repository: arne_f-linux
Actor: mtremer
Payload: {"shas":[["e58d78f941db4f728cd05335be7c90246ab83e7c","43232e92d70cc7aa53504ad0397085ee47bad87f@goodmis.org","sched: Use CPUPRI_NR_PRIORITIES instead of MAX_RT_PRIO in cpupri check\n\ncommit 6227cb00cc120f9a43ce8313bb0475ddabcb7d01 upstream.\n\nThe check at the beginning of cpupri_find() makes sure that the task_pri\nvariable does not exceed the cp->pri_to_cpu array length. But that length\nis CPUPRI_NR_PRIORITIES not MAX_RT_PRIO, where it will miss the last two\npriorities in that array.\n\nAs task_pri is computed from convert_prio() which should never be bigger\nthan CPUPRI_NR_PRIORITIES, if the check should cause a panic if it is\nhit.\n\nReported-by: Mike Galbraith <umgwanakikbuti@gmail.com>\nSigned-off-by: Steven Rostedt <rostedt@goodmis.org>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/1397015410.5212.13.camel@marge.simpson.net\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Steven Rostedt (Red Hat)",true],["ecaf19a7685c6359e80ec02e4c9e5930481c2087","00e4cf8f46a57000a44449bf9dd8cbbcc209fd2a@linutronix.de","sched: Sanitize irq accounting madness\n\ncommit 2d513868e2a33e1d5315490ef4c861ee65babd65 upstream.\n\nRussell reported, that irqtime_account_idle_ticks() takes ages due to:\n\n       for (i = 0; i < ticks; i++)\n               irqtime_account_process_tick(current, 0, rq);\n\nIt's sad, that this code was written way _AFTER_ the NOHZ idle\nfunctionality was available. I charge myself guitly for not paying\nattention when that crap got merged with commit abb74cefa (\"sched:\nExport ns irqtimes through /proc/stat\")\n\nSo instead of looping nr_ticks times just apply the whole thing at\nonce.\n\nAs a side note: The whole cputime_t vs. u64 business in that context\nwants to be cleaned up as well. There is no point in having all these\nback and forth conversions. Lets standardise on u64 nsec for all\nkernel internal accounting and be done with it. Everything else does\nnot make sense at all for fine grained accounting. Frederic, can you\nplease take care of that?\n\nReported-by: Russell King <rmk+kernel@arm.linux.org.uk>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nReviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nCc: Venkatesh Pallipadi <venki@google.com>\nCc: Shaun Ruffell <sruffell@digium.com>\nLink: http://lkml.kernel.org/r/alpine.DEB.2.02.1405022307000.6261@ionos.tec.linutronix.de\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Thomas Gleixner",true],["266166041bd6195b0d1ecbb1c4753aa00569112f","2c6594f608aa3d41e98d48846a6328831f7084ad@redhat.com","perf: Prevent false warning in perf_swevent_add\n\ncommit 39af6b1678afa5880dda7e375cf3f9d395087f6d upstream.\n\nThe perf cpu offline callback takes down all cpu context\nevents and releases swhash->swevent_hlist.\n\nThis could race with task context software event being just\nscheduled on this cpu via perf_swevent_add while cpu hotplug\ncode already cleaned up event's data.\n\nThe race happens in the gap between the cpu notifier code\nand the cpu being actually taken down. Note that only cpu\nctx events are terminated in the perf cpu hotplug code.\n\nIt's easily reproduced with:\n  $ perf record -e faults perf bench sched pipe\n\nwhile putting one of the cpus offline:\n  # echo 0 > /sys/devices/system/cpu/cpu1/online\n\nConsole emits following warning:\n  WARNING: CPU: 1 PID: 2845 at kernel/events/core.c:5672 perf_swevent_add+0x18d/0x1a0()\n  Modules linked in:\n  CPU: 1 PID: 2845 Comm: sched-pipe Tainted: G        W    3.14.0+ #256\n  Hardware name: Intel Corporation Montevina platform/To be filled by O.E.M., BIOS AMVACRB1.86C.0066.B00.0805070703 05/07/2008\n   0000000000000009 ffff880077233ab8 ffffffff81665a23 0000000000200005\n   0000000000000000 ffff880077233af8 ffffffff8104732c 0000000000000046\n   ffff88007467c800 0000000000000002 ffff88007a9cf2a0 0000000000000001\n  Call Trace:\n   [<ffffffff81665a23>] dump_stack+0x4f/0x7c\n   [<ffffffff8104732c>] warn_slowpath_common+0x8c/0xc0\n   [<ffffffff8104737a>] warn_slowpath_null+0x1a/0x20\n   [<ffffffff8110fb3d>] perf_swevent_add+0x18d/0x1a0\n   [<ffffffff811162ae>] event_sched_in.isra.75+0x9e/0x1f0\n   [<ffffffff8111646a>] group_sched_in+0x6a/0x1f0\n   [<ffffffff81083dd5>] ? sched_clock_local+0x25/0xa0\n   [<ffffffff811167e6>] ctx_sched_in+0x1f6/0x450\n   [<ffffffff8111757b>] perf_event_sched_in+0x6b/0xa0\n   [<ffffffff81117a4b>] perf_event_context_sched_in+0x7b/0xc0\n   [<ffffffff81117ece>] __perf_event_task_sched_in+0x43e/0x460\n   [<ffffffff81096f1e>] ? put_lock_stats.isra.18+0xe/0x30\n   [<ffffffff8107b3c8>] finish_task_switch+0xb8/0x100\n   [<ffffffff8166a7de>] __schedule+0x30e/0xad0\n   [<ffffffff81172dd2>] ? pipe_read+0x3e2/0x560\n   [<ffffffff8166b45e>] ? preempt_schedule_irq+0x3e/0x70\n   [<ffffffff8166b45e>] ? preempt_schedule_irq+0x3e/0x70\n   [<ffffffff8166b464>] preempt_schedule_irq+0x44/0x70\n   [<ffffffff816707f0>] retint_kernel+0x20/0x30\n   [<ffffffff8109e60a>] ? lockdep_sys_exit+0x1a/0x90\n   [<ffffffff812a4234>] lockdep_sys_exit_thunk+0x35/0x67\n   [<ffffffff81679321>] ? sysret_check+0x5/0x56\n\nFixing this by tracking the cpu hotplug state and displaying\nthe WARN only if current cpu is initialized properly.\n\nCc: Corey Ashford <cjashfor@linux.vnet.ibm.com>\nCc: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Paul Mackerras <paulus@samba.org>\nCc: Arnaldo Carvalho de Melo <acme@redhat.com>\nReported-by: Fengguang Wu <fengguang.wu@intel.com>\nSigned-off-by: Jiri Olsa <jolsa@redhat.com>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/1396861448-10097-1-git-send-email-jolsa@redhat.com\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Jiri Olsa",true],["95090e8a573c7743a2b0d800c4c52fac581e5bbe","3fddac958924aef220f202ca567388ddab3f14a8@infradead.org","perf: Limit perf_event_attr::sample_period to 63 bits\n\ncommit 0819b2e30ccb93edf04876237b6205eef84ec8d2 upstream.\n\nVince reported that using a large sample_period (one with bit 63 set)\nresults in wreckage since while the sample_period is fundamentally\nunsigned (negative periods don't make sense) the way we implement\nthings very much rely on signed logic.\n\nSo limit sample_period to 63 bits to avoid tripping over this.\n\nReported-by: Vince Weaver <vincent.weaver@maine.edu>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/n/tip-p25fhunibl4y3qi0zuqmyf4b@git.kernel.org\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Peter Zijlstra",true],["54b3f8df1fc2d8f69862ed617c89c0304dc5f04b","3fddac958924aef220f202ca567388ddab3f14a8@infradead.org","perf: Fix race in removing an event\n\ncommit 46ce0fe97a6be7532ce6126bb26ce89fed81528c upstream.\n\nWhen removing a (sibling) event we do:\n\n\traw_spin_lock_irq(&ctx->lock);\n\tperf_group_detach(event);\n\traw_spin_unlock_irq(&ctx->lock);\n\n\t<hole>\n\n\tperf_remove_from_context(event);\n\t\traw_spin_lock_irq(&ctx->lock);\n\t\t...\n\t\traw_spin_unlock_irq(&ctx->lock);\n\nNow, assuming the event is a sibling, it will be 'unreachable' for\nthings like ctx_sched_out() because that iterates the\ngroups->siblings, and we just unhooked the sibling.\n\nSo, if during <hole> we get ctx_sched_out(), it will miss the event\nand not call event_sched_out() on it, leaving it programmed on the\nPMU.\n\nThe subsequent perf_remove_from_context() call will find the ctx is\ninactive and only call list_del_event() to remove the event from all\nother lists.\n\nHereafter we can proceed to free the event; while still programmed!\n\nClose this hole by moving perf_group_detach() inside the same\nctx->lock region(s) perf_remove_from_context() has.\n\nThe condition on inherited events only in __perf_event_exit_task() is\nlikely complete crap because non-inherited events are part of groups\ntoo and we're tearing down just the same. But leave that for another\npatch.\n\nMost-likely-Fixes: e03a9a55b4e (\"perf: Change close() semantics for group events\")\nReported-by: Vince Weaver <vincent.weaver@maine.edu>\nTested-by: Vince Weaver <vincent.weaver@maine.edu>\nMuch-staring-at-traces-by: Vince Weaver <vincent.weaver@maine.edu>\nMuch-staring-at-traces-by: Thomas Gleixner <tglx@linutronix.de>\nCc: Arnaldo Carvalho de Melo <acme@kernel.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/20140505093124.GN17778@laptop.programming.kicks-ass.net\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Peter Zijlstra",true],["509a6ce860fc71a16cdeed25b131c26d4917a0a6","b80c1600f604d3b0d768f26f90a76757e76005dd@gmail.com","perf evsel: Fix printing of perf_event_paranoid message\n\ncommit b69e63a45f2d96a0dfe930ed20385058d4574d2f upstream.\n\nmessage is currently shown as:\n\n  Error:\n  You may not have permission to collect %sstats.\n  Consider tweaking /proc/sys/kernel/perf_event_paranoid:\n\nNote the %sstats. With patch this becomes:\n\n  Error:\n  You may not have permission to collect stats.\n  Consider tweaking /proc/sys/kernel/perf_event_paranoid:\n\nSigned-off-by: David Ahern <dsahern@gmail.com>\nCc: Jiri Olsa <jolsa@redhat.com>\nLink: http://lkml.kernel.org/r/1369526040-1368-1-git-send-email-dsahern@gmail.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nCc: xiakaixu <xiakaixu@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","David Ahern",true],["53e8565ac009becf0e27c2c77980426f1b40db09","8e7a128cd0264d3269a891fb3e87507c2985f8af@ah.jp.nec.com","mm/memory-failure.c: fix memory leak by race between poison and unpoison\n\ncommit 3e030ecc0fc7de10fd0da10c1c19939872a31717 upstream.\n\nWhen a memory error happens on an in-use page or (free and in-use)\nhugepage, the victim page is isolated with its refcount set to one.\n\nWhen you try to unpoison it later, unpoison_memory() calls put_page()\nfor it twice in order to bring the page back to free page pool (buddy or\nfree hugepage list).  However, if another memory error occurs on the\npage which we are unpoisoning, memory_failure() returns without\nreleasing the refcount which was incremented in the same call at first,\nwhich results in memory leak and unconsistent num_poisoned_pages\nstatistics.  This patch fixes it.\n\nSigned-off-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>\nCc: Andi Kleen <andi@firstfloor.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>","Naoya Horiguchi",true],["267da3199e97cc66be842ef255bcd681dd1fdfc5","bff32994ff0f8d048f262a8388145a71b6071bfe@intel.com","Documentation: fix DOCBOOKS=... building\n\ncommit e60cbeedc48d80689c249ab5dcc3c31ad0452dea upstream.\n\nPrior to commit 4266129964b8 (\"[media] DocBook: Move all media docbook\nstuff into its own directory\") it was possible to build only a single\n(or more) book(s) by calling, for example\n\n    make htmldocs DOCBOOKS=80211.xml\n\nThis now fails:\n\n    cp: target `.../Documentation/DocBook//media_api' is not a directory\n\nIgnore errors from that copy to make this possible again.\n\nFixes: 4266129964b8 (\"[media] DocBook: Move all media docbook stuff into its own directory\")\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\nAcked-by: Randy Dunlap <rdunlap@xenotime.net>\nCc: Mauro Carvalho Chehab <mchehab@redhat.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>","Johannes Berg",true],["afe687819d8a4bf19ddceb14f734c3bbe9fff66c","efca98801f3398ebd7eeff805a2c18e6c49e84d4@suse.de","hwmon: (ntc_thermistor) Fix dependencies\n\ncommit 59cf4243e557aa64ab2ef51280454aa1f3828e14 upstream.\n\nIn commit 9e8269de, support was added for ntc_thermistor devices being\ndeclared in the device tree and implemented on top of IIO. With that\nchange, a dependency was added to the ntc_thermistor driver:\n\n\tdepends on (!OF && !IIO) || (OF && IIO)\n\nThis construct has the drawback that the driver can no longer be\nselected when OF is set and IIO isn't, nor when IIO is set and OF is\nnot. This is a regression for the original users of the driver.\n\nAs the new code depends on IIO and is useless without OF, include it\nonly if both are enabled, and set the dependencies accordingly. This\nis clearer, more simple and more correct.\n\nSigned-off-by: Jean Delvare <jdelvare@suse.de>\nFixes: 9e8269de hwmon: (ntc_thermistor) Add DT with IIO support to NTC thermistor driver\nReviewed-by: Guenter Roeck <linux@roeck-us.net>\nCc: Naveen Krishna Chatradhi <ch.naveen@samsung.com>\nCc: Doug Anderson <dianders@chromium.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Jean Delvare",true],["13a3538413f03be9e9e3222fb11a18d319b649e1","efca98801f3398ebd7eeff805a2c18e6c49e84d4@suse.de","hwmon: (ntc_thermistor) Fix OF device ID mapping\n\ncommit ead82d6792ef5c600d535bca6ec50a4da14ff7c7 upstream.\n\nThe mapping from OF device IDs to platform device IDs is wrong.\nTYPE_NCPXXWB473 is 0, TYPE_NCPXXWL333 is 1, so\nntc_thermistor_id[TYPE_NCPXXWB473] is { \"ncp15wb473\", TYPE_NCPXXWB473 }\nwhile\nntc_thermistor_id[TYPE_NCPXXWL333] is { \"ncp18wb473\", TYPE_NCPXXWB473 }.\n\nSo the name is wrong for all but the \"ntc,ncp15wb473\" entry, and the\ntype is wrong for the \"ntc,ncp15wl333\" entry.\n\nSo map the entries by index, it is neither elegant nor robust but at\nleast it is correct.\n\nSigned-off-by: Jean Delvare <jdelvare@suse.de>\nFixes: 9e8269de hwmon: (ntc_thermistor) Add DT with IIO support to NTC thermistor driver\nReviewed-by: Guenter Roeck <linux@roeck-us.net>\nCc: Naveen Krishna Chatradhi <ch.naveen@samsung.com>\nCc: Doug Anderson <dianders@chromium.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Jean Delvare",true],["df9cddcf99bfe73a6b4328c14593749f3facfa89","d9f27fb07c1e9f131223ad827fa5179f3846c30b@redhat.com","drm/gf119-/disp: fix nasty bug which can clobber SOR0's clock setup\n\ncommit 0f1d360b2ee3a2a0f510d3f1bcd3f5ebe5d41265 upstream.\n\nFixes a LVDS bleed issue on Lenovo W530 that can occur under a\nnumber of circumstances.\n\nSigned-off-by: Ben Skeggs <bskeggs@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Ben Skeggs",true],["739b79fb90dd187f5377aa9ddaaaa2470007ddf6","c7ea837d7a46effe4232b086213468b8b31643bf@amd.com","drm/radeon: also try GART for CPU accessed buffers\n\ncommit 544092596e8ac269f70e70961b5e9381909c9b1e upstream.\n\nPlacing them exclusively into VRAM might not work all the time.\n\nFixes: https://bugs.freedesktop.org/show_bug.cgi?id=78297\n\nSigned-off-by: Christian König <christian.koenig@amd.com>\nReviewed-by: Alex Deucher <alexander.deucher@amd.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Christian König",true],["caf3d430ba12e30567f20950b62faa51a264ca38","bf84f557a1e54fd62cd73c6847f7d9df60e9fbef@gmail.com","drm/radeon: handle non-VGA class pci devices with ATRM\n\ncommit d8ade3526b2aa0505132c404c05a38b73ea15490 upstream.\n\nNewer PX systems have non-VGA pci class dGPUs.  Update\nthe ATRM fetch method to handle those cases.\n\nbug:\nhttps://bugzilla.kernel.org/show_bug.cgi?id=75401\n\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\nSigned-off-by: Christian König <christian.koenig@amd.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Alex Deucher",true],["6a93022f1d099b66b573aac243a4df890fd0a1c4","8f82f727ceef69ddbc9c99a3e77927715fed00fe@gmail.com","ARM: imx: fix error handling in ipu device registration\n\ncommit d1d70e5dc2cfa9047bb935c41ba808ebb8135696 upstream.\n\nIf we fail to allocate struct platform_device pdev we\ndereference it after the goto label err.\n\nThis bug was found using coccinelle.\n\nFixes: afa77ef (ARM: mx3: dynamically allocate \"ipu-core\" devices)\nSigned-off-by: Emil Goode <emilgoode@gmail.com>\nAcked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>\nSigned-off-by: Shawn Guo <shawn.guo@freescale.com>\nSigned-off-by: Olof Johansson <olof@lixom.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Emil Goode",true],["8d1bf0a204da672b10874ba91907ef0492288a7a","ae960578cc5eca7b9b1dbc37d9caa6cb634f35e0@ideasonboard.com","ARM: OMAP3: clock: Back-propagate rate change from cam_mclk to dpll4_m5 on all OMAP3 platforms\n\ncommit 98d7e1aee6dd534f468993f8c6a1bc730d4cfa81 upstream.\n\nCommit 7b2e1277598e4187c9be3e61fd9b0f0423f97986 (\"ARM: OMAP3: clock:\nBack-propagate rate change from cam_mclk to dpll4_m5\") enabled clock\nrate back-propagation from cam_mclk do dpll4_m5 on OMAP3630 only.\nPerform back-propagation on other OMAP3 platforms as well.\n\nReported-by: Jean-Philippe François <jp.francois@cynove.com>\nSigned-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nSigned-off-by: Paul Walmsley <paul@pwsan.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Laurent Pinchart",true],["c506847413e50969d24e26bc00595e982796a5dc","5b4d8dc9ea337fff5fd1729321eda9873ade0b09@ti.com","ARM: OMAP4: Fix the boot regression with CPU_IDLE enabled\n\ncommit 4b353a706a86598ba47307c47301c3c428b79e09 upstream.\n\nOn OMAP4 panda board, there have been several bug reports about boot\nhang and lock-ups with CPU_IDLE enabled. The root cause of the issue\nis missing interrupts while in idle state. Commit cb7094e8 {cpuidle / omap4 :\nuse CPUIDLE_FLAG_TIMER_STOP flag} moved the broadcast notifiers to common\ncode for right reasons but on OMAP4 which suffers from a nasty ROM code\nbug with GIC, commit ff999b8a {ARM: OMAP4460: Workaround for ROM bug ..},\nwe loose interrupts which leads to issues like lock-up, hangs etc.\n\nPatch reverts commit cb7094 {cpuidle / omap4 : use CPUIDLE_FLAG_TIMER_STOP\nflag} and 54769d6 {cpuidle: OMAP4: remove timer broadcast initialization} to\navoid the issue. With this change, OMAP4 panda boards, the mentioned\nissues are getting fixed. We no longer loose interrupts which was the cause\nof the regression.\n\nFixes: cb7094e8 (cpuidle / omap4 : use CPUIDLE_FLAG_TIMER_STOP flag)\nFixes: ff999b8a (cpuidle: OMAP4: remove timer broadcast initialization)\nCc: Roger Quadros <rogerq@ti.com>\nCc: Kevin Hilman <khilman@linaro.org>\nCc: Tony Lindgren <tony@atomide.com>\nCc: Daniel Lezcano <daniel.lezcano@linaro.org>\nReported-tested-by: Roger Quadros <rogerq@ti.com>\nReported-tested-by: Kevin Hilman <khilman@linaro.org>\nTested-by: Tony Lindgren <tony@atomide.com>\nSigned-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Santosh Shilimkar",true],["b1da22af26d907e88925c2ce1a9ee527bd899875","d7a2c23eccda99639e3fab64d868a1b1895748fa@samsung.com","ARM: 8051/1: put_user: fix possible data corruption in put_user\n\ncommit 537094b64b229bf3ad146042f83e74cf6abe59df upstream.\n\nAccording to arm procedure call standart r2 register is call-cloberred.\nSo after the result of x expression was put into r2 any following\nfunction call in p may overwrite r2. To fix this, the result of p\nexpression must be saved to the temporary variable before the\nassigment x expression to __r2.\n\nSigned-off-by: Andrey Ryabinin <a.ryabinin@samsung.com>\nReviewed-by: Nicolas Pitre <nico@linaro.org>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Andrey Ryabinin",true],["50faf9370b0aa357a9d114faafc2327505547928","4beca5398d608e62d2566fc23741b57e67f35e89@redhat.com","dm cache: always split discards on cache block boundaries\n\ncommit f1daa838e861ae1a0fb7cd9721a21258430fcc8c upstream.\n\nThe DM cache target cannot cope with discards that span multiple cache\nblocks, so each discard bio that spans more than one cache block must\nget split by the DM core.\n\nSigned-off-by: Heinz Mauelshagen <heinzm@redhat.com>\nAcked-by: Joe Thornber <ejt@redhat.com>\nSigned-off-by: Mike Snitzer <snitzer@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Heinz Mauelshagen",true],["24d52daafcd53f109893ec2faf668c8eeef4a382","4c9eb49378914b743bdd32292c04df29b820d73e@cn.fujitsu.com","sched: Fix hotplug vs. set_cpus_allowed_ptr()\n\ncommit 6acbfb96976fc3350e30d964acb1dbbdf876d55e upstream.\n\nLai found that:\n\n  WARNING: CPU: 1 PID: 13 at arch/x86/kernel/smp.c:124 native_smp_send_reschedule+0x2d/0x4b()\n  ...\n  migration_cpu_stop+0x1d/0x22\n\nwas caused by set_cpus_allowed_ptr() assuming that cpu_active_mask is\nalways a sub-set of cpu_online_mask.\n\nThis isn't true since 5fbd036b552f (\"sched: Cleanup cpu_active madness\").\n\nSo set active and online at the same time to avoid this particular\nproblem.\n\nFixes: 5fbd036b552f (\"sched: Cleanup cpu_active madness\")\nSigned-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nCc: Andrew Morton <akpm@linux-foundation.org>\nCc: Gautham R. Shenoy <ego@linux.vnet.ibm.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Michael wang <wangyun@linux.vnet.ibm.com>\nCc: Paul Gortmaker <paul.gortmaker@windriver.com>\nCc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nCc: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\nCc: Toshi Kani <toshi.kani@hp.com>\nLink: http://lkml.kernel.org/r/53758B12.8060609@cn.fujitsu.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Lai Jiangshan",true],["fe01110735379c9b04f25b356f1a1589ecb9227d","711c73f64afdce07b7e38039a96d2224209e9a6c@chris-wilson.co.uk","drm/i915: Only copy back the modified fields to userspace from execbuffer\n\ncommit 9aab8bff7aa3bee567213ad3c1fdfb217bb980a2 upstream.\n\nWe only want to modifiy a single field in the userspace view of the\nexecbuffer command buffer, so explicitly change that rather than copy\neverything back again.\n\nThis serves two purposes:\n\n1. The single fields are much cheaper to copy (constant size so the\ncopy uses special case code) and much smaller than the whole array.\n\n2. We modify the array for internal use that need to be masked from\nthe user.\n\nNote: We need this backported since without it the next bugfix will\nblow up when userspace recycles batchbuffers and relocations.\n\nSigned-off-by: Chris Wilson <chris@chris-wilson.co.uk>\nCc: Daniel Vetter <daniel.vetter@ffwll.ch>\nSigned-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Chris Wilson",true]],"size":42,"ref":"refs/heads/linux-3.10.x-grsecurity-2.9.1","head":"5c1bfd759369cce6747ea6c374ef3e983deac918"}