{"push_id":1137427801,"size":748,"distinct_size":748,"ref":"refs/heads/6.0.1","head":"e6951e7d49226b4e71833a28d4df3b246323e2b5","before":"ac9a971272b8342574905add3eafe5f361af9bba","commits":[{"sha":"9083cb065a03722697dc5b81cfb2d0d426a73f82","author":{"name":"David Matlack","email":"523bec985bc5508cd610fc1b83e7d4aa80ac8a25@google.com"},"message":"kvm: x86: fix stale mmio cache bug\n\ncommit 56f17dd3fbc44adcdbc3340fe3988ddb833a47a7 upstream.\n\nThe following events can lead to an incorrect KVM_EXIT_MMIO bubbling\nup to userspace:\n\n(1) Guest accesses gpa X without a memory slot. The gfn is cached in\nstruct kvm_vcpu_arch (mmio_gfn). On Intel EPT-enabled hosts, KVM sets\nthe SPTE write-execute-noread so that future accesses cause\nEPT_MISCONFIGs.\n\n(2) Host userspace creates a memory slot via KVM_SET_USER_MEMORY_REGION\ncovering the page just accessed.\n\n(3) Guest attempts to read or write to gpa X again. On Intel, this\ngenerates an EPT_MISCONFIG. The memory slot generation number that\nwas incremented in (2) would normally take care of this but we fast\npath mmio faults through quickly_check_mmio_pf(), which only checks\nthe per-vcpu mmio cache. Since we hit the cache, KVM passes a\nKVM_EXIT_MMIO up to userspace.\n\nThis patch fixes the issue by using the memslot generation number\nto validate the mmio cache.\n\nSigned-off-by: David Matlack <dmatlack@google.com>\n[xiaoguangrong: adjust the code to make it simpler for stable-tree fix.]\nSigned-off-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>\nReviewed-by: David Matlack <dmatlack@google.com>\nReviewed-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>\nTested-by: David Matlack <dmatlack@google.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/9083cb065a03722697dc5b81cfb2d0d426a73f82"},{"sha":"a5b4755f4bd37cef9498e2d53a8cd666361e3cbe","author":{"name":"Artem Bityutskiy","email":"41ea5dbf7c14082392bca66bc06c733fa8b2e808@linux.intel.com"},"message":"UBIFS: remove mst_mutex\n\ncommit 07e19dff63e3d5d6500d831e36554ac9b1b0560e upstream.\n\nThe 'mst_mutex' is not needed since because 'ubifs_write_master()' is only\ncalled on the mount path and commit path. The mount path is sequential and\nthere is no parallelism, and the commit path is also serialized - there is only\none commit going on at a time.\n\nSigned-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/a5b4755f4bd37cef9498e2d53a8cd666361e3cbe"},{"sha":"db73d4fcba98f8427d820b9e3cae01f1ec604233","author":{"name":"Artem Bityutskiy","email":"41ea5dbf7c14082392bca66bc06c733fa8b2e808@linux.intel.com"},"message":"UBIFS: fix a race condition\n\ncommit 052c28073ff26f771d44ef33952a41d18dadd255 upstream.\n\nHu (hujianyang@huawei.com) discovered a race condition which may lead to a\nsituation when UBIFS is unable to mount the file-system after an unclean\nreboot. The problem is theoretical, though.\n\nIn UBIFS, we have the log, which basically a set of LEBs in a certain area. The\nlog has the tail and the head.\n\nEvery time user writes data to the file-system, the UBIFS journal grows, and\nthe log grows as well, because we append new reference nodes to the head of the\nlog. So the head moves forward all the time, while the log tail stays at the\nsame position.\n\nAt any time, the UBIFS master node points to the tail of the log. When we mount\nthe file-system, we scan the log, and we always start from its tail, because\nthis is where the master node points to. The only occasion when the tail of the\nlog changes is the commit operation.\n\nThe commit operation has 2 phases - \"commit start\" and \"commit end\". The former\nis relatively short, and does not involve much I/O. During this phase we mostly\njust build various in-memory lists of the things which have to be written to\nthe flash media during \"commit end\" phase.\n\nDuring the commit start phase, what we do is we \"clean\" the log. Indeed, the\ncommit operation will index all the data in the journal, so the entire journal\n\"disappears\", and therefore the data in the log become unneeded. So we just\nmove the head of the log to the next LEB, and write the CS node there. This LEB\nwill be the tail of the new log when the commit operation finishes.\n\nWhen the \"commit start\" phase finishes, users may write more data to the\nfile-system, in parallel with the ongoing \"commit end\" operation. At this point\nthe log tail was not changed yet, it is the same as it had been before we\nstarted the commit. The log head keeps moving forward, though.\n\nThe commit operation now needs to write the new master node, and the new master\nnode should point to the new log tail. After this the LEBs between the old log\ntail and the new log tail can be unmapped and re-used again.\n\nAnd here is the possible problem. We do 2 operations: (a) We first update the\nlog tail position in memory (see 'ubifs_log_end_commit()'). (b) And then we\nwrite the master node (see the big lock of code in 'do_commit()').\n\nBut nothing prevents the log head from moving forward between (a) and (b), and\nthe log head may \"wrap\" now to the old log tail. And when the \"wrap\" happens,\nthe contends of the log tail gets erased. Now a power cut happens and we are in\ntrouble. We end up with the old master node pointing to the old tail, which was\nerased. And replay fails because it expects the master node to point to the\ncorrect log tail at all times.\n\nThis patch merges the abovementioned (a) and (b) operations by moving the master\nnode change code to the 'ubifs_log_end_commit()' function, so that it runs with\nthe log mutex locked, which will prevent the log from being changed benween\noperations (a) and (b).\n\nReported-by: hujianyang <hujianyang@huawei.com>\nTested-by: hujianyang <hujianyang@huawei.com>\nSigned-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/db73d4fcba98f8427d820b9e3cae01f1ec604233"},{"sha":"82508e0f0bdd4fd1090fc8ee09c6b94e170f78a5","author":{"name":"Artem Bityutskiy","email":"41ea5dbf7c14082392bca66bc06c733fa8b2e808@linux.intel.com"},"message":"UBIFS: fix free log space calculation\n\ncommit ba29e721eb2df6df8f33c1f248388bb037a47914 upstream.\n\nHu (hujianyang <hujianyang@huawei.com>) discovered an issue in the\n'empty_log_bytes()' function, which calculates how many bytes are left in the\nlog:\n\n\"\nIf 'c->lhead_lnum + 1 == c->ltail_lnum' and 'c->lhead_offs == c->leb_size', 'h'\nwould equalent to 't' and 'empty_log_bytes()' would return 'c->log_bytes'\ninstead of 0.\n\"\n\nAt this point it is not clear what would be the consequences of this, and\nwhether this may lead to any problems, but this patch addresses the issue just\nin case.\n\nTested-by: hujianyang <hujianyang@huawei.com>\nReported-by: hujianyang <hujianyang@huawei.com>\nSigned-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/82508e0f0bdd4fd1090fc8ee09c6b94e170f78a5"},{"sha":"d480591d22c6ccf8327da5716f96a41ae1cb9663","author":{"name":"Champion Chen","email":"ec4b6b2aa2d09925b4e87872b15a556c33f036df@realsil.com.cn"},"message":"Bluetooth: Fix issue with USB suspend in btusb driver\n\ncommit 85560c4a828ec9c8573840c9b66487b6ae584768 upstream.\n\nSuspend could fail for some platforms because\nbtusb_suspend==> btusb_stop_traffic ==> usb_kill_anchored_urbs.\n\nWhen btusb_bulk_complete returns before system suspend and resubmits\nan URB, the system cannot enter suspend state.\n\nSigned-off-by: Champion Chen <champion_chen@realsil.com.cn>\nSigned-off-by: Larry Finger <Larry.Finger@lwfinger.net>\nSigned-off-by: Marcel Holtmann <marcel@holtmann.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/d480591d22c6ccf8327da5716f96a41ae1cb9663"},{"sha":"c002aa006faa936b9b1c29431807fe8ab97df1b2","author":{"name":"Christian Borntraeger","email":"fc33f3ee5609c5ec6047db37e69d0178239969f7@de.ibm.com"},"message":"KVM: s390: unintended fallthrough for external call\n\ncommit f346026e55f1efd3949a67ddd1dcea7c1b9a615e upstream.\n\nWe must not fallthrough if the conditions for external call are not met.\n\nSigned-off-by: Christian Borntraeger <borntraeger@de.ibm.com>\nReviewed-by: Thomas Huth <thuth@linux.vnet.ibm.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/c002aa006faa936b9b1c29431807fe8ab97df1b2"},{"sha":"7cf009d054e48bea3eb70af362d8c58b22baadec","author":{"name":"Andreas Noever","email":"43fb328dd0aa516f5e8b122b47ec451062182f80@gmail.com"},"message":"PCI: pciehp: Prevent NULL dereference during probe\n\ncommit bceee4a97eb58bd0e80e39eff11b506ddd9e7ad3 upstream.\n\npciehp assumes that dev->subordinate, the struct pci_bus for a bridge's\nsecondary bus, exists.  But we do not create that bus if we run out of bus\nnumbers during enumeration.  This leads to a NULL dereference in\ninit_slot() (and other places).\n\nChange pciehp_probe() to return -ENODEV when no secondary bus is present.\n\nSigned-off-by: Andreas Noever <andreas.noever@gmail.com>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/7cf009d054e48bea3eb70af362d8c58b22baadec"},{"sha":"a66b378950318cc5ab9be8eb3f21dd2383ae18b9","author":{"name":"Douglas Lehr","email":"8e4c21cfa7f122536e72f4c088d134ebfb1e6405@us.ibm.com"},"message":"PCI: Increase IBM ipr SAS Crocodile BARs to at least system page size\n\ncommit 9fe373f9997b48fcd6222b95baf4a20c134b587a upstream.\n\nThe Crocodile chip occasionally comes up with 4k and 8k BAR sizes.  Due to\nan erratum, setting the SR-IOV page size causes the physical function BARs\nto expand to the system page size.  Since ppc64 uses 64k pages, when Linux\ntries to assign the smaller resource sizes to the now 64k BARs the address\nwill be truncated and the BARs will overlap.\n\nForce Linux to allocate the resource as a full page, which avoids the\noverlap.\n\n[bhelgaas: print expanded resource, too]\nSigned-off-by: Douglas Lehr <dllehr@us.ibm.com>\nSigned-off-by: Anton Blanchard <anton@samba.org>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nAcked-by: Milton Miller <miltonm@us.ibm.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/a66b378950318cc5ab9be8eb3f21dd2383ae18b9"},{"sha":"2d150da34ec69ac10329d01cab11e9334d0faba7","author":{"name":"Johan Hedberg","email":"96898026c3f4a50ee66f26e7291d450d5b98554a@intel.com"},"message":"Bluetooth: Fix setting correct security level when initiating SMP\n\ncommit 5eb596f55cacc2389554a8d7572d90d5e9d4269d upstream.\n\nWe can only determine the final security level when both pairing request\nand response have been exchanged. When initiating pairing the starting\ntarget security level is set to MEDIUM unless explicitly specified to be\nHIGH, so that we can still perform pairing even if the remote doesn't\nhave MITM capabilities. However, once we've received the pairing\nresponse we should re-consult the remote and local IO capabilities and\nupgrade the target security level if necessary.\n\nWithout this patch the resulting Long Term Key will occasionally be\nreported to be unauthenticated when it in reality is an authenticated\none.\n\nSigned-off-by: Johan Hedberg <johan.hedberg@intel.com>\nSigned-off-by: Marcel Holtmann <marcel@holtmann.org>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/2d150da34ec69ac10329d01cab11e9334d0faba7"},{"sha":"8e48aa5819ec9d87953110ca6ea2079b17d94524","author":{"name":"Guenter Roeck","email":"177f6c7e7d0681e1b64ab10ef561094344edf6d6@roeck-us.net"},"message":"Revert \"percpu: free percpu allocation info for uniprocessor system\"\n\ncommit bb2e226b3bef596dd56be97df655d857b4603923 upstream.\n\nThis reverts commit 3189eddbcafc (\"percpu: free percpu allocation info for\nuniprocessor system\").\n\nThe commit causes a hang with a crisv32 image. This may be an architecture\nproblem, but at least for now the revert is necessary to be able to boot a\ncrisv32 image.\n\nCc: Tejun Heo <tj@kernel.org>\nCc: Honggang Li <enjoymindful@gmail.com>\nSigned-off-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Tejun Heo <tj@kernel.org>\nFixes: 3189eddbcafc (\"percpu: free percpu allocation info for uniprocessor system\")\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/8e48aa5819ec9d87953110ca6ea2079b17d94524"},{"sha":"810c74bd39235ef7b9f166e842efb6f2b42a9c3b","author":{"name":"Joe Savage","email":"3c31257cb5a1f69a4486903da58b68b9e5d5b528@goketra.com"},"message":"USB: serial: cp210x: added Ketra N1 wireless interface support\n\ncommit bfc2d7dfdd761ae3beccdb26abebe03cef042f46 upstream.\n\nAdded support for Ketra N1 wireless interface, which uses the\nSilicon Labs' CP2104 USB to UART bridge with customized PID 8946.\n\nSigned-off-by: Joe Savage <joe.savage@goketra.com>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/810c74bd39235ef7b9f166e842efb6f2b42a9c3b"},{"sha":"a84663095ae6c00ecb0dcc07a0b82801aa33180f","author":{"name":"Andreas Bomholtz","email":"80b780c8305f0f75fc9380899bda91aa1af94a74@seluxit.com"},"message":"USB: cp210x: add support for Seluxit USB dongle\n\ncommit dee80ad12d2b1b304286a707fde7ab05d1fc7bab upstream.\n\nAdded the Seluxit ApS USB Serial Dongle to cp210x driver.\n\nSigned-off-by: Andreas Bomholtz <andreas@seluxit.com>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/a84663095ae6c00ecb0dcc07a0b82801aa33180f"},{"sha":"7a6185a12d7bc28267a0917b2cb41e8eb8adb24f","author":{"name":"Ricardo Ribalda Delgado","email":"1d916c4e2e300e3102d4ef191eab8464e77b0533@gmail.com"},"message":"PCI: Generate uppercase hex for modalias interface class\n\ncommit 89ec3dcf17fd3fa009ecf8faaba36828dd6bc416 upstream.\n\nSome implementations of modprobe fail to load the driver for a PCI device\nautomatically because the \"interface\" part of the modalias from the kernel\nis lowercase, and the modalias from file2alias is uppercase.\n\nThe \"interface\" is the low-order byte of the Class Code, defined in PCI\nr3.0, Appendix D.  Most interface types defined in the spec do not use\nalpha characters, so they won't be affected.  For example, 00h, 01h, 10h,\n20h, etc. are unaffected.\n\nPrint the \"interface\" byte of the Class Code in uppercase hex, as we\nalready do for the Vendor ID, Device ID, Class, etc.\n\n[bhelgaas: changelog]\nSigned-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nAcked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/7a6185a12d7bc28267a0917b2cb41e8eb8adb24f"},{"sha":"eea5a87d270e8d6925063019c3b0f3ff61fcb49a","author":{"name":"Lu Baolu","email":"aa0cb55c2120fe06ddbb364d78cace89fc49cea8@linux.intel.com"},"message":"USB: Add device quirk for ASUS T100 Base Station keyboard\n\ncommit ddbe1fca0bcb87ca8c199ea873a456ca8a948567 upstream.\n\nThis full-speed USB device generates spurious remote wakeup event\nas soon as USB_DEVICE_REMOTE_WAKEUP feature is set. As the result,\nLinux can't enter system suspend and S0ix power saving modes once\nthis keyboard is used.\n\nThis patch tries to introduce USB_QUIRK_IGNORE_REMOTE_WAKEUP quirk.\nWith this quirk set, wakeup capability will be ignored during\ndevice configure.\n\nThis patch could be back-ported to kernels as old as 2.6.39.\n\nSigned-off-by: Lu Baolu <baolu.lu@linux.intel.com>\nAcked-by: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/eea5a87d270e8d6925063019c3b0f3ff61fcb49a"},{"sha":"0bd172d1db29b8379fc8a78dd384c462fe833183","author":{"name":"Kees Cook","email":"999bfbbf6e15a9d6aba3dfebadcec55340f87c3f@chromium.org"},"message":"firmware_class: make sure fw requests contain a name\n\ncommit 471b095dfe0d693a8d624cbc716d1ee4d74eb437 upstream.\n\nAn empty firmware request name will trigger warnings when building\ndevice names. Make sure this is caught earlier and rejected.\n\nThe warning was visible via the test_firmware.ko module interface:\n\necho -ne \"\\x00\" > /sys/devices/virtual/misc/test_firmware/trigger_request\n\nReported-by: Sasha Levin <sasha.levin@oracle.com>\nSigned-off-by: Kees Cook <keescook@chromium.org>\nTested-by: Sasha Levin <sasha.levin@oracle.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/0bd172d1db29b8379fc8a78dd384c462fe833183"},{"sha":"3aae84bbb972584b095a9d170631d825c1dd9de2","author":{"name":"K. Y. Srinivasan","email":"a5cf196ea310dd27b5485244414a63baf7c6af2b@microsoft.com"},"message":"Drivers: hv: vmbus: Cleanup vmbus_post_msg()\n\ncommit fdeebcc62279119dbeafbc1a2e39e773839025fd upstream.\n\nPosting messages to the host can fail because of transient resource\nrelated failures. Correctly deal with these failures and increase the\nnumber of attempts to post the message before giving up.\n\nIn this version of the patch, I have normalized the error code to\nLinux error code.\n\nSigned-off-by: K. Y. Srinivasan <kys@microsoft.com>\nTested-by: Sitsofe Wheeler <sitsofe@yahoo.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/3aae84bbb972584b095a9d170631d825c1dd9de2"},{"sha":"3adbbcc200f4911123fa5c71f729958a54e9c51d","author":{"name":"K. Y. Srinivasan","email":"a5cf196ea310dd27b5485244414a63baf7c6af2b@microsoft.com"},"message":"Drivers: hv: vmbus: Cleanup vmbus_teardown_gpadl()\n\ncommit 66be653083057358724d56d817e870e53fb81ca7 upstream.\n\nEliminate calls to BUG_ON() by properly handling errors. In cases where\nrollback is possible, we will return the appropriate error to have the\ncalling code decide how to rollback state. In the case where we are\ntransferring ownership of the guest physical pages to the host,\nwe will wait for the host to respond.\n\nSigned-off-by: K. Y. Srinivasan <kys@microsoft.com>\nTested-by: Sitsofe Wheeler <sitsofe@yahoo.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/3adbbcc200f4911123fa5c71f729958a54e9c51d"},{"sha":"1e0293dd0218520d0b8e802e07357b07061882b1","author":{"name":"K. Y. Srinivasan","email":"a5cf196ea310dd27b5485244414a63baf7c6af2b@microsoft.com"},"message":"Drivers: hv: vmbus: Cleanup vmbus_establish_gpadl()\n\ncommit 72c6b71c245dac8f371167d97ef471b367d0b66b upstream.\n\nEliminate the call to BUG_ON() by waiting for the host to respond. We are\ntrying to reclaim the ownership of memory that was given to the host and so\nwe will have to wait until the host responds.\n\nSigned-off-by: K. Y. Srinivasan <kys@microsoft.com>\nTested-by: Sitsofe Wheeler <sitsofe@yahoo.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/1e0293dd0218520d0b8e802e07357b07061882b1"},{"sha":"a12dc90d616b4ea7cc2cce6d4c6b2394073daaed","author":{"name":"K. Y. Srinivasan","email":"a5cf196ea310dd27b5485244414a63baf7c6af2b@microsoft.com"},"message":"Drivers: hv: vmbus: Fix a bug in vmbus_open()\n\ncommit 45d727cee9e200f5b351528b9fb063b69cf702c8 upstream.\n\nFix a bug in vmbus_open() and properly propagate the error. I would\nlike to thank Dexuan Cui <decui@microsoft.com> for identifying the\nissue.\n\nSigned-off-by: K. Y. Srinivasan <kys@microsoft.com>\nTested-by: Sitsofe Wheeler <sitsofe@yahoo.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/a12dc90d616b4ea7cc2cce6d4c6b2394073daaed"},{"sha":"67ecb11ce62e9d87b29edbf73bf87c562206edcb","author":{"name":"K. Y. Srinivasan","email":"a5cf196ea310dd27b5485244414a63baf7c6af2b@microsoft.com"},"message":"Drivers: hv: vmbus: Cleanup vmbus_close_internal()\n\ncommit 98d731bb064a9d1817a6ca9bf8b97051334a7cfe upstream.\n\nEliminate calls to BUG_ON() in vmbus_close_internal().\nWe have chosen to potentially leak memory, than crash the guest\nin case of failures.\n\nIn this version of the patch I have addressed comments from\nDan Carpenter (dan.carpenter@oracle.com).\n\nSigned-off-by: K. Y. Srinivasan <kys@microsoft.com>\nTested-by: Sitsofe Wheeler <sitsofe@yahoo.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n[lizf: Backported to 3.4: s/return ret/return/g]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/67ecb11ce62e9d87b29edbf73bf87c562206edcb"}]}
{"actor":{"display_login":"dblockopp"}}