{"push_id":4226125498,"size":55,"distinct_size":1,"ref":"refs/heads/nougat-caf","head":"404aa49cc86ef3537a57cedfc2a75b37ab1d5b57","before":"54043b60048e4c053b0a98330bacc7585e767641","commits":[{"sha":"a57a632774a1918bf3b1e4233cfac5c5ac22af81","author":{"name":"Alan Stern","email":"75ea6bb7bfc1186f92d26164de5f9268c9a45b59@rowland.harvard.edu"},"message":"HID: usbhid: fix inconsistent reset/resume/reset-resume behavior\n\n[ Upstream commit 972e6a993f278b416a8ee3ec65475724fc36feb2 ]\n\nThe usbhid driver has inconsistently duplicated code in its post-reset,\nresume, and reset-resume pathways.\n\n\treset-resume doesn't check HID_STARTED before trying to\n\trestart the I/O queues.\n\n\tresume fails to clear the HID_SUSPENDED flag if HID_STARTED\n\tisn't set.\n\n\tresume calls usbhid_restart_queues() with usbhid->lock held\n\tand the others call it without holding the lock.\n\nThe first item in particular causes a problem following a reset-resume\nif the driver hasn't started up its I/O.  URB submission fails because\nusbhid->urbin is NULL, and this triggers an unending reset-retry loop.\n\nThis patch fixes the problem by creating a new subroutine,\nhid_restart_io(), to carry out all the common activities.  It also\nadds some checks that were missing in the original code:\n\n\tAfter a reset, there's no need to clear any halted endpoints.\n\n\tAfter a resume, if a reset is pending there's no need to\n\trestart any I/O until the reset is finished.\n\n\tAfter a resume, if the interrupt-IN endpoint is halted there's\n\tno need to submit the input URB until the halt has been\n\tcleared.\n\nSigned-off-by: Alan Stern <stern@rowland.harvard.edu>\nReported-by: Daniel Fraga <fragabr@gmail.com>\nTested-by: Daniel Fraga <fragabr@gmail.com>\nCC: <stable@vger.kernel.org>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/a57a632774a1918bf3b1e4233cfac5c5ac22af81"},{"sha":"2898d8f1c8623203ddb54fc14e215fe62f8f84aa","author":{"name":"Lokesh Vutla","email":"c1574519d727edaf2e16b260e452051ef77bf018@ti.com"},"message":"ARM: OMAP2+: hwmod: Fix updating of sysconfig register\n\n[ Upstream commit 3ca4a238106dedc285193ee47f494a6584b6fd2f ]\n\nCommit 127500ccb766f (\"ARM: OMAP2+: Only write the sysconfig on idle\nwhen necessary\") talks about verification of sysconfig cache value before\nupdating it, only during idle path. But the patch is adding the\nverification in the enable path. So, adding the check in a proper place\nas per the commit description.\n\nNot keeping this check during enable path as there is a chance of losing\ncontext and it is safe to do on idle as the context of the register will\nnever be lost while the device is active.\n\nSigned-off-by: Lokesh Vutla <lokeshvutla@ti.com>\nAcked-by: Tero Kristo <t-kristo@ti.com>\nCc: Jon Hunter <jonathanh@nvidia.com>\nCc: <stable@vger.kernel.org> # 3.12+\nFixes: commit 127500ccb766 \"ARM: OMAP2+: Only write the sysconfig on idle when necessary\"\n[paul@pwsan.com: appears to have been caused by my own mismerge of the\n originally posted patch]\nSigned-off-by: Paul Walmsley <paul@pwsan.com>\n\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/2898d8f1c8623203ddb54fc14e215fe62f8f84aa"},{"sha":"237200d1c1ec9453d491da82a7c4819a38f51344","author":{"name":"Yoshihiro Shimoda","email":"de6fb888308c49c20838826baf4e7cc406af80ff@renesas.com"},"message":"usb: renesas_usbhs: avoid NULL pointer derefernce in usbhsf_pkt_handler()\n\n[ Upstream commit 894f2fc44f2f3f48c36c973b1123f6ab298be160 ]\n\nWhen unexpected situation happened (e.g. tx/rx irq happened while\nDMAC is used), the usbhsf_pkt_handler() was possible to cause NULL\npointer dereference like the followings:\n\nUnable to handle kernel NULL pointer dereference at virtual address 00000000\npgd = c0004000\n[00000000] *pgd=00000000\nInternal error: Oops: 80000007 [#1] SMP ARM\nModules linked in: usb_f_acm u_serial g_serial libcomposite\nCPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.5.0-rc6-00842-gac57066-dirty #63\nHardware name: Generic R8A7790 (Flattened Device Tree)\ntask: c0729c00 ti: c0724000 task.ti: c0724000\nPC is at 0x0\nLR is at usbhsf_pkt_handler+0xac/0x118\npc : [<00000000>]    lr : [<c03257e0>]    psr: 60000193\nsp : c0725db8  ip : 00000000  fp : c0725df4\nr10: 00000001  r9 : 00000193  r8 : ef3ccab4\nr7 : ef3cca10  r6 : eea4586c  r5 : 00000000  r4 : ef19ceb4\nr3 : 00000000  r2 : 0000009c  r1 : c0725dc4  r0 : ef19ceb4\n\nThis patch adds a condition to avoid the dereference.\n\nFixes: e73a989 (\"usb: renesas_usbhs: add DMAEngine support\")\nCc: <stable@vger.kernel.org> # v3.1+\nSigned-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/237200d1c1ec9453d491da82a7c4819a38f51344"},{"sha":"fd06e77766cf86f28b37e9eaf784c25111b45f7c","author":{"name":"Yoshihiro Shimoda","email":"de6fb888308c49c20838826baf4e7cc406af80ff@renesas.com"},"message":"usb: renesas_usbhs: disable TX IRQ before starting TX DMAC transfer\n\n[ Upstream commit 6490865c67825277b29638e839850882600b48ec ]\n\nThis patch adds a code to surely disable TX IRQ of the pipe before\nstarting TX DMAC transfer. Otherwise, a lot of unnecessary TX IRQs\nmay happen in rare cases when DMAC is used.\n\nFixes: e73a989 (\"usb: renesas_usbhs: add DMAEngine support\")\nCc: <stable@vger.kernel.org> # v3.1+\nSigned-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/fd06e77766cf86f28b37e9eaf784c25111b45f7c"},{"sha":"ee63f2b1ef65d29a206a1bcfdd6573bacf3932d1","author":{"name":"John Keeping","email":"a51dda7c7ff50b61eaea0444371f4a6a9301e501@metanate.com"},"message":"drm/qxl: fix cursor position with non-zero hotspot\n\n[ Upstream commit d59a1f71ff1aeda4b4630df92d3ad4e3b1dfc885 ]\n\nThe SPICE protocol considers the position of a cursor to be the location\nof its active pixel on the display, so the cursor is drawn with its\ntop-left corner at \"(x - hot_spot_x, y - hot_spot_y)\" but the DRM cursor\nposition gives the location where the top-left corner should be drawn,\nwith the hotspot being a hint for drivers that need it.\n\nThis fixes the location of the window resize cursors when using Fluxbox\nwith the QXL DRM driver and both the QXL and modesetting X drivers.\n\nSigned-off-by: John Keeping <john@metanate.com>\nReviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nCc: stable@vger.kernel.org\nLink: http://patchwork.freedesktop.org/patch/msgid/1447845445-2116-1-git-send-email-john@metanate.com\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/ee63f2b1ef65d29a206a1bcfdd6573bacf3932d1"},{"sha":"e8f4639414972d17224cd816be7b89a00840b09e","author":{"name":"Oliver Neukum","email":"bfee72d94d376f4e00f72b756466867d7f9eb24e@suse.com"},"message":"USB: mct_u232: add sanity checking in probe\n\n[ Upstream commit 4e9a0b05257f29cf4b75f3209243ed71614d062e ]\n\nAn attack using the lack of sanity checking in probe is known. This\npatch checks for the existence of a second port.\n\nCVE-2016-3136\n\nSigned-off-by: Oliver Neukum <ONeukum@suse.com>\nCC: stable@vger.kernel.org\n[johan: add error message ]\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/e8f4639414972d17224cd816be7b89a00840b09e"},{"sha":"55e18b81b1d3755288aa6234d9439bdd95b3f58f","author":{"name":"Oliver Neukum","email":"bfee72d94d376f4e00f72b756466867d7f9eb24e@suse.com"},"message":"USB: cypress_m8: add endpoint sanity check\n\n[ Upstream commit c55aee1bf0e6b6feec8b2927b43f7a09a6d5f754 ]\n\nAn attack using missing endpoints exists.\n\nCVE-2016-3137\n\nSigned-off-by: Oliver Neukum <ONeukum@suse.com>\nCC: stable@vger.kernel.org\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/55e18b81b1d3755288aa6234d9439bdd95b3f58f"},{"sha":"fb6e2ebb91f21839aa13c40a6f71ac6423e4c64e","author":{"name":"Oliver Neukum","email":"bfee72d94d376f4e00f72b756466867d7f9eb24e@suse.com"},"message":"USB: digi_acceleport: do sanity checking for the number of ports\n\n[ Upstream commit 5a07975ad0a36708c6b0a5b9fea1ff811d0b0c1f ]\n\nThe driver can be crashed with devices that expose crafted descriptors\nwith too few endpoints.\n\nSee: http://seclists.org/bugtraq/2016/Mar/61\n\nSigned-off-by: Oliver Neukum <ONeukum@suse.com>\n[johan: fix OOB endpoint check and add error messages ]\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/fb6e2ebb91f21839aa13c40a6f71ac6423e4c64e"},{"sha":"9838542a2b2ea96f5a54e2b31472b7a5b2628050","author":{"name":"Martin K. Petersen","email":"0384aaef27f06874adbdb09a807bb339f4aff9fd@oracle.com"},"message":"sd: Fix excessive capacity printing on devices with blocks bigger than 512 bytes\n\n[ Upstream commit f08bb1e0dbdd0297258d0b8cd4dbfcc057e57b2a ]\n\nDuring revalidate we check whether device capacity has changed before we\ndecide whether to output disk information or not.\n\nThe check for old capacity failed to take into account that we scaled\nsdkp->capacity based on the reported logical block size. And therefore\nthe capacity test would always fail for devices with sectors bigger than\n512 bytes and we would print several copies of the same discovery\ninformation.\n\nAvoid scaling sdkp->capacity and instead adjust the value on the fly\nwhen setting the block device capacity and generating fake C/H/S\ngeometry.\n\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nCc: <stable@vger.kernel.org>\nReported-by: Hannes Reinecke <hare@suse.de>\nReviewed-by: Hannes Reinicke <hare@suse.de>\nReviewed-by: Ewan Milne <emilne@redhat.com>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/9838542a2b2ea96f5a54e2b31472b7a5b2628050"},{"sha":"4fcac08014394972bfb9b63e10e841770ad34b8e","author":{"name":"Theodore Ts'o","email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu"},"message":"ext4: add lockdep annotations for i_data_sem\n\n[ Upstream commit daf647d2dd58cec59570d7698a45b98e580f2076 ]\n\nWith the internal Quota feature, mke2fs creates empty quota inodes and\nquota usage tracking is enabled as soon as the file system is mounted.\nSince quotacheck is no longer preallocating all of the blocks in the\nquota inode that are likely needed to be written to, we are now seeing\na lockdep false positive caused by needing to allocate a quota block\nfrom inside ext4_map_blocks(), while holding i_data_sem for a data\ninode.  This results in this complaint:\n\n  Possible unsafe locking scenario:\n\n        CPU0                    CPU1\n        ----                    ----\n   lock(&ei->i_data_sem);\n                                lock(&s->s_dquot.dqio_mutex);\n                                lock(&ei->i_data_sem);\n   lock(&s->s_dquot.dqio_mutex);\n\nGoogle-Bug-Id: 27907753\n\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nCc: stable@vger.kernel.org\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/4fcac08014394972bfb9b63e10e841770ad34b8e"},{"sha":"1cbab78d2f11ad12efc8b61e2ae66f020f7b8ce1","author":{"name":"Yuki Shibuya","email":"f963e3c6684bbd501f41d18b16a7d5ddec032505@ncos.nec.co.jp"},"message":"KVM: x86: Inject pending interrupt even if pending nmi exist\n\n[ Upstream commit 321c5658c5e9192dea0d58ab67cf1791e45b2b26 ]\n\nNon maskable interrupts (NMI) are preferred to interrupts in current\nimplementation. If a NMI is pending and NMI is blocked by the result\nof nmi_allowed(), pending interrupt is not injected and\nenable_irq_window() is not executed, even if interrupts injection is\nallowed.\n\nIn old kernel (e.g. 2.6.32), schedule() is often called in NMI context.\nIn this case, interrupts are needed to execute iret that intends end\nof NMI. The flag of blocking new NMI is not cleared until the guest\nexecute the iret, and interrupts are blocked by pending NMI. Due to\nthis, iret can't be invoked in the guest, and the guest is starved\nuntil block is cleared by some events (e.g. canceling injection).\n\nThis patch injects pending interrupts, when it's allowed, even if NMI\nis blocked. And, If an interrupts is pending after executing\ninject_pending_event(), enable_irq_window() is executed regardless of\nNMI pending counter.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Yuki Shibuya <shibuya.yk@ncos.nec.co.jp>\nSuggested-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/1cbab78d2f11ad12efc8b61e2ae66f020f7b8ce1"},{"sha":"3c853788bdd85e73e9eb5bb8d3f40201a933ad93","author":{"name":"Theodore Ts'o","email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu"},"message":"ext4: ignore quota mount options if the quota feature is enabled\n\n[ Upstream commit c325a67c72903e1cc30e990a15ce745bda0dbfde ]\n\nPreviously, ext4 would fail the mount if the file system had the quota\nfeature enabled and quota mount options (used for the older quota\nsetups) were present.  This broke xfstests, since xfs silently ignores\nthe usrquote and grpquota mount options if they are specified.  This\ncommit changes things so that we are consistent with xfs; having the\nmount options specified is harmless, so no sense break users by\nforbidding them.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/3c853788bdd85e73e9eb5bb8d3f40201a933ad93"},{"sha":"186b929c6b1e2db6310858f438b178cc2d00a876","author":{"name":"Eric Wong","email":"8c2951295f8292b0c03727bc4652981172298eae@yhbt.net"},"message":"ALSA: usb-audio: don't try to get Outlaw RR2150 sample rate\n\n[ Upstream commit 2f80b2958abe5658000d5ad9b45a36ecf879666e ]\n\nThis quirk allows us to avoid the noisy:\n\n\tcurrent rate 0 is different from the runtime rate\n\nmessage every time playback starts.  While USB DAC in the RR2150\nsupports reading the sample rate, it never returns a sample rate\nother than zero in my observation with common sample rates.\n\nSigned-off-by: Eric Wong <normalperson@yhbt.net>\nCc: Joe Turner <joe@oampo.co.uk>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/186b929c6b1e2db6310858f438b178cc2d00a876"},{"sha":"b672486754838d943a7a2769ed6e55ef169dcd12","author":{"name":"Anssi Hannula","email":"a67f875f3f4d9a809275c1d14e68c85c921fe2e8@iki.fi"},"message":"ALSA: usb-audio: Add sample rate inquiry quirk for AudioQuest DragonFly\n\n[ Upstream commit 12a6116e66695a728bcb9616416c508ce9c051a1 ]\n\nAvoid getting sample rate on AudioQuest DragonFly as it is unsupported\nand causes noisy \"cannot get freq at ep 0x1\" messages when playback\nstarts.\n\nSigned-off-by: Anssi Hannula <anssi.hannula@iki.fi>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/b672486754838d943a7a2769ed6e55ef169dcd12"},{"sha":"bdd3700374c2a7281cd54bb24680bdea2372edc4","author":{"name":"Takashi Iwai","email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de"},"message":"ALSA: usb-audio: Add a sample rate quirk for Phoenix Audio TMX320\n\n[ Upstream commit f03b24a851d32ca85dacab01785b24a7ee717d37 ]\n\nPhoenix Audio TMX320 gives the similar error when the sample rate is\nasked:\n  usb 2-1.3: 2:1: cannot get freq at ep 0x85\n  usb 2-1.3: 1:1: cannot get freq at ep 0x2\n  ....\n\nAdd the corresponding USB-device ID (1de7:0014) to\nsnd_usb_get_sample_rate_quirk() list.\n\nBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=110221\nCc: <stable@vger.kernel.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/bdd3700374c2a7281cd54bb24680bdea2372edc4"},{"sha":"1491937f7897c398121ac284a3bc17203c992a12","author":{"name":"Boris Ostrovsky","email":"b41c17b861974b03cec38e3ec2992769b9bfae55@oracle.com"},"message":"xen/events: Mask a moving irq\n\n[ Upstream commit ff1e22e7a638a0782f54f81a6c9cb139aca2da35 ]\n\nMoving an unmasked irq may result in irq handler being invoked on both\nsource and target CPUs.\n\nWith 2-level this can happen as follows:\n\nOn source CPU:\n        evtchn_2l_handle_events() ->\n            generic_handle_irq() ->\n                handle_edge_irq() ->\n                   eoi_pirq():\n                       irq_move_irq(data);\n\n                       /***** WE ARE HERE *****/\n\n                       if (VALID_EVTCHN(evtchn))\n                           clear_evtchn(evtchn);\n\nIf at this moment target processor is handling an unrelated event in\nevtchn_2l_handle_events()'s loop it may pick up our event since target's\ncpu_evtchn_mask claims that this event belongs to it *and* the event is\nunmasked and still pending. At the same time, source CPU will continue\nexecuting its own handle_edge_irq().\n\nWith FIFO interrupt the scenario is similar: irq_move_irq() may result\nin a EVTCHNOP_unmask hypercall which, in turn, may make the event\npending on the target CPU.\n\nWe can avoid this situation by moving and clearing the event while\nkeeping event masked.\n\nSigned-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>\nCc: stable@vger.kernel.org\nSigned-off-by: David Vrabel <david.vrabel@citrix.com>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/1491937f7897c398121ac284a3bc17203c992a12"},{"sha":"ccf7f20931bd04cd419d178d4f3a7c059690a924","author":{"name":"Yoshihiro Shimoda","email":"de6fb888308c49c20838826baf4e7cc406af80ff@renesas.com"},"message":"usb: renesas_usbhs: fix spinlock suspected in a gadget complete function\n\n[ Upstream commit 00f30d29b497577954b20237b405e9d22b5286c2 ]\n\nAccording to the gadget.h, a \"complete\" function will always be called\nwith interrupts disabled. However, sometimes usbhsg_queue_pop() function\nis called with interrupts enabled. So, this function should be held by\nusbhs_lock() to disable interruption. Also, this driver has to call\nspin_unlock() to avoid spinlock recursion by this driver before calling\nusb_gadget_giveback_request().\nOtherwise, there is possible to cause a spinlock suspected in a gadget\ncomplete function.\n\nSigned-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>\nSigned-off-by: Felipe Balbi <balbi@ti.com>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/ccf7f20931bd04cd419d178d4f3a7c059690a924"},{"sha":"09cbe7dba48375f1638d04fe85224c15c178a197","author":{"name":"Yoshihiro Shimoda","email":"de6fb888308c49c20838826baf4e7cc406af80ff@renesas.com"},"message":"usb: renesas_usbhs: fix to avoid using a disabled ep in usbhsg_queue_done()\n\n[ Upstream commit 4fccb0767fdbdb781a9c5b5c15ee7b219443c89d ]\n\nThis patch fixes an issue that usbhsg_queue_done() may cause kernel\npanic when dma callback is running and usb_ep_disable() is called\nby interrupt handler. (Especially, we can reproduce this issue using\ng_audio with usb-dmac driver.)\n\nFor example of a flow:\n usbhsf_dma_complete (on tasklet)\n  --> usbhsf_pkt_handler (on tasklet)\n   --> usbhsg_queue_done (on tasklet)\n    *** interrupt happened and usb_ep_disable() is called ***\n    --> usbhsg_queue_pop (on tasklet)\n     Then, oops happened.\n\nFixes: e73a989 (\"usb: renesas_usbhs: add DMAEngine support\")\nCc: <stable@vger.kernel.org> # v3.1+\nSigned-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/09cbe7dba48375f1638d04fe85224c15c178a197"},{"sha":"677fa15cd6d5b0843e7b9c58409f67d656b1ec2f","author":{"name":"Joe Perches","email":"16a9a54ddf4259952e3c118c763138e83693d7fd@perches.com"},"message":"compiler-gcc: integrate the various compiler-gcc[345].h files\n\n[ Upstream commit f320793e52aee78f0fbb8bcaf10e6614d2e67bfc ]\n\n[ Upstream commit cb984d101b30eb7478d32df56a0023e4603cba7f ]\n\nAs gcc major version numbers are going to advance rather rapidly in the\nfuture, there's no real value in separate files for each compiler\nversion.\n\nDeduplicate some of the macros #defined in each file too.\n\nNeaten comments using normal kernel commenting style.\n\nSigned-off-by: Joe Perches <joe@perches.com>\nCc: Andi Kleen <andi@firstfloor.org>\nCc: Michal Marek <mmarek@suse.cz>\nCc: Segher Boessenkool <segher@kernel.crashing.org>\nCc: Sasha Levin <levinsasha928@gmail.com>\nCc: Anton Blanchard <anton@samba.org>\nCc: Alan Modra <amodra@gmail.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/677fa15cd6d5b0843e7b9c58409f67d656b1ec2f"},{"sha":"7c134b078cb5738f10d1d1533ab1895864b958f9","author":{"name":"Paolo Bonzini","email":"69d3ebcf5ee4e7f05a50dc23cd96655b730804b4@redhat.com"},"message":"compiler-gcc: disable -ftracer for __noclone functions\n\n[ Upstream commit 95272c29378ee7dc15f43fa2758cb28a5913a06d ]\n\n-ftracer can duplicate asm blocks causing compilation to fail in\nnoclone functions.  For example, KVM declares a global variable\nin an asm like\n\n    asm(\"2: ... \\n\n         .pushsection data \\n\n         .global vmx_return \\n\n         vmx_return: .long 2b\");\n\nand -ftracer causes a double declaration.\n\nCc: Andrew Morton <akpm@linux-foundation.org>\nCc: Michal Marek <mmarek@suse.cz>\nCc: stable@vger.kernel.org\nCc: kvm@vger.kernel.org\nReported-by: Linda Walsh <lkml@tlinx.org>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":false,"url":"https://api.github.com/repos/AyaanSaleemMalik/kernel_xiaomi_oxygen/commits/7c134b078cb5738f10d1d1533ab1895864b958f9"}]}
{"actor":{"display_login":"AyaanSaleemMalik"}}