{"push_id":860427637,"size":56,"distinct_size":56,"ref":"refs/heads/test","head":"97e74dd5a6ada9658fa9c13b02f230173725db83","before":"6a7f3d27f942c8f5d124fcc3646666e9062d886f","commits":[{"sha":"1759ff07d09c6fd3f272c657f6ac7b3158ea5bb0","author":{"email":"03189597947f75187c4136ade35aec34feed9dc1@redhat.com","name":"Gleb Natapov"},"message":"KVM: VMX: fix halt emulation while emulating invalid guest sate\n\ncommit 8d76c49e9ffeee839bc0b7a3278a23f99101263e upstream.\n\nThe invalid guest state emulation loop does not check halt_request\nwhich causes 100% cpu loop while guest is in halt and in invalid\nstate, but more serious issue is that this leaves halt_request set, so\nrandom instruction emulated by vm86 #GP exit can be interpreted\nas halt which causes guest hang. Fix both problems by handling\nhalt_request in emulation loop.\n\nReported-by: Tomas Papan <tomas.papan@gmail.com>\nTested-by: Tomas Papan <tomas.papan@gmail.com>\nReviewed-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Gleb Natapov <gleb@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/1759ff07d09c6fd3f272c657f6ac7b3158ea5bb0"},{"sha":"5d7b565bc980230bb83dced89aef025f55bd3180","author":{"email":"13423a3f3006b5859cfceae66d59451f5eb4e205@iki.fi","name":"Aaro Koskinen"},"message":"ARM: OMAP: RX-51: change probe order of touchscreen and panel SPI devices\n\ncommit e65f131a14726e5f1b880a528271a52428e5b3a5 upstream.\n\nCommit 9fdca9df (spi: omap2-mcspi: convert to module_platform_driver)\nbroke the SPI display/panel driver probe on RX-51/N900. The exact cause is\nnot fully understood, but it seems to be related to the probe order. SPI\ncommunication to the panel driver (spi1.2) fails unless the touchscreen\n(spi1.0) has been probed/initialized before. When the omap2-mcspi driver\nwas converted to a platform driver, it resulted in that the devices are\nprobed immediately after the board registers them in the order they are\nlisted in the board file.\n\nFix the issue by moving the touchscreen before the panel in the SPI\ndevice list.\n\nThe patch fixes the following failure:\n\n[    1.260955] acx565akm spi1.2: invalid display ID\n[    1.265899] panel-acx565akm display0: acx_panel_probe panel detect error\n[    1.273071] omapdss CORE error: driver probe failed: -19\n\nTested-by: Sebastian Reichel <sre@debian.org>\nSigned-off-by: Aaro Koskinen <aaro.koskinen@iki.fi>\nCc: Pali Rohár <pali.rohar@gmail.com>\nCc: Joni Lapilainen <joni.lapilainen@gmail.com>\nCc: Tomi Valkeinen <tomi.valkeinen@ti.com>\nCc: Felipe Balbi <balbi@ti.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/5d7b565bc980230bb83dced89aef025f55bd3180"},{"sha":"64aae725a393c366a037b7f9ea2832b816aec6f1","author":{"email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com","name":"Dan Carpenter"},"message":"ASoC: wm8994: missing break in wm8994_aif3_hw_params()\n\ncommit 4495e46fe18f198366961bb2b324a694ef8a9b44 upstream.\n\nThe missing break here means that we always return early and the\nfunction is a no-op.\n\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/64aae725a393c366a037b7f9ea2832b816aec6f1"},{"sha":"e2481e470b1724081d4602539e7272a77ad67fd7","author":{"email":"861d61e839a6c9cacf88c3a26b10371d2c9b211f@intel.com","name":"Bob Moore"},"message":"ACPICA: Fix possible buffer overflow during a field unit read operation\n\ncommit 61388f9e5d93053cf399a356414f31f9b4814c6d upstream.\n\nCan only happen under these conditions: 1) The DSDT version is 1,\nmeaning integers are 32-bits.  2) The field is between 33 and 64\nbits long.\n\nIt applies cleanly back to ACPICA 20100806+ (Linux v2.6.37+).\n\nSigned-off-by: Bob Moore <robert.moore@intel.com>\nSigned-off-by: Lv Zheng <lv.zheng@intel.com>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/e2481e470b1724081d4602539e7272a77ad67fd7"},{"sha":"9948d32546ccfb356fa0bb71e043dce0703454f8","author":{"email":"56ca982e301c39f713d7dc27488130819812afde@gmail.com","name":"Wang YanQing"},"message":"ALSA: HDA: Fix Oops caused by dereference NULL pointer\n\ncommit 2195b063f6609e4c6268f291683902f25eaf9aa6 upstream.\n\nThe interrupt handler azx_interrupt will call azx_update_rirb,\nwhich may call snd_hda_queue_unsol_event, snd_hda_queue_unsol_event\nwill dereference chip->bus pointer.\n\nThe problem is we alloc chip->bus in azx_codec_create\nwhich will be called after we enable IRQ and enable unsolicited\nevent in azx_probe.\n\nThis will cause Oops due dereference NULL pointer. I meet it, good luck:)\n\n[Rearranged the NULL check before the tracepoint and added another\n NULL check of bus->workq -- tiwai]\n\nSigned-off-by: Wang YanQing <udknight@gmail.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/9948d32546ccfb356fa0bb71e043dce0703454f8"},{"sha":"81beff88bb7f2a1dd79c5371d23a2e03b6cdbcf4","author":{"email":"b8f9cab8be13de37b9588aedad10a20fc3a68783@trendmicro.com.cn","name":"Wei Yongjun"},"message":"dm snapshot: fix error return code in snapshot_ctr\n\ncommit 09e8b813897a0f85bb401435d009228644c81214 upstream.\n\nReturn -ENOMEM instead of success if unable to allocate pending\nexception mempool in snapshot_ctr.\n\nSigned-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>\nSigned-off-by: Alasdair G Kergon <agk@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/81beff88bb7f2a1dd79c5371d23a2e03b6cdbcf4"},{"sha":"ba9f148e987dcb8cfa57b4d83a8476db861acbae","author":{"email":"51738506c1b2ccb0761f23bdc612c93babf738ea@redhat.com","name":"J. Bruce Fields"},"message":"nfsd4: don't allow owner override on 4.1 CLAIM_FH opens\n\ncommit 9f415eb25574db4b73a9a712a4438e41dc284922 upstream.\n\nThe Linux client is using CLAIM_FH to implement regular opens, not just\nrecovery cases, so it depends on the server to check permissions\ncorrectly.\n\nTherefore the owner override, which may make sense in the delegation\nrecovery case, isn't right in the CLAIM_FH case.\n\nSymptoms: on a client with 49f9a0fafd844c32f2abada047c0b9a5ba0d6255\n\"NFSv4.1: Enable open-by-filehandle\", Bryan noticed this:\n\n\ttouch test.txt\n\tchmod 000 test.txt\n\techo test > test.txt\n\nsucceeding.\n\nReported-by: Bryan Schumaker <bjschuma@netapp.com>\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/ba9f148e987dcb8cfa57b4d83a8476db861acbae"},{"sha":"0b454c805cc1d19d8b09adb70e0e24aad1f1ee3e","author":{"email":"f9cffb48774c5c540daacd974d14454046841468@hp.com","name":"Shuah Khan"},"message":"hp_accel: Ignore the error from lis3lv02d_poweron() at resume\n\ncommit 7783819920ca52fc582a2782f654fe6ed373f465 upstream.\n\nThe error in lis3lv02_poweron() is harmless in the resume path, so\nwe should ignore it. It is inline with the other usages of lis3lv02_poweron()\nand matches the 3.0 code for this routine. This patch is in suse git and\nmight have missed making it into the mainline.\nopensuse - commit id: 66ccdac87c322cf7af12bddba8c805af640b1cff\n\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Shuah Khan <shuah.khan@hp.com>\nSigned-off-by: Matthew Garrett <matthew.garrett@nebula.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/0b454c805cc1d19d8b09adb70e0e24aad1f1ee3e"},{"sha":"e5b051fb01ce6cf60c3ea47246a3d82ade02842b","author":{"email":"da3a51b335cef0eb0e2c329c5ef6bcd6acef687a@oracle.com","name":"Konrad Rzeszutek Wilk"},"message":"xen/vcpu/pvhvm: Fix vcpu hotplugging hanging.\n\ncommit 7f1fc268c47491fd5e63548f6415fc8604e13003 upstream.\n\nIf a user did:\n\n\techo 0 > /sys/devices/system/cpu/cpu1/online\n\techo 1 > /sys/devices/system/cpu/cpu1/online\n\nwe would (this a build with DEBUG enabled) get to:\nsmpboot: ++++++++++++++++++++=_---CPU UP  1\n.. snip..\nsmpboot: Stack at about ffff880074c0ff44\nsmpboot: CPU1: has booted.\n\nand hang. The RCU mechanism would kick in an try to IPI the CPU1\nbut the IPIs (and all other interrupts) would never arrive at the\nCPU1. At first glance at least. A bit digging in the hypervisor\ntrace shows that (using xenanalyze):\n\n[vla] d4v1 vec 243 injecting\n   0.043163027 --|x d4v1 intr_window vec 243 src 5(vector) intr f3\n]  0.043163639 --|x d4v1 vmentry cycles 1468\n]  0.043164913 --|x d4v1 vmexit exit_reason PENDING_INTERRUPT eip ffffffff81673254\n   0.043164913 --|x d4v1 inj_virq vec 243  real\n  [vla] d4v1 vec 243 injecting\n   0.043164913 --|x d4v1 intr_window vec 243 src 5(vector) intr f3\n]  0.043165526 --|x d4v1 vmentry cycles 1472\n]  0.043166800 --|x d4v1 vmexit exit_reason PENDING_INTERRUPT eip ffffffff81673254\n   0.043166800 --|x d4v1 inj_virq vec 243  real\n  [vla] d4v1 vec 243 injecting\n\nthere is a pending event (subsequent debugging shows it is the IPI\nfrom the VCPU0 when smpboot.c on VCPU1 has done\n\"set_cpu_online(smp_processor_id(), true)\") and the guest VCPU1 is\ninterrupted with the callback IPI (0xf3 aka 243) which ends up calling\n__xen_evtchn_do_upcall.\n\nThe __xen_evtchn_do_upcall seems to do *something* but not acknowledge\nthe pending events. And the moment the guest does a 'cli' (that is the\nffffffff81673254 in the log above) the hypervisor is invoked again to\ninject the IPI (0xf3) to tell the guest it has pending interrupts.\nThis repeats itself forever.\n\nThe culprit was the per_cpu(xen_vcpu, cpu) pointer. At the bootup\nwe set each per_cpu(xen_vcpu, cpu) to point to the\nshared_info->vcpu_info[vcpu] but later on use the VCPUOP_register_vcpu_info\nto register per-CPU  structures (xen_vcpu_setup).\nThis is used to allow events for more than 32 VCPUs and for performance\noptimizations reasons.\n\nWhen the user performs the VCPU hotplug we end up calling the\nthe xen_vcpu_setup once more. We make the hypercall which returns\n-EINVAL as it does not allow multiple registration calls (and\nalready has re-assigned where the events are being set). We pick\nthe fallback case and set per_cpu(xen_vcpu, cpu) to point to the\nshared_info->vcpu_info[vcpu] (which is a good fallback during bootup).\nHowever the hypervisor is still setting events in the register\nper-cpu structure (per_cpu(xen_vcpu_info, cpu)).\n\nAs such when the events are set by the hypervisor (such as timer one),\nand when we iterate in __xen_evtchn_do_upcall we end up reading stale\nevents from the shared_info->vcpu_info[vcpu] instead of the\nper_cpu(xen_vcpu_info, cpu) structures. Hence we never acknowledge the\nevents that the hypervisor has set and the hypervisor keeps on reminding\nus to ack the events which we never do.\n\nThe fix is simple. Don't on the second time when xen_vcpu_setup is\ncalled over-write the per_cpu(xen_vcpu, cpu) if it points to\nper_cpu(xen_vcpu_info).\n\nAcked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>\nSigned-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/e5b051fb01ce6cf60c3ea47246a3d82ade02842b"},{"sha":"75a95d71af1913b55fd035823263c6113882841b","author":{"email":"1acebbdca565c7b6b638bdc23b58b5610d1a56b8@Parallels.com","name":"James Bottomley"},"message":"SCSI: sd: fix array cache flushing bug causing performance problems\n\ncommit 39c60a0948cc06139e2fbfe084f83cb7e7deae3b upstream.\n\nSome arrays synchronize their full non volatile cache when the sd driver sends\na SYNCHRONIZE CACHE command.  Unfortunately, they can have Terrabytes of this\nand we send a SYNCHRONIZE CACHE for every barrier if an array reports it has a\nwriteback cache.  This leads to massive slowdowns on journalled filesystems.\n\nThe fix is to allow userspace to turn off the writeback cache setting as a\ntemporary measure (i.e. without doing the MODE SELECT to write it back to the\ndevice), so even though the device reported it has a writeback cache, the\nuser, knowing that the cache is non volatile and all they care about is\nfilesystem correctness, can turn that bit off in the kernel and avoid the\nperformance ruinous (and safety irrelevant) SYNCHRONIZE CACHE commands.\n\nThe way you do this is add a 'temporary' prefix when performing the usual\ncache setting operations, so\n\necho temporary write through > /sys/class/scsi_disk/<disk>/cache_type\n\nReported-by: Ric Wheeler <rwheeler@redhat.com>\nSigned-off-by: James Bottomley <JBottomley@Parallels.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/75a95d71af1913b55fd035823263c6113882841b"},{"sha":"cdca3afc8a80fcbf8a3c02526c2af8835cd11bb6","author":{"email":"14deb5e5e417133e888bf47bb6a3555c9bb7d81c@samba.org","name":"Anton Blanchard"},"message":"audit: Syscall rules are not applied to existing processes on non-x86\n\ncommit cdee3904b4ce7c03d1013ed6dd704b43ae7fc2e9 upstream.\n\nCommit b05d8447e782 (audit: inline audit_syscall_entry to reduce\nburden on archs) changed audit_syscall_entry to check for a dummy\ncontext before calling __audit_syscall_entry. Unfortunately the dummy\ncontext state is maintained in __audit_syscall_entry so once set it\nnever gets cleared, even if the audit rules change.\n\nAs a result, if there are no auditing rules when a process starts\nthen it will never be subject to any rules added later. x86 doesn't\nsee this because it has an assembly fast path that calls directly into\n__audit_syscall_entry.\n\nI noticed this issue when working on audit performance optimisations.\nI wrote a set of simple test cases available at:\n\nhttp://ozlabs.org/~anton/junkcode/audit_tests.tar.gz\n\n02_new_rule.py fails without the patch and passes with it. The\ntest case clears all rules, starts a process, adds a rule then\nverifies the process produces a syscall audit record.\n\nSigned-off-by: Anton Blanchard <anton@samba.org>\nSigned-off-by: Eric Paris <eparis@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/cdca3afc8a80fcbf8a3c02526c2af8835cd11bb6"},{"sha":"76b4e73e35c8b1a197d40940b91e6311927fe94d","author":{"email":"00e4cf8f46a57000a44449bf9dd8cbbcc209fd2a@linutronix.de","name":"Thomas Gleixner"},"message":"tick: Cleanup NOHZ per cpu data on cpu down\n\ncommit 4b0c0f294f60abcdd20994a8341a95c8ac5eeb96 upstream.\n\nPrarit reported a crash on CPU offline/online. The reason is that on\nCPU down the NOHZ related per cpu data of the dead cpu is not cleaned\nup. If at cpu online an interrupt happens before the per cpu tick\ndevice is registered the irq_enter() check potentially sees stale data\nand dereferences a NULL pointer.\n\nCleanup the data after the cpu is dead.\n\nReported-by: Prarit Bhargava <prarit@redhat.com>\nCc: Mike Galbraith <bitbucket@online.de>\nLink: http://lkml.kernel.org/r/alpine.LFD.2.02.1305031451561.2886@ionos\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/76b4e73e35c8b1a197d40940b91e6311927fe94d"},{"sha":"05bd45d026a4dc6311819f342a598170d57d9c24","author":{"email":"43232e92d70cc7aa53504ad0397085ee47bad87f@goodmis.org","name":"Steven Rostedt (Red Hat)"},"message":"tracing: Fix leaks of filter preds\n\ncommit 60705c89460fdc7227f2d153b68b3f34814738a4 upstream.\n\nSpecial preds are created when folding a series of preds that\ncan be done in serial. These are allocated in an ops field of\nthe pred structure. But they were never freed, causing memory\nleaks.\n\nThis was discovered using the kmemleak checker:\n\nunreferenced object 0xffff8800797fd5e0 (size 32):\n  comm \"swapper/0\", pid 1, jiffies 4294690605 (age 104.608s)\n  hex dump (first 32 bytes):\n    00 00 01 00 03 00 05 00 07 00 09 00 0b 00 0d 00  ................\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace:\n    [<ffffffff814b52af>] kmemleak_alloc+0x73/0x98\n    [<ffffffff8111ff84>] kmemleak_alloc_recursive.constprop.42+0x16/0x18\n    [<ffffffff81120e68>] __kmalloc+0xd7/0x125\n    [<ffffffff810d47eb>] kcalloc.constprop.24+0x2d/0x2f\n    [<ffffffff810d4896>] fold_pred_tree_cb+0xa9/0xf4\n    [<ffffffff810d3781>] walk_pred_tree+0x47/0xcc\n    [<ffffffff810d5030>] replace_preds.isra.20+0x6f8/0x72f\n    [<ffffffff810d50b5>] create_filter+0x4e/0x8b\n    [<ffffffff81b1c30d>] ftrace_test_event_filter+0x5a/0x155\n    [<ffffffff8100028d>] do_one_initcall+0xa0/0x137\n    [<ffffffff81afbedf>] kernel_init_freeable+0x14d/0x1dc\n    [<ffffffff814b24b7>] kernel_init+0xe/0xdb\n    [<ffffffff814d539c>] ret_from_fork+0x7c/0xb0\n    [<ffffffffffffffff>] 0xffffffffffffffff\n\nSigned-off-by: Steven Rostedt <rostedt@goodmis.org>\nCc: Tom Zanussi <tzanussi@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/05bd45d026a4dc6311819f342a598170d57d9c24"},{"sha":"787873f1b0c8a1340bf4232421fd4fbf95a862f3","author":{"email":"ff9e869555c1bbba9d4ec165450acb53740323ed@redhat.com","name":"Lachlan McIlroy"},"message":"ext4: limit group search loop for non-extent files\n\ncommit e6155736ad76b2070652745f9e54cdea3f0d8567 upstream.\n\nIn the case where we are allocating for a non-extent file,\nwe must limit the groups we allocate from to those below\n2^32 blocks, and ext4_mb_regular_allocator() attempts to\ndo this initially by putting a cap on ngroups for the\nsubsequent search loop.\n\nHowever, the initial target group comes in from the\nallocation context (ac), and it may already be beyond\nthe artificially limited ngroups.  In this case,\nthe limit\n\n\tif (group == ngroups)\n\t\tgroup = 0;\n\nat the top of the loop is never true, and the loop will\nrun away.\n\nCatch this case inside the loop and reset the search to\nstart at group 0.\n\n[sandeen@redhat.com: add commit msg & comments]\n\nSigned-off-by: Lachlan McIlroy <lmcilroy@redhat.com>\nSigned-off-by: Eric Sandeen <sandeen@redhat.com>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/787873f1b0c8a1340bf4232421fd4fbf95a862f3"},{"sha":"b668f93d8a13467b6062ce5d335a1d000d066d4c","author":{"email":"3915fb8377205924ccc3120e302501c7a259dd7e@linux.vnet.ibm.com","name":"Robert Jennings"},"message":"powerpc: Bring all threads online prior to migration/hibernation\n\ncommit 120496ac2d2d60aee68d3123a68169502a85f4b5 upstream.\n\nThis patch brings online all threads which are present but not online\nprior to migration/hibernation.  After migration/hibernation those\nthreads are taken back offline.\n\nDuring migration/hibernation all online CPUs must call H_JOIN, this is\nrequired by the hypervisor.  Without this patch, threads that are offline\n(H_CEDE'd) will not be woken to make the H_JOIN call and the OS will be\ndeadlocked (all threads either JOIN'd or CEDE'd).\n\nSigned-off-by: Robert Jennings <rcj@linux.vnet.ibm.com>\nSigned-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/b668f93d8a13467b6062ce5d335a1d000d066d4c"},{"sha":"5678382f64a008a2714b34cebdca3a724abfa926","author":{"email":"118ed6118e893d16e8c6e0776e0ebc290952c897@openwrt.org","name":"Felix Fietkau"},"message":"ath9k: fix key allocation error handling for powersave keys\n\ncommit 4ef69d0394cba8caa9f75d3f2e53429bfb8b3045 upstream.\n\nIf no keycache slots are available, ath_key_config can return -ENOSPC.\nIf the key index is not checked for errors, it can lead to logspam that\nlooks like this: \"ath: wiphy0: keyreset: keycache entry 228 out of range\"\nThis can cause follow-up errors if the invalid keycache index gets\nused for tx.\n\nSigned-off-by: Felix Fietkau <nbd@openwrt.org>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/5678382f64a008a2714b34cebdca3a724abfa926"},{"sha":"e1e39aee35b202f09cd4008d6c62a6dc89a5deec","author":{"email":"abbaae6378dda6b8d65fe6bd0f8beb334a5e4c4f@marvell.com","name":"Bing Zhao"},"message":"mwifiex: clear is_suspended flag when interrupt is received early\n\ncommit 48795424acff7215d5eac0b52793a2c1eb3a6283 upstream.\n\nWhen the XO-4 with 8787 wireless is woken up due to wake-on-WLAN\nmwifiex is often flooded with \"not allowed while suspended\" messages\nand the interface is unusable.\n\n[  202.171609] int: sdio_ireg = 0x1\n[  202.180700] info: mwifiex_process_hs_config: auto cancelling host\n               sleep since there is interrupt from the firmware\n[  202.201880] event: wakeup device...\n[  202.211452] event: hs_deactivated\n[  202.514638] info: --- Rx: Data packet ---\n[  202.514753] data: 4294957544 BSS(0-0): Data <= kernel\n[  202.514825] PREP_CMD: device in suspended state\n[  202.514839] data: dequeuing the packet ec7248c0 ec4869c0\n[  202.514886] mwifiex_write_data_sync: not allowed while suspended\n[  202.514886] host_to_card, write iomem (1) failed: -1\n[  202.514917] mwifiex_write_data_sync: not allowed while suspended\n[  202.514936] host_to_card, write iomem (2) failed: -1\n[  202.514949] mwifiex_write_data_sync: not allowed while suspended\n[  202.514965] host_to_card, write iomem (3) failed: -1\n[  202.514976] mwifiex_write_data_async failed: 0xFFFFFFFF\n\nThis can be readily reproduced when putting the XO-4 in a loop where\nit goes to sleep due to inactivity, but then wakes up due to an\nincoming ping. The error is hit within an hour or two.\n\nThis issue happens when an interrupt comes in early while host sleep\nis still activated. Driver handles this case by auto cancelling host\nsleep. However is_suspended flag is still set which prevents any cmd\nor data from being sent to firmware. Fix it by clearing is_suspended\nflag in this path.\n\nReported-by: Daniel Drake <dsd@laptop.org>\nTested-by: Daniel Drake <dsd@laptop.org>\nSigned-off-by: Bing Zhao <bzhao@marvell.com>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/e1e39aee35b202f09cd4008d6c62a6dc89a5deec"},{"sha":"5945bf5ebb62e2928626a3518cedb7efc91347cf","author":{"email":"83b0c3d63e8a11eb6e40077030b59e95bfe31ffa@laptop.org","name":"Daniel Drake"},"message":"mwifiex: fix setting of multicast filter\n\ncommit ccd384b10420ac81ba3fb9b0a7d18272c7173552 upstream.\n\nA small bug in this code was causing the ALLMULTI filter to be set\nwhen in fact we were just wanting to program a selective multicast list\nto the hardware.\n\nFix that bug and remove a redundant if condition in the code that\nfollows.\n\nThis fixes wakeup behaviour when multicast WOL is enabled. Previously,\nall multicast packets would wake up the system. Now, only those that the\nhost intended to receive trigger wakeups.\n\nSigned-off-by: Daniel Drake <dsd@laptop.org>\nAcked-by: Bing Zhao <bzhao@marvell.com>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/5945bf5ebb62e2928626a3518cedb7efc91347cf"},{"sha":"3f28610e6571188e07c2dea303c837e99f9e3f09","author":{"email":"22f02d77e3d63643bb259e2f6ed89ea953cbe348@gmail.com","name":"Thommy Jakobsson"},"message":"B43: Handle DMA RX descriptor underrun\n\ncommit 73b82bf0bfbf58e6ff328d3726934370585f6e78 upstream.\n\nAdd handling of rx descriptor underflow. This fixes a fault that could\nhappen on slow machines, where data is received faster than the CPU can\nhandle. In such a case the device will use up all rx descriptors and\nrefuse to send any more data before confirming that it is ok. This\npatch enables necessary interrupt to discover such a situation and will\nhandle them by dropping everything in the ring buffer.\n\nReviewed-by: Michael Buesch <m@bues.ch>\nSigned-off-by: Thommy Jakobsson <thommyj@gmail.com>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/3f28610e6571188e07c2dea303c837e99f9e3f09"},{"sha":"30e4585b0d2a8a5a3afd4ad7fa499455adece335","author":{"email":"c1b6782c4af8f0673da8923a0702a1832e5940f4@ffwll.ch","name":"Daniel Vetter"},"message":"drm/mm: fix dump table BUG\n\ncommit 3a359f0b21ab218c1bf7a6a1b638b6fd143d0b99 upstream.\n\nIn\n\ncommit 9e8944ab564f2e3dde90a518cd32048c58918608\nAuthor: Chris Wilson <chris@chris-wilson.co.uk>\nDate:   Thu Nov 15 11:32:17 2012 +0000\n\n    drm: Introduce an iterator over holes in the drm_mm range manager\n\nhelpers and iterators for hole handling have been introduced with some\ndebug BUG_ONs sprinkled over. Unfortunately this broke the mm dumper\nwhich unconditionally tried to compute the size of the very first\nhole.\n\nWhile at it unify the code a bit with the hole dumping in the loop.\n\nv2: Extract a hole dump helper.\n\nReported-by: Christopher Harvey <charvey@matrox.com>\nCc: Christopher Harvey <charvey@matrox.com>\nCc: Dave Airlie <airlied@redhat.com>\nCc: Chris Wilson <chris@chris-wilson.co.uk>\nAcked-by: Dave Airlie <airlied@redhat.com>\nSigned-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-M/commits/30e4585b0d2a8a5a3afd4ad7fa499455adece335"}]}