{"push_id":2182949850,"size":97,"distinct_size":97,"ref":"refs/heads/stock-wip","head":"46303012180778d62221c1961c0a8c265b00a4db","before":"6f576ebac996843382ad23545065cc3efefcf82f","commits":[{"sha":"33cba355949c224a7c7ac530bbc1b0f187179d4b","author":{"name":"Ming Lei","email":"72a707b21fef18e5518655f1512233913e52ba1f@canonical.com"},"message":"Bluetooth: Add support for Dell[QCA 0cf3:817a]\n\ncommit ebaf5795ef57a70a042ea259448a465024e2821d upstream.\n\nAdd support for the AR9462 chip\n\nT:  Bus=03 Lev=01 Prnt=01 Port=08 Cnt=01 Dev#=  5 Spd=12   MxCh= 0\nD:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1\nP:  Vendor=0cf3 ProdID=817a Rev= 0.02\nC:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA\nI:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms\nE:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms\nE:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms\nI:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms\nE:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms\nI:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms\nE:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms\nI:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms\nE:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms\nI:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms\nE:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms\nI:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms\nE:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms\nI:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms\nE:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms\n\nSigned-off-by: Ming Lei <ming.lei@canonical.com>\nCc: Gustavo Padovan <gustavo.padovan@collabora.co.uk>\nSigned-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/33cba355949c224a7c7ac530bbc1b0f187179d4b"},{"sha":"0fd1fcdec7031e9eba03ab88a5172fce6baf05ec","author":{"name":"Ian Abbott","email":"494c7f4da2ed9b356b47e2dfeca52bf8ebbb3680@mev.co.uk"},"message":"staging: comedi: s626: fix continuous acquisition\n\ncommit e4317ce877a31dbb9d96375391c1c4ad2210d637 upstream.\n\nFor the s626 driver, there is a bug in the handling of asynchronous\ncommands on the AI subdevice when the stop source is `TRIG_NONE`.  The\ncommand should run continuously until cancelled, but the interrupt\nhandler stops the command running after the first scan.\n\nThe command set-up function `s626_ai_cmd()` contains this code:\n\n\tswitch (cmd->stop_src) {\n\tcase TRIG_COUNT:\n\t\t/*  data arrives as one packet */\n\t\tdevpriv->ai_sample_count = cmd->stop_arg;\n\t\tdevpriv->ai_continous = 0;\n\t\tbreak;\n\tcase TRIG_NONE:\n\t\t/*  continous acquisition */\n\t\tdevpriv->ai_continous = 1;\n\t\tdevpriv->ai_sample_count = 0;\n\t\tbreak;\n\t}\n\nThe interrupt handler `s626_irq_handler()` contains this code:\n\n\t\tif (!(devpriv->ai_continous))\n\t\t\tdevpriv->ai_sample_count--;\n\t\tif (devpriv->ai_sample_count <= 0) {\n\t\t\tdevpriv->ai_cmd_running = 0;\n\t\t\t/* ... */\n\t\t}\n\nSo `devpriv->ai_sample_count` is only decremented for the `TRIG_COUNT`\ncase, but `devpriv->ai_cmd_running` is set to 0 (and the command\nstopped) regardless.\n\nFix this in `s626_ai_cmd()` by setting `devpriv->ai_sample_count = 1`\nfor the `TRIG_NONE` case.  The interrupt handler will not decrement it\nso it will remain greater than 0 and the check for stopping the\nacquisition will fail.\n\nSigned-off-by: Ian Abbott <abbotti@mev.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/0fd1fcdec7031e9eba03ab88a5172fce6baf05ec"},{"sha":"5329034bb870266da550baaa7fbfc2cad3fd00b8","author":{"name":"Ming Lei","email":"72a707b21fef18e5518655f1512233913e52ba1f@canonical.com"},"message":"sysfs: fix race between readdir and lseek\n\ncommit 991f76f837bf22c5bb07261cfd86525a0a96650c upstream.\n\nWhile readdir() is running, lseek() may set filp->f_pos as zero,\nthen may leave filp->private_data pointing to one sysfs_dirent\nobject without holding its reference counter, so the sysfs_dirent\nobject may be used after free in next readdir().\n\nThis patch holds inode->i_mutex to avoid the problem since\nthe lock is always held in readdir path.\n\nReported-by: Dave Jones <davej@redhat.com>\nTested-by: Sasha Levin <levinsasha928@gmail.com>\nSigned-off-by: Ming Lei <ming.lei@canonical.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/5329034bb870266da550baaa7fbfc2cad3fd00b8"},{"sha":"397528487a13a500d568f683c9a3b85bcc79e39f","author":{"name":"Ming Lei","email":"72a707b21fef18e5518655f1512233913e52ba1f@canonical.com"},"message":"sysfs: handle failure path correctly for readdir()\n\ncommit e5110f411d2ee35bf8d202ccca2e89c633060dca upstream.\n\nIn case of 'if (filp->f_pos ==  0 or 1)' of sysfs_readdir(),\nthe failure from filldir() isn't handled, and the reference counter\nof the sysfs_dirent object pointed by filp->private_data will be\nreleased without clearing filp->private_data, so use after free\nbug will be triggered later.\n\nThis patch returns immeadiately under the situation for fixing the bug,\nand it is reasonable to return from readdir() when filldir() fails.\n\nReported-by: Dave Jones <davej@redhat.com>\nTested-by: Sasha Levin <levinsasha928@gmail.com>\nSigned-off-by: Ming Lei <ming.lei@canonical.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/397528487a13a500d568f683c9a3b85bcc79e39f"},{"sha":"7ace374646bd53c62b4d6748fca9024e53846aa6","author":{"name":"Marc Kleine-Budde","email":"86a3a4ad69448b8f7c92083394f83d765887082e@pengutronix.de"},"message":"can: sja1000: fix define conflict on SH\n\ncommit f901b6bc404b67d96eca739857c097e022727b71 upstream.\n\nThias patch fixes a define conflict between the SH architecture and the sja1000\ndriver:\n\n    drivers/net/can/sja1000/sja1000.h:59:0: warning:\n        \"REG_SR\" redefined [enabled by default]\n    arch/sh/include/asm/ptrace_32.h:25:0: note:\n         this is the location of the previous definition\n\nA SJA1000_ prefix is added to the offending sja1000 define only, to make a\nminimal patch suited for stable. A later patch will add a SJA1000_ prefix to\nall defines in sja1000.h.\n\nReported-by: Fengguang Wu <fengguang.wu@intel.com>\nSigned-off-by: Marc Kleine-Budde <mkl@pengutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/7ace374646bd53c62b4d6748fca9024e53846aa6"},{"sha":"7f26f984654865ae771debdb21a512d16d30367c","author":{"name":"Felix Fietkau","email":"8cf1b58efcecbc12846b1b7b0c62f2bc67216d26@openwrt.org"},"message":"ath9k_hw: revert chainmask to user configuration after calibration\n\ncommit 74632d11a133b5baf6b9d622dd19d2f944d93d94 upstream.\n\nThe commit 'ath9k_hw: fix calibration issues on chainmask that don't\ninclude chain 0' changed the hardware chainmask to the chip chainmask\nfor the duration of the calibration, but the revert to user\nconfiguration in the reset path runs too early.\n\nThat causes some issues with limiting the number of antennas (including\nspurious failure in hardware-generated packets).\n\nFix this by reverting the chainmask after the essential parts of the\ncalibration that need the workaround, and before NF calibration is run.\n\nSigned-off-by: Felix Fietkau <nbd@openwrt.org>\nReported-by: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>\nTested-by: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/7f26f984654865ae771debdb21a512d16d30367c"},{"sha":"1e01f0afb4ba9b6e7ab8ed085ecfba1eac4e62bd","author":{"name":"Josh Boyer","email":"e24ddf329890aac7d3872652a1775b5739162df4@redhat.com"},"message":"HID: usbhid: quirk for Realtek Multi-card reader\n\ncommit 3d464d9b71ef2f2b40a4bc9dcf06794fd1be9d12 upstream.\n\nThis device needs to be added to the quirks list with HID_QUIRK_NO_INIT_REPORTS,\notherwise it causes 10 seconds timeout during report initialization.\n\nThis fixes Red Hat bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=806587\n\nSigned-off-by: Josh Boyer <jwboyer@redhat.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/1e01f0afb4ba9b6e7ab8ed085ecfba1eac4e62bd"},{"sha":"a56e4c761a68dece4fc132c4abc32565f742549d","author":{"name":"Jussi Kivilinna","email":"ebedc8c519d2fd32b0904e7d3f397751a366765e@iki.fi"},"message":"rtlwifi: usb: add missing freeing of skbuff\n\ncommit 36ef0b473fbf43d5db23eea4616cc1d18cec245f upstream.\n\nSigned-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi>\nAcked-by: Larry Finger <Larry.Finger@lwfinger.net>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/a56e4c761a68dece4fc132c4abc32565f742549d"},{"sha":"b0ed690a761b9c5380cd315ca480f9e39f9de777","author":{"name":"Rafał Miłecki","email":"de5d087365c8139236c33844c5e7521dcce45b14@gmail.com"},"message":"b43: N-PHY: increase initial value of \"mind\" in RSSI calibration\n\ncommit e67dd874e60529dbd2e8232babb1e23479ba2ffa upstream.\n\nWe're using \"mind\" variable to find the VCM that got the best polling\nresults. For each VCM we calculte \"currd\" which is compared to the\n\"mind\". For PHY rev3+ \"currd\" gets values around 14k-40k. Looking for a\nvalue smaller than 40 makes no sense, so increase the initial value.\n\nThis fixes a regression introduced in 3.4 by commit:\ne0c9a0219a8f542e3946fe972a68aacf8c3f906c\n(my BCM4322 performance dropped from 18,4Mb/s to 9,26Mb/s)\n\nSigned-off-by: Rafał Miłecki <zajec5@gmail.com>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/b0ed690a761b9c5380cd315ca480f9e39f9de777"},{"sha":"95fe2a602b08c314012d1acc937d7fc3cbd305f8","author":{"name":"Iestyn C. Elfick","email":"e5ec4044095f807ee1f77f9ae9689cb2e726eafc@gmail.com"},"message":"b43: A fix for DMA transmission sequence errors\n\ncommit b251412db99ccd4495ce372fec7daee27bf06923 upstream.\n\nIntermittently, b43 will report \"Out of order TX status report on DMA ring\".\nWhen this happens, the driver must be reset before communication can resume.\nThe cause of the problem is believed to be an error in the closed-source\nfirmware; however, all versions of the firmware are affected.\n\nThis change uses the observation that the expected status is always 2 less\nthan the observed value, and supplies a fake status report to skip one\nheader/data pair.\n\nNot all devices suffer from this problem, but it can occur several times\nper second under heavy load. As each occurence kills the unmodified driver,\nthis patch makes if possible for the affected devices to function. The patch\nlogs only the first instance of the reset operation to prevent spamming\nthe logs.\n\nTested-by: Chris Vine <chris@cvine.freeserve.co.uk>\nSigned-off-by: Larry Finger <Larry.Finger@lwfinger.net>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/95fe2a602b08c314012d1acc937d7fc3cbd305f8"},{"sha":"f7d3eb5d3195832a61a55b021bbc75a3a1cd6ab7","author":{"name":"Rafał Miłecki","email":"de5d087365c8139236c33844c5e7521dcce45b14@gmail.com"},"message":"b43: N-PHY: use more bits for offset in RSSI calibration\n\ncommit 2e1253d640eb7f8707d2591c93097c1e9f9c71d5 upstream.\n\nWhen calculating \"offset\" for final RSSI calibration we're using numbers\nbigger than s8 can hold. We have for example:\noffset[j] = 232 - poll_results[j];\nformula. If poll_results[j] is small enough (it usually is) we treat\nnumber's bit as a sign bit. For example 232 - 1 becomes:\n0xE8 - 0x1 = 0xE7, which is not 231 but -25.\n\nThis code was introduced in e0c9a0219a8f542e3946fe972a68aacf8c3f906c\nand caused stability regression on some cards, for ex. BCM4322.\n\nSigned-off-by: Rafał Miłecki <zajec5@gmail.com>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/f7d3eb5d3195832a61a55b021bbc75a3a1cd6ab7"},{"sha":"6489dc1309733de4eb0e93cb94c6453474b65055","author":{"name":"Kees Cook","email":"999bfbbf6e15a9d6aba3dfebadcec55340f87c3f@chromium.org"},"message":"tg3: fix length overflow in VPD firmware parsing\n\ncommit 715230a44310a8cf66fbfb5a46f9a62a9b2de424 upstream.\n\nCommit 184b89044fb6e2a74611dafa69b1dce0d98612c6 (\"tg3: Use VPD fw version\nwhen present\") introduced VPD parsing that contained a potential length\noverflow.\n\nLimit the hardware's reported firmware string length (max 255 bytes) to\nstay inside the driver's firmware string length (32 bytes). On overflow,\ntruncate the formatted firmware string instead of potentially overwriting\nportions of the tg3 struct.\n\nhttp://cansecwest.com/slides/2013/PrivateCore%20CSW%202013.pdf\n\nSigned-off-by: Kees Cook <keescook@chromium.org>\nReported-by: Oded Horovitz <oded@privatecore.com>\nReported-by: Brad Spengler <spender@grsecurity.net>\nCc: Matt Carlson <mcarlson@broadcom.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/6489dc1309733de4eb0e93cb94c6453474b65055"},{"sha":"5717451b304899a439fd748919ae5e4cfb7bd519","author":{"name":"Joerg Roedel","email":"d25114f783851316b476036d456793fb259fc7ef@8bytes.org"},"message":"iommu/amd: Make sure dma_ops are set for hotplug devices\n\ncommit c2a2876e863356b092967ea62bebdb4dd663af80 upstream.\n\nThere is a bug introduced with commit 27c2127 that causes\ndevices which are hot unplugged and then hot-replugged to\nnot have per-device dma_ops set. This causes these devices\nto not function correctly. Fixed with this patch.\n\nReported-by: Andreas Degert <andreas.degert@googlemail.com>\nSigned-off-by: Joerg Roedel <joro@8bytes.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/5717451b304899a439fd748919ae5e4cfb7bd519"},{"sha":"942c665be95a001553d062e14c3a8a3a138d41cc","author":{"name":"David Vrabel","email":"0622fb2836634876d1b2a72d98e1723882d22bb8@citrix.com"},"message":"xen/blkback: correctly respond to unknown, non-native requests\n\ncommit 0e367ae46503cfe7791460c8ba8434a5d60b2bd5 upstream.\n\nIf the frontend is using a non-native protocol (e.g., a 64-bit\nfrontend with a 32-bit backend) and it sent an unrecognized request,\nthe request was not translated and the response would have the\nincorrect ID.  This may cause the frontend driver to behave\nincorrectly or crash.\n\nSince the ID field in the request is always in the same place,\nregardless of the request type we can get the correct ID and make a\nvalid response (which will report BLKIF_RSP_EOPNOTSUPP).\n\nThis bug affected 64-bit SLES 11 guests when using a 32-bit backend.\nThis guest does a BLKIF_OP_RESERVED_1 (BLKIF_OP_PACKET in the SLES\nsource) and would crash in blkif_int() as the ID in the response would\nbe invalid.\n\nSigned-off-by: David Vrabel <david.vrabel@citrix.com>\nSigned-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/942c665be95a001553d062e14c3a8a3a138d41cc"},{"sha":"485cc1b2be52f35e23febd2cfd79d0e31c61d4fa","author":{"name":"Jan Beulich","email":"1fd971496e1aa6d286ec629ae628ee3e35c09db5@suse.com"},"message":"xen-blkback: fix dispatch_rw_block_io() error path\n\ncommit 0e5e098ac22dae38f957e951b70d3cf73beff0f7 upstream.\n\nCommit 7708992 (\"xen/blkback: Seperate the bio allocation and the bio\nsubmission\") consolidated the pendcnt updates to just a single write,\nneglecting the fact that the error path relied on it getting set to 1\nup front (such that the decrement in __end_block_io_op() would actually\ndrop the count to zero, triggering the necessary cleanup actions).\n\nAlso remove a misleading and a stale (after said commit) comment.\n\nSigned-off-by: Jan Beulich <jbeulich@suse.com>\nSigned-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/485cc1b2be52f35e23febd2cfd79d0e31c61d4fa"},{"sha":"993f5d53e3a12fcc80e6e2343e43108f85fe5aa6","author":{"name":"Pawel Wieczorkiewicz","email":"9b48093cb02976edf445753675ff639b0c1b2207@gmail.com"},"message":"tty: atmel_serial_probe(): index of atmel_ports[] fix\n\ncommit 503bded92da283b2f31d87e054c4c6d30c3c2340 upstream.\n\nIndex of atmel_ports[ATMEL_MAX_UART] should be smaller\nthan ATMEL_MAX_UART.\n\nSigned-off-by: Pawel Wieczorkiewicz <wpawel@gmail.com>\nAcked-by: Nicolas Ferre <nicolas.ferre@atmel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/993f5d53e3a12fcc80e6e2343e43108f85fe5aa6"},{"sha":"6eab9906032d98ab4a890b82d18f6db2a6896b19","author":{"name":"Konstantin Holoborodko","email":"95c61c2cc68c5d46a970ccfe9176e33a9cafd435@gmail.com"},"message":"usb: ftdi_sio: Add support for Mitsubishi FX-USB-AW/-BD\n\ncommit 482b0b5d82bd916cc0c55a2abf65bdc69023b843 upstream.\n\nIt enhances the driver for FTDI-based USB serial adapters\nto recognize Mitsubishi Electric Corp. USB/RS422 Converters\nas FT232BM chips and support them.\nhttps://search.meau.com/?q=FX-USB-AW\n\nSigned-off-by: Konstantin Holoborodko <klh.kernel@gmail.com>\nTested-by: Konstantin Holoborodko <klh.kernel@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/6eab9906032d98ab4a890b82d18f6db2a6896b19"},{"sha":"bbcf4fdca24dee33dc584aa08b8fa92450e02069","author":{"name":"Al Viro","email":"2a537e97523ffee458777df5f34a2f8c9964f945@zeniv.linux.org.uk"},"message":"vt: synchronize_rcu() under spinlock is not nice...\n\ncommit e8cd81693bbbb15db57d3c9aa7dd90eda4842874 upstream.\n\nvcs_poll_data_free() calls unregister_vt_notifier(), which calls\natomic_notifier_chain_unregister(), which calls synchronize_rcu().\nDo it *after* we'd dropped ->f_lock.\n\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/bbcf4fdca24dee33dc584aa08b8fa92450e02069"},{"sha":"253f66ad3194012932a5cd992400ded0d5cc3d39","author":{"name":"Bing Zhao","email":"acd91236852544b6ed6e9c5ee5f7d8809e48f977@marvell.com"},"message":"mwifiex: cancel cmd timer and free curr_cmd in shutdown process\n\ncommit 084c7189acb3f969c855536166042e27f5dd703f upstream.\n\ncurr_cmd points to the command that is in processing or waiting\nfor its command response from firmware. If the function shutdown\nhappens to occur at this time we should cancel the cmd timer and\nput the command back to free queue.\n\nTested-by: Marco Cesarano <marco@marvell.com>\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>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/253f66ad3194012932a5cd992400ded0d5cc3d39"},{"sha":"207d44873e6d2a0564e9e2f75b0b2c7ef27cf8a3","author":{"name":"fanchaoting","email":"b8f96616699445cc0e34bc932f0ab0b03234061c@cn.fujitsu.com"},"message":"pnfs-block: removing DM device maybe cause oops when call dev_remove\n\ncommit 4376c94618c26225e69e17b7c91169c45a90b292 upstream.\n\nwhen pnfs block using device mapper,if umounting later,it maybe\ncause oops. we apply \"1 + sizeof(bl_umount_request)\" memory for\nmsg->data, the memory maybe overflow when we do \"memcpy(&dataptr\n[sizeof(bl_msg)], &bl_umount_request, sizeof(bl_umount_request))\",\nbecause the size of bl_msg is more than 1 byte.\n\nSigned-off-by: fanchaoting<fanchaoting@cn.fujitsu.com>\nSigned-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/SmartPack/SmartPack-Kernel-Project_kltexxx/commits/207d44873e6d2a0564e9e2f75b0b2c7ef27cf8a3"}]}
{"actor":{"display_login":"sunilpaulmathew"}}