{"push_id":1299538245,"size":132,"distinct_size":20,"ref":"refs/heads/master-ddbridge-features","head":"93fa394be4809414b8cc01537c527770fafaf745","before":"fa0a3fa50d05cf6529181d9309682efb2f43ee3c","commits":[{"sha":"7e196aa1a011da35a04cb1f161e186563aa8d8db","author":{"name":"Wei Yongjun","email":"07c9053292b1ab0fc7bfece763550eb7eb3e7a18@trendmicro.com.cn"},"message":"clk: sunxi: pll2: Fix return value check in sun4i_pll2_setup()\n\nIn case of error, the functions clk_register_composite() and\nclk_register_divider() returns ERR_PTR() and never returns NULL.\nThe NULL test in the return value check should be replaced with\nIS_ERR().\n\nSigned-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>\nSigned-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/7e196aa1a011da35a04cb1f161e186563aa8d8db"},{"sha":"fbe359f12ce40e3126bea959b135656e4a305897","author":{"name":"Wei Yongjun","email":"07c9053292b1ab0fc7bfece763550eb7eb3e7a18@trendmicro.com.cn"},"message":"clk: sunxi: Fix return value check in sun8i_a23_mbus_setup()\n\nIn case of error, the function of_io_request_and_map() returns ERR_PTR()\nand never returns NULL. The NULL test in the return value check should be\nreplaced with IS_ERR().\n\nSigned-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>\nSigned-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/fbe359f12ce40e3126bea959b135656e4a305897"},{"sha":"156ad0d7eae4825a0d94a4bf68571e97302f2501","author":{"name":"Chen-Yu Tsai","email":"d935d34b7d281e4f50030b838a1bf5c8f10bdb43@csie.org"},"message":"clk: sunxi-ng: Fix inverted test condition in ccu_helper_wait_for_lock\n\nThe condition passed to read*_poll_timeout() is the break condition,\ni.e. wait for this condition to happen and return success.\n\nThe original code assumed the opposite, resulting in a warning when\nthe PLL clock rate was changed but never lost it's lock as far as\nthe readout indicated. This was verified by checking the read out\nregister value.\n\nFixes: 1d80c14248d6 (\"clk: sunxi-ng: Add common infrastructure\")\nSigned-off-by: Chen-Yu Tsai <wens@csie.org>\nAcked-by: Maxime Ripard <maxime.ripard@free-electrons.com>\nSigned-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/156ad0d7eae4825a0d94a4bf68571e97302f2501"},{"sha":"06421a7821f9040467e0db2702309b72aa2b7af4","author":{"name":"Chen-Yu Tsai","email":"d935d34b7d281e4f50030b838a1bf5c8f10bdb43@csie.org"},"message":"clk: sunxi-ng: nk: Make ccu_nk_find_best static\n\nmake C=2 reports:\n\n  CHECK   drivers/clk/sunxi-ng/ccu_nk.c\ndrivers/clk/sunxi-ng/ccu_nk.c:17:6: warning: symbol 'ccu_nk_find_best' was\nnot declared. Should it be static?\n\nccu_nk_find_best is only used within ccu_nk.c. So make it static to get\nrid of this warning.\n\nFixes: adbfb0056e03 (\"clk: sunxi-ng: Add N-K-factor clock support\")\nSigned-off-by: Chen-Yu Tsai <wens@csie.org>\nSigned-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/06421a7821f9040467e0db2702309b72aa2b7af4"},{"sha":"a7d4b8f2565ad0dfdff9a222d1d87990c73b36e8","author":{"name":"David Hildenbrand","email":"4cfe9eda3d73e933d1621922c181632f0257f5a6@linux.vnet.ibm.com"},"message":"KVM: s390: don't use current->thread.fpu.* when accessing registers\n\nAs the meaning of these variables and pointers seems to change more\nfrequently, let's directly access our save area, instead of going via\ncurrent->thread.\n\nRight now, this is broken for set/get_fpu. They simply overwrite the\nhost registers, as the pointers to the current save area were turned\ninto the static host save area.\n\nCc: stable@vger.kernel.org # 4.7\nFixes: 3f6813b9a5e0 (\"s390/fpu: allocate 'struct fpu' with the task_struct\")\nReported-by: Hao QingFeng <haoqf@linux.vnet.ibm.com>\nSigned-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>\nSigned-off-by: Christian Borntraeger <borntraeger@de.ibm.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/a7d4b8f2565ad0dfdff9a222d1d87990c73b36e8"},{"sha":"6654674cb7b5953ac04fc9d7f5f511676ae97e29","author":{"name":"Jorik Jonker","email":"e310cc0bd881ed0adc9949ccb6d16469ae903edc@kippendief.biz"},"message":"clk: sunxi-ng: Fix wrong reset register offsets\n\nThe reset register offsets for UART*, I2C* and SCR were off by a few bytes.\n\nSigned-off-by: Jorik Jonker <jorik@kippendief.biz>\nSigned-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/6654674cb7b5953ac04fc9d7f5f511676ae97e29"},{"sha":"20b8f9e2dde171c69da4a79c34fccdc2a8492797","author":{"name":"Paolo Bonzini","email":"7438500e0207b21c4e5dfca8d2a7898734cd7706@redhat.com"},"message":"Merge tag 'kvm-s390-master-4.8-2' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into kvm-master\n\nKVM: s390: Fix for fpu register errors since 4.7\n\nThis fixes a regression that was introduced by a semantic\nchange in commit 3f6813b9a5e0 (\"s390/fpu: allocate 'struct\nfpu' with the task_struct\"). Symptoms are broken host userspace\nfpu registers if the old FPU set/get ioctls are used.","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/20b8f9e2dde171c69da4a79c34fccdc2a8492797"},{"sha":"8e018c21da3febb558586b48c8db0d6d66cb6593","author":{"name":"Shaohua Li","email":"78841d68de820ce65a8f2019d48ffc5e6c8a1f78@fb.com"},"message":"raid5-cache: fix a deadlock in superblock write\n\nThere is a potential deadlock in superblock write. Discard could zero data, so\nbefore discard we must make sure superblock is updated to new log tail.\nUpdating superblock (either directly call md_update_sb() or depend on md\nthread) must hold reconfig mutex. On the other hand, raid5_quiesce is called\nwith reconfig_mutex hold. The first step of raid5_quiesce() is waitting for all\nIO finish, hence waitting for reclaim thread, while reclaim thread is calling\nthis function and waitting for reconfig mutex. So there is a deadlock. We\nworkaround this issue with a trylock. The downside of the solution is we could\nmiss discard if we can't take reconfig mutex. But this should happen rarely\n(mainly in raid array stop), so miss discard shouldn't be a big problem.\n\nCc: NeilBrown <neilb@suse.com>\nSigned-off-by: Shaohua Li <shli@fb.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/8e018c21da3febb558586b48c8db0d6d66cb6593"},{"sha":"ad5b0f7685dbfc4730987cd16af3c5ebe8133f10","author":{"name":"Shaohua Li","email":"78841d68de820ce65a8f2019d48ffc5e6c8a1f78@fb.com"},"message":"raid5: guarantee enough stripes to avoid reshape hang\n\nIf there aren't enough stripes, reshape will hang. We have a check for\nthis in new reshape, but miss it for reshape resume, hence we could see\nhang in reshape resume. This patch forces enough stripes existed if\nreshape resumes.\n\nReviewed-by: NeilBrown <neilb@suse.com>\nSigned-off-by: Shaohua Li <shli@fb.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/ad5b0f7685dbfc4730987cd16af3c5ebe8133f10"},{"sha":"6af7e4f77259ee946103387372cb159f2e99a6d4","author":{"name":"Bjorn Helgaas","email":"d58560f8a8eaa2bf0a57092b2469a9a49461ac56@google.com"},"message":"PCI: Mark Haswell Power Control Unit as having non-compliant BARs\n\nThe Haswell Power Control Unit has a non-PCI register (CONFIG_TDP_NOMINAL)\nwhere BAR 0 is supposed to be.  This is erratum HSE43 in the spec update\nreferenced below:\n\n  The PCIe* Base Specification indicates that Configuration Space Headers\n  have a base address register at offset 0x10.  Due to this erratum, the\n  Power Control Unit's CONFIG_TDP_NOMINAL CSR (Bus 1; Device 30; Function\n  3; Offset 0x10) is located where a base register is expected.\n\nMark the PCU as having non-compliant BARs so we don't try to probe any of\nthem.  There are no other BARs on this device.\n\nRename the quirk so it's not Broadwell-specific.\n\nLink: http://www.intel.com/content/www/us/en/processors/xeon/xeon-e5-v3-spec-update.html\nLink: http://www.intel.com/content/www/us/en/processors/xeon/xeon-e5-v3-datasheet-vol-2.html (section 5.4, Device 30 Function 3)\nLink: https://bugzilla.kernel.org/show_bug.cgi?id=153881\nReported-by: Paul Menzel <pmenzel@molgen.mpg.de>\nTested-by: Prarit Bhargava <prarit@redhat.com>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nAcked-by: Myron Stowe <myron.stowe@redhat.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/6af7e4f77259ee946103387372cb159f2e99a6d4"},{"sha":"a41bd25ae67d3e4052c7f00ee9f2b4ba9219309e","author":{"name":"Paolo Abeni","email":"760d0d6fcadb77e1b4c1d3c7879788c2b4ed8bbe@redhat.com"},"message":"sunrpc: fix UDP memory accounting\n\nThe commit f9b2ee714c5c (\"SUNRPC: Move UDP receive data path\ninto a workqueue context\"), as a side effect, moved the\nskb_free_datagram() call outside the scope of the related socket\nlock, but UDP sockets require such lock to be held for proper\nmemory accounting.\nFix it by replacing skb_free_datagram() with\nskb_free_datagram_locked().\n\nFixes: f9b2ee714c5c (\"SUNRPC: Move UDP receive data path into a workqueue context\")\nReported-and-tested-by: Jan Stancek <jstancek@redhat.com>\nSigned-off-by: Paolo Abeni <pabeni@redhat.com>\nCc: stable@vger.kernel.org # 4.4+\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/a41bd25ae67d3e4052c7f00ee9f2b4ba9219309e"},{"sha":"c49edecd513693ea7530ab18efbd7d6d5b7cbf90","author":{"name":"Trond Myklebust","email":"74f7b75b0dfb06f182c703b16f16eeff3727673a@primarydata.com"},"message":"NFS: Fix error reporting in nfs_file_write()\n\nWhen doing O_DSYNC writes, the actual write errors are reported through\ngeneric_write_sync(), so we must test the result.\n\nReported-by: J. R. Okajima <hooanon05g@gmail.com>\nFixes: 18290650b1c8 (\"NFS: Move buffered I/O locking into nfs_file_write()\")\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/c49edecd513693ea7530ab18efbd7d6d5b7cbf90"},{"sha":"bf0291dd2267a2b9a4cd74d65249553d11bb45d6","author":{"name":"Trond Myklebust","email":"74f7b75b0dfb06f182c703b16f16eeff3727673a@primarydata.com"},"message":"pNFS: Ensure LAYOUTGET and LAYOUTRETURN are properly serialised\n\nAccording to RFC5661, the client is responsible for serialising\nLAYOUTGET and LAYOUTRETURN to avoid ambiguity. Consider the case\nwhere we send both in parallel.\n\nClient\t\t\t\t\tServer\n======\t\t\t\t\t======\nLAYOUTGET(seqid=X)\nLAYOUTRETURN(seqid=X)\n\t\t\t\t\tLAYOUTGET return seqid=X+1\n\t\t\t\t\tLAYOUTRETURN return seqid=X+2\nProcess LAYOUTRETURN\n          Forget layout stateid\nProcess LAYOUTGET\n          Set seqid=X+1\n\nThe client processes the layoutget/layoutreturn in the wrong order,\nand since the result of the layoutreturn was to clear the only\nexisting layout segment, the client forgets the layout stateid.\n\nWhen the LAYOUTGET comes in, it is treated as having a completely\nnew stateid, and so the client sets the wrong sequence id...\n\nFix is to check if there are outstanding LAYOUTGET requests\nbefore we send the LAYOUTRETURN (note that LAYOUGET will already\nwait if it sees an outstanding LAYOUTRETURN).\n\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>\nCc: stable@vger.kernel.org # v4.5+\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/bf0291dd2267a2b9a4cd74d65249553d11bb45d6"},{"sha":"2a59a0411671ef9daf17ba21da57809c696f4119","author":{"name":"Trond Myklebust","email":"74f7b75b0dfb06f182c703b16f16eeff3727673a@primarydata.com"},"message":"pNFS: Fix pnfs_set_layout_stateid() to clear NFS_LAYOUT_INVALID_STID\n\nIf the layout was marked as invalid, we want to ensure to initialise\nthe layout header fields correctly.\n\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/2a59a0411671ef9daf17ba21da57809c696f4119"},{"sha":"52ec7be2e27392201adf77892ba883f68df88c99","author":{"name":"Trond Myklebust","email":"74f7b75b0dfb06f182c703b16f16eeff3727673a@primarydata.com"},"message":"pNFS: Clear out all layout segments if the server unsets lrp->res.lrs_present\n\nIf the server fails to set lrp->res.lrs_present in the LAYOUTRETURN reply,\nthen that means it believes the client holds no more layout state for that\nfile, and that the layout stateid is now invalid.\n\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/52ec7be2e27392201adf77892ba883f68df88c99"},{"sha":"334a8f37115bf35e38617315a360a91ac4f2b2c6","author":{"name":"Trond Myklebust","email":"74f7b75b0dfb06f182c703b16f16eeff3727673a@primarydata.com"},"message":"pNFS: Don't forget the layout stateid if there are outstanding LAYOUTGETs\n\nIf there are outstanding LAYOUTGET rpc calls, then we want to ensure that\nwe keep the layout stateid around so we that don't inadvertently pick up\nan old/misordered sequence id.\nThe race is as follows:\n\nClient\t\t\t\tServer\n======\t\t\t\t======\nLAYOUTGET(seqid)\nLAYOUTGET(seqid)\n\t\t\t\treturn LAYOUTGET(seqid+1)\n\t\t\t\treturn LAYOUTGET(seqid+2)\nprocess LAYOUTGET(seqid+2)\n\tforget layout\nprocess LAYOUTGET(seqid+1)\n\nIf it forgets the layout stateid before processing seqid+1, then\nthe client will not check the layout->plh_barrier, and so will set\nthe stateid with seqid+1.\n\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/334a8f37115bf35e38617315a360a91ac4f2b2c6"},{"sha":"cc2187a6e037bc64404f63c6d650ff263c2200c0","author":{"name":"Borislav Petkov","email":"eb590213a9667d8ba86dc1d7da45a37c724b7836@alien8.de"},"message":"x86/microcode/AMD: Fix load of builtin microcode with randomized memory\n\nWe do not need to add the randomization offset when the microcode is\nbuilt in.\n\nReported-and-tested-by: Emanuel Czirai <icanrealizeum@gmail.com>\nSigned-off-by: Borislav Petkov <bp@suse.de>\nLink: http://lkml.kernel.org/r/20160904093736.GA11939@pd.tnic\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/cc2187a6e037bc64404f63c6d650ff263c2200c0"},{"sha":"d7127b5e5fa0551be21b86640f1648b224e36d43","author":{"name":"Johannes Berg","email":"9a5936d824e6835dfe162c5611d10d2cf40ffbad@intel.com"},"message":"locking/barriers: Don't use sizeof(void) in lockless_dereference()\n\nMy previous commit:\n\n  112dc0c8069e (\"locking/barriers: Suppress sparse warnings in lockless_dereference()\")\n\ncaused sparse to complain that (in radix-tree.h) we use sizeof(void)\nsince that rcu_dereference()s a void *.\n\nReally, all we need is to have the expression *p in here somewhere\nto make sure p is a pointer type, and sizeof(*p) was the thing that\ncame to my mind first to make sure that's done without really doing\nanything at runtime.\n\nAnother thing I had considered was using typeof(*p), but obviously\nwe can't just declare a typeof(*p) variable either, since that may\nend up being void. Declaring a variable as typeof(*p)* gets around\nthat, and still checks that typeof(*p) is valid, so do that. This\ntype construction can't be done for _________p1 because that will\nactually be used and causes sparse address space warnings, so keep\na separate unused variable for it.\n\nReported-by: Fengguang Wu <fengguang.wu@intel.com>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Paul E . McKenney <paulmck@linux.vnet.ibm.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: kbuild-all@01.org\nFixes: 112dc0c8069e (\"locking/barriers: Suppress sparse warnings in lockless_dereference()\")\nLink: http://lkml.kernel.org/r/1472192160-4049-1-git-send-email-johannes@sipsolutions.net\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/d7127b5e5fa0551be21b86640f1648b224e36d43"},{"sha":"58763148758057ffc447bf990321d3ea86d199a0","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"perf/core: Remove WARN from perf_event_read()\n\nThis effectively reverts commit:\n\n  71e7bc2bab77 (\"perf/core: Check return value of the perf_event_read() IPI\")\n\n... and puts in a comment explaining why we ignore the return value.\n\nReported-by: Vegard Nossum <vegard.nossum@gmail.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: David Carrillo-Cisneros <davidcc@google.com>\nCc: Jiri Olsa <jolsa@redhat.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nFixes: 71e7bc2bab77 (\"perf/core: Check return value of the perf_event_read() IPI\")\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/58763148758057ffc447bf990321d3ea86d199a0"},{"sha":"135e8c9250dd5c8c9aae5984fde6f230d0cbfeaf","author":{"name":"Balbir Singh","email":"daca7b412031fb0e95d58c31aac905f736b2d1c1@gmail.com"},"message":"sched/core: Fix a race between try_to_wake_up() and a woken up task\n\nThe origin of the issue I've seen is related to\na missing memory barrier between check for task->state and\nthe check for task->on_rq.\n\nThe task being woken up is already awake from a schedule()\nand is doing the following:\n\n\tdo {\n\t\tschedule()\n\t\tset_current_state(TASK_(UN)INTERRUPTIBLE);\n\t} while (!cond);\n\nThe waker, actually gets stuck doing the following in\ntry_to_wake_up():\n\n\twhile (p->on_cpu)\n\t\tcpu_relax();\n\nAnalysis:\n\nThe instance I've seen involves the following race:\n\n CPU1\t\t\t\t\tCPU2\n\n while () {\n   if (cond)\n     break;\n   do {\n     schedule();\n     set_current_state(TASK_UN..)\n   } while (!cond);\n\t\t\t\t\twakeup_routine()\n\t\t\t\t\t  spin_lock_irqsave(wait_lock)\n   raw_spin_lock_irqsave(wait_lock)\t  wake_up_process()\n }\t\t\t\t\t  try_to_wake_up()\n set_current_state(TASK_RUNNING);\t  ..\n list_del(&waiter.list);\n\nCPU2 wakes up CPU1, but before it can get the wait_lock and set\ncurrent state to TASK_RUNNING the following occurs:\n\n CPU3\n wakeup_routine()\n raw_spin_lock_irqsave(wait_lock)\n if (!list_empty)\n   wake_up_process()\n   try_to_wake_up()\n   raw_spin_lock_irqsave(p->pi_lock)\n   ..\n   if (p->on_rq && ttwu_wakeup())\n   ..\n   while (p->on_cpu)\n     cpu_relax()\n   ..\n\nCPU3 tries to wake up the task on CPU1 again since it finds\nit on the wait_queue, CPU1 is spinning on wait_lock, but immediately\nafter CPU2, CPU3 got it.\n\nCPU3 checks the state of p on CPU1, it is TASK_UNINTERRUPTIBLE and\nthe task is spinning on the wait_lock. Interestingly since p->on_rq\nis checked under pi_lock, I've noticed that try_to_wake_up() finds\np->on_rq to be 0. This was the most confusing bit of the analysis,\nbut p->on_rq is changed under runqueue lock, rq_lock, the p->on_rq\ncheck is not reliable without this fix IMHO. The race is visible\n(based on the analysis) only when ttwu_queue() does a remote wakeup\nvia ttwu_queue_remote. In which case the p->on_rq change is not\ndone uder the pi_lock.\n\nThe result is that after a while the entire system locks up on\nthe raw_spin_irqlock_save(wait_lock) and the holder spins infintely\n\nReproduction of the issue:\n\nThe issue can be reproduced after a long run on my system with 80\nthreads and having to tweak available memory to very low and running\nmemory stress-ng mmapfork test. It usually takes a long time to\nreproduce. I am trying to work on a test case that can reproduce\nthe issue faster, but thats work in progress. I am still testing the\nchanges on my still in a loop and the tests seem OK thus far.\n\nBig thanks to Benjamin and Nick for helping debug this as well.\nBen helped catch the missing barrier, Nick caught every missing\nbit in my theory.\n\nSigned-off-by: Balbir Singh <bsingharora@gmail.com>\n[ Updated comment to clarify matching barriers. Many\n  architectures do not have a full barrier in switch_to()\n  so that cannot be relied upon. ]\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nAcked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nCc: Alexey Kardashevskiy <aik@ozlabs.ru>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Nicholas Piggin <nicholas.piggin@gmail.com>\nCc: Nicholas Piggin <npiggin@gmail.com>\nCc: Oleg Nesterov <oleg@redhat.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: <stable@vger.kernel.org>\nLink: http://lkml.kernel.org/r/e02cce7b-d9ca-1ad0-7a61-ea97c7582b37@gmail.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":false,"url":"https://api.github.com/repos/herrnst/dddvb-linux-kernel/commits/135e8c9250dd5c8c9aae5984fde6f230d0cbfeaf"}]}
{"actor":{"display_login":"herrnst"}}