{"push_id":1100480982,"size":178,"distinct_size":178,"ref":"refs/heads/6.0.0-kr01","head":"b5f0c88ce4ba9a36eea3ec172f8c8b02eb76d085","before":"e5ee49c90ddd103861c7c8c0baf9d5030e4ebd0a","commits":[{"sha":"15289cf345730d07078ce629ac01336401d46c49","author":{"email":"8c17e024526dd808f510f3b63b496656e96cd4f2@twitter.com","name":"Masoud Sharbiani"},"message":"x86/reboot: Add quirk to make Dell C6100 use reboot=pci automatically\n\ncommit 4f0acd31c31f03ba42494c8baf6c0465150e2621 upstream.\n\nDell PowerEdge C6100 machines fail to completely reboot about 20% of the time.\n\nSigned-off-by: Masoud Sharbiani <msharbiani@twitter.com>\nSigned-off-by: Vinson Lee <vlee@twitter.com>\nCc: Robin Holt <holt@sgi.com>\nCc: Russell King <rmk+kernel@arm.linux.org.uk>\nCc: Guan Xuetao <gxt@mprc.pku.edu.cn>\nLink: http://lkml.kernel.org/r/1379717947-18042-1-git-send-email-vlee@freedesktop.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/15289cf345730d07078ce629ac01336401d46c49"},{"sha":"5a7a56d556628fda4738d762fb25f1c5caa1bc17","author":{"email":"94755a79aca753e683bb6d0e796d473b797056eb@redhat.com","name":"Josh Boyer"},"message":"x86, efi: Don't map Boot Services on i386\n\ncommit 700870119f49084da004ab588ea2b799689efaf7 upstream.\n\nAdd patch to fix 32bit EFI service mapping (rhbz 726701)\n\nMultiple people are reporting hitting the following WARNING on i386,\n\n  WARNING: at arch/x86/mm/ioremap.c:102 __ioremap_caller+0x3d3/0x440()\n  Modules linked in:\n  Pid: 0, comm: swapper Not tainted 3.9.0-rc7+ #95\n  Call Trace:\n   [<c102b6af>] warn_slowpath_common+0x5f/0x80\n   [<c1023fb3>] ? __ioremap_caller+0x3d3/0x440\n   [<c1023fb3>] ? __ioremap_caller+0x3d3/0x440\n   [<c102b6ed>] warn_slowpath_null+0x1d/0x20\n   [<c1023fb3>] __ioremap_caller+0x3d3/0x440\n   [<c106007b>] ? get_usage_chars+0xfb/0x110\n   [<c102d937>] ? vprintk_emit+0x147/0x480\n   [<c1418593>] ? efi_enter_virtual_mode+0x1e4/0x3de\n   [<c102406a>] ioremap_cache+0x1a/0x20\n   [<c1418593>] ? efi_enter_virtual_mode+0x1e4/0x3de\n   [<c1418593>] efi_enter_virtual_mode+0x1e4/0x3de\n   [<c1407984>] start_kernel+0x286/0x2f4\n   [<c1407535>] ? repair_env_string+0x51/0x51\n   [<c1407362>] i386_start_kernel+0x12c/0x12f\n\nDue to the workaround described in commit 916f676f8 (\"x86, efi: Retain\nboot service code until after switching to virtual mode\") EFI Boot\nService regions are mapped for a period during boot. Unfortunately, with\nthe limited size of the i386 direct kernel map it's possible that some\nof the Boot Service regions will not be directly accessible, which\ncauses them to be ioremap()'d, triggering the above warning as the\nregions are marked as E820_RAM in the e820 memmap.\n\nThere are currently only two situations where we need to map EFI Boot\nService regions,\n\n  1. To workaround the firmware bug described in 916f676f8\n  2. To access the ACPI BGRT image\n\nbut since we haven't seen an i386 implementation that requires either,\nthis simple fix should suffice for now.\n\n[ Added to changelog - Matt ]\n\nReported-by: Bryan O'Donoghue <bryan.odonoghue.lkml@nexus-software.ie>\nAcked-by: Tom Zanussi <tom.zanussi@intel.com>\nAcked-by: Darren Hart <dvhart@linux.intel.com>\nCc: Josh Triplett <josh@joshtriplett.org>\nCc: Matthew Garrett <mjg59@srcf.ucam.org>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Josh Boyer <jwboyer@redhat.com>\nSigned-off-by: Matt Fleming <matt.fleming@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/5a7a56d556628fda4738d762fb25f1c5caa1bc17"},{"sha":"f4358d81f28e7a9adcbad8d3809af040083ec32b","author":{"email":"123fd39c698f702285d09eaebae85efdff081c95@gmail.com","name":"Malcolm Priestley"},"message":"staging: vt6656: [BUG] main_usb.c oops on device_close move flag earlier.\n\ncommit e3eb270fab7734427dd8171a93e4946fe28674bc upstream.\n\nThe vt6656 is prone to resetting on the usb bus.\n\nIt seems there is a race condition and wpa supplicant is\ntrying to open the device via iw_handlers before its actually\nclosed at a stage that the buffers are being removed.\n\nThe device is longer considered open when the\nbuffers are being removed. So move ~DEVICE_FLAGS_OPENED\nflag to before freeing the device buffers.\n\nSigned-off-by: Malcolm Priestley <tvboxspy@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/f4358d81f28e7a9adcbad8d3809af040083ec32b"},{"sha":"a11279370f1a02a4aeab13db509df120dbd19791","author":{"email":"2d4473c5e67eb83655334d4e9a7757f781607241@linux.intel.com","name":"Mathias Nyman"},"message":"xhci: Ensure a command structure points to the correct trb on the command ring\n\ncommit ec7e43e2d98173483866fe2e4e690143626b659c upstream.\n\nIf a command on the command ring needs to be cancelled before it is handled\nit can be turned to a no-op operation when the ring is stopped.\nWe want to store the command ring enqueue pointer in the command structure\nwhen the command in enqueued for the cancellation case.\n\nSome commands used to store the command ring dequeue pointers instead of enqueue\n(these often worked because enqueue happends to equal dequeue quite often)\n\nOther commands correctly used the enqueue pointer but did not check if it pointed\nto a valid trb or a link trb, this caused for example stop endpoint command to timeout in\nxhci_stop_device() in about 2% of suspend/resume cases.\n\nThis should also solve some weird behavior happening in command cancellation cases.\n\nThis patch is based on a patch submitted by Sarah Sharp to linux-usb, but\nthen forgotten:\n    http://marc.info/?l=linux-usb&m=136269803207465&w=2\n\nThis patch should be backported to kernels as old as 3.7, that contain\nthe commit b92cc66c047ff7cf587b318fe377061a353c120f \"xHCI: add aborting\ncommand ring function\"\n\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/a11279370f1a02a4aeab13db509df120dbd19791"},{"sha":"d2b56ea6e3b043fb120d4e9c2afe3812c08d49c5","author":{"email":"2d4473c5e67eb83655334d4e9a7757f781607241@linux.intel.com","name":"Mathias Nyman"},"message":"xhci: Fix oops happening after address device timeout\n\ncommit 284d20552461466b04d6bfeafeb1c47a8891b591 upstream.\n\nWhen a command times out, the command ring is first aborted,\nand then stopped. If the command ring is empty when it is stopped\nthe stop event will point to next command which is not yet set.\nxHCI tries to handle this next event often causing an oops.\n\nDon't handle command completion events on stopped cmd ring if ring is\nempty.\n\nThis patch should be backported to kernels as old as 3.7, that contain\nthe commit b92cc66c047ff7cf587b318fe377061a353c120f \"xHCI: add aborting\ncommand ring function\"\n\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nReported-by: Giovanni <giovanni.nervi@yahoo.com>\nSigned-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/d2b56ea6e3b043fb120d4e9c2afe3812c08d49c5"},{"sha":"12d51d8d2d88e73e3399f9d0c9cb2e9f07acd044","author":{"email":"abf3b3fdd2728b2750e2eb0b1548a8aeccb32686@web.de","name":"Florian Wolter"},"message":"xhci: Fix race between ep halt and URB cancellation\n\ncommit 526867c3ca0caa2e3e846cb993b0f961c33c2abb upstream.\n\nThe halted state of a endpoint cannot be cleared over CLEAR_HALT from a\nuser process, because the stopped_td variable was overwritten in the\nhandle_stopped_endpoint() function. So the xhci_endpoint_reset() function will\nrefuse the reset and communication with device can not run over this endpoint.\nhttps://bugzilla.kernel.org/show_bug.cgi?id=60699\n\nSigned-off-by: Florian Wolter <wolly84@web.de>\nSigned-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>\nCc: Jonghwan Choi <jhbird.choi@samsung.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/12d51d8d2d88e73e3399f9d0c9cb2e9f07acd044"},{"sha":"a4b27d6d42735c908933935da2e6c4e771983e4b","author":{"email":"bb87b47479d83cec3c76132206933257ded727b2@garloff.de","name":"Kurt Garloff"},"message":"usb/core/devio.c: Don't reject control message to endpoint with wrong direction bit\n\ncommit 831abf76643555a99b80a3b54adfa7e4fa0a3259 upstream.\n\nTrying to read data from the Pegasus Technologies NoteTaker (0e20:0101)\n[1] with the Windows App (EasyNote) works natively but fails when\nWindows is running under KVM (and the USB device handed to KVM).\n\nThe reason is a USB control message\n usb 4-2.2: control urb: bRequestType=22 bRequest=09 wValue=0200 wIndex=0001 wLength=0008\nThis goes to endpoint address 0x01 (wIndex); however, endpoint address\n0x01 does not exist. There is an endpoint 0x81 though (same number,\nbut other direction); the app may have meant that endpoint instead.\n\nThe kernel thus rejects the IO and thus we see the failure.\n\nApparently, Linux is more strict here than Windows ... we can't change\nthe Win app easily, so that's a problem.\n\nIt seems that the Win app/driver is buggy here and the driver does not\nbehave fully according to the USB HID class spec that it claims to\nbelong to.  The device seems to happily deal with that though (and\nseems to not really care about this value much).\n\nSo the question is whether the Linux kernel should filter here.\nRejecting has the risk that somewhat non-compliant userspace apps/\ndrivers (most likely in a virtual machine) are prevented from working.\nNot rejecting has the risk of confusing an overly sensitive device with\nsuch a transfer. Given the fact that Windows does not filter it makes\nthis risk rather small though.\n\nThe patch makes the kernel more tolerant: If the endpoint address in\nwIndex does not exist, but an endpoint with toggled direction bit does,\nit will let the transfer through. (It does NOT change the message.)\n\nWith attached patch, the app in Windows in KVM works.\n usb 4-2.2: check_ctrlrecip: process 13073 (qemu-kvm) requesting ep 01 but needs 81\n\nI suspect this will mostly affect apps in virtual environments; as on\nLinux the apps would have been adapted to the stricter handling of the\nkernel. I have done that for mine[2].\n\n[1] http://www.pegatech.com/\n[2] https://sourceforge.net/projects/notetakerpen/\n\nSigned-off-by: Kurt Garloff <kurt@garloff.de>\nAcked-by: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/a4b27d6d42735c908933935da2e6c4e771983e4b"},{"sha":"3a6458ab1e73e701844e758b8a4323c2bf83c5bb","author":{"email":"52f8f9962b7f38d8269c63c0859d68147c8d10f0@redhat.com","name":"Mikulas Patocka"},"message":"dm snapshot: workaround for a false positive lockdep warning\n\ncommit 5ea330a75bd86b2b2a01d7b85c516983238306fb upstream.\n\nThe kernel reports a lockdep warning if a snapshot is invalidated because\nit runs out of space.\n\nThe lockdep warning was triggered by commit 0976dfc1d0cd80a4e9dfaf87bd87\n(\"workqueue: Catch more locking problems with flush_work()\") in v3.5.\n\nThe warning is false positive.  The real cause for the warning is that\nthe lockdep engine treats different instances of md->lock as a single\nlock.\n\nThis patch is a workaround - we use flush_workqueue instead of flush_work.\nThis code path is not performance sensitive (it is called only on\ninitialization or invalidation), thus it doesn't matter that we flush the\nwhole workqueue.\n\nThe real fix for the problem would be to teach the lockdep engine to treat\ndifferent instances of md->lock as separate locks.\n\nSigned-off-by: Mikulas Patocka <mpatocka@redhat.com>\nAcked-by: Alasdair G Kergon <agk@redhat.com>\nSigned-off-by: Mike Snitzer <snitzer@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/3a6458ab1e73e701844e758b8a4323c2bf83c5bb"},{"sha":"dc738f77676df71c0b9b8f44c586238e3e20abed","author":{"email":"52f8f9962b7f38d8269c63c0859d68147c8d10f0@redhat.com","name":"Mikulas Patocka"},"message":"dm-snapshot: fix performance degradation due to small hash size\n\ncommit 60e356f381954d79088d0455e357db48cfdd6857 upstream.\n\nLVM2, since version 2.02.96, creates origin with zero size, then loads\nthe snapshot driver and then loads the origin.  Consequently, the\nsnapshot driver sees the origin size zero and sets the hash size to the\nlower bound 64.  Such small hash table causes performance degradation.\n\nThis patch changes it so that the hash size is determined by the size of\nsnapshot volume, not minimum of origin and snapshot size.  It doesn't\nmake sense to set the snapshot size significantly larger than the origin\nsize, so we do not need to take origin size into account when\ncalculating the hash size.\n\nSigned-off-by: Mikulas Patocka <mpatocka@redhat.com>\nSigned-off-by: Mike Snitzer <snitzer@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/dc738f77676df71c0b9b8f44c586238e3e20abed"},{"sha":"4152884329db073419ca101383fd1a200e8d1120","author":{"email":"ba783f3beccaedfda693f41a15407d612a629408@intel.com","name":"Jani Nikula"},"message":"drm/i915/dp: increase i2c-over-aux retry interval on AUX DEFER\n\ncommit 8d16f258217f2f583af1fd57c5144aa4bbe73e48 upstream.\n\nThere is no clear cut rules or specs for the retry interval, as there\nare many factors that affect overall response time. Increase the\ninterval, and even more so on branch devices which may have limited i2c\nbit rates.\n\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>\nReference: https://bugs.freedesktop.org/show_bug.cgi?id=60263\nTested-by: Nicolas Suzor <nic@suzor.com>\nReviewed-by: Todd Previte <tprevite@gmail.com>\nSigned-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/4152884329db073419ca101383fd1a200e8d1120"},{"sha":"601c736001142a87dc3d8552424b3f704828629a","author":{"email":"08dc22c6156113f2deff178e35e3ed9b24d6af9e@amd.com","name":"Alex Deucher"},"message":"drm/radeon: disable tests/benchmarks if accel is disabled\n\ncommit 4a1132a023eb48cf10522d84c5908d43b612c041 upstream.\n\nThe tests are only usable if the acceleration engines have\nbeen successfully initialized.\n\nBased on an initial patch from: Alex Ivanov <gnidorah@p0n4ik.tk>\n\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/601c736001142a87dc3d8552424b3f704828629a"},{"sha":"ac6acddba7cf5df7b898766c1a17e14ec4ef51ba","author":{"email":"b7088a9c70345a9ab94cacab3cc3888d0a7dc884@euromail.se","name":"Henrik Rydberg"},"message":"hwmon: (applesmc) Check key count before proceeding\n\ncommit 5f4513864304672e6ea9eac60583eeac32e679f2 upstream.\n\nAfter reports from Chris and Josh Boyer of a rare crash in applesmc,\nGuenter pointed at the initialization problem fixed below. The patch\nhas not been verified to fix the crash, but should be applied\nregardless.\n\nReported-by: <jwboyer@fedoraproject.org>\nSuggested-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Henrik Rydberg <rydberg@euromail.se>\nSigned-off-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/ac6acddba7cf5df7b898766c1a17e14ec4ef51ba"},{"sha":"b3bf457d73160d9d8c94e6be80c64a7beef0e0a1","author":{"email":"1c687ae09fa7f11acd34075a0ae6b39df2be9341@linux.intel.com","name":"Liam Girdwood"},"message":"ALSA: compress: Fix compress device unregister.\n\ncommit 4028b6c4c03f213260e9290ff3a6b5439aad07ce upstream.\n\nsnd_unregister_device() should return the device type and not stream\ndirection.\n\nSigned-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>\nAcked-by: Vinod Koul <vinod.koul@intel.com>\nTested-by: Vinod Koul <vinod.koul@intel.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/b3bf457d73160d9d8c94e6be80c64a7beef0e0a1"},{"sha":"3c8312e4864be20c2e272e14ced835776fa033d5","author":{"email":"d8cd2994e15bc61ddb2b113030bda55eebc3a0fe@google.com","name":"David Rientjes"},"message":"mm, memcg: give exiting processes access to memory reserves\n\ncommit 465adcf1ea7b2e49b2e0899366624f5532b64012\n\nA memcg may livelock when oom if the process that grabs the hierarchy's\noom lock is never the first process with PF_EXITING set in the memcg's\ntask iteration.\n\nThe oom killer, both global and memcg, will defer if it finds an\neligible process that is in the process of exiting and it is not being\nptraced.  The idea is to allow it to exit without using memory reserves\nbefore needlessly killing another process.\n\nThis normally works fine except in the memcg case with a large number of\nthreads attached to the oom memcg.  In this case, the memcg oom killer\nonly gets called for the process that grabs the hierarchy's oom lock;\nall others end up blocked on the memcg's oom waitqueue.  Thus, if the\nprocess that grabs the hierarchy's oom lock is never the first\nPF_EXITING process in the memcg's task iteration, the oom killer is\nconstantly deferred without anything making progress.\n\nThe fix is to give PF_EXITING processes access to memory reserves so\nthat we've marked them as oom killed without any iteration.  This allows\n__mem_cgroup_try_charge() to succeed so that the process may exit.  This\nmakes the memcg oom killer exemption for TIF_MEMDIE tasks, now\nimmediately granted for processes with pending SIGKILLs and those in the\nexit path, to be equivalent to what is done for the global oom killer.\n\nSigned-off-by: David Rientjes <rientjes@google.com>\nAcked-by: Michal Hocko <mhocko@suse.cz>\nAcked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\nAcked-by: Johannes Weiner <hannes@cmpxchg.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n[Qiang: backported to 3.4:\n - move the changes from memcontrol.c to oom_kill.c]\nSigned-off-by: Qiang Huang <h.huangqiang@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/3c8312e4864be20c2e272e14ced835776fa033d5"},{"sha":"ffc298f6967545e732776f2768a7785df34cc6fb","author":{"email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org","name":"Kees Cook"},"message":"HID: LG: validate HID output report details\n\ncommit 0fb6bd06e06792469acc15bbe427361b56ada528 upstream.\n\nA HID device could send a malicious output report that would cause the\nlg, lg3, and lg4 HID drivers to write beyond the output report allocation\nduring an event, causing a heap overflow:\n\n[  325.245240] usb 1-1: New USB device found, idVendor=046d, idProduct=c287\n...\n[  414.518960] BUG kmalloc-4096 (Not tainted): Redzone overwritten\n\nAdditionally, while lg2 did correctly validate the report details, it was\ncleaned up and shortened.\n\nCVE-2013-2893\n\nSigned-off-by: Kees Cook <keescook@chromium.org>\nReviewed-by: Benjamin Tissoires <benjamin.tissoires@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/Benowit/android_kernel_motorola_msm8974/commits/ffc298f6967545e732776f2768a7785df34cc6fb"},{"sha":"00e38825abd02770b378d3db8a9dda614765344b","author":{"email":"4645f7897fd33786a2ee1264d590b3c400559d85@linuxfoundation.org","name":"Greg Kroah-Hartman"},"message":"Linux 3.4.65","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/00e38825abd02770b378d3db8a9dda614765344b"},{"sha":"9147eef72639f064aecdb745554dd150b0f197eb","author":{"email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com","name":"Dan Carpenter"},"message":"cpqarray: fix info leak in ida_locked_ioctl()\n\ncommit 627aad1c01da6f881e7f98d71fd928ca0c316b1a upstream.\n\nThe pciinfo struct has a two byte hole after ->dev_fn so stack\ninformation could be leaked to the user.\n\nThis was assigned CVE-2013-2147.\n\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nAcked-by: Mike Miller <mike.miller@hp.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/9147eef72639f064aecdb745554dd150b0f197eb"},{"sha":"962ade4bd4188e3a76d4a3e005c86cd105b0188f","author":{"email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com","name":"Dan Carpenter"},"message":"cciss: fix info leak in cciss_ioctl32_passthru()\n\ncommit 58f09e00ae095e46ef9edfcf3a5fd9ccdfad065e upstream.\n\nThe arg64 struct has a hole after ->buf_size which isn't cleared.  Or if\nany of the calls to copy_from_user() fail then that would cause an\ninformation leak as well.\n\nThis was assigned CVE-2013-2147.\n\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nAcked-by: Mike Miller <mike.miller@hp.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/Benowit/android_kernel_motorola_msm8974/commits/962ade4bd4188e3a76d4a3e005c86cd105b0188f"},{"sha":"5234d06949fa843098b29bffba499207c5cc4be4","author":{"email":"93199f51fb74af07aaea9f00c34bceab8fd209ab@freescale.com","name":"Claudiu Manoil"},"message":"gianfar: Change default HW Tx queue scheduling mode\n\ncommit b98b8babd6e3370fadb7c6eaacb00eb2f6344a6c upstream.\n\nThis is primarily to address transmission timeout occurrences, when\nmultiple H/W Tx queues are being used concurrently. Because in\nthe priority scheduling mode the controller does not service the\nTx queues equally (but in ascending index order), Tx timeouts are\nbeing triggered rightaway for a basic test with multiple simultaneous\nconnections like:\niperf -c <server_ip> -n 100M -P 8\n\nresulting in kernel trace:\nNETDEV WATCHDOG: eth1 (fsl-gianfar): transmit queue <X> timed out\n------------[ cut here ]------------\nWARNING: at net/sched/sch_generic.c:255\n...\nand controller reset during intense traffic, and possibly further\ncomplications.\n\nThis patch changes the default H/W Tx scheduling setting (TXSCHED)\nfor multi-queue devices, from priority scheduling mode to a weighted\nround robin mode with equal weights for all H/W Tx queues, and\naddresses the issue above.\n\nSigned-off-by: Claudiu Manoil <claudiu.manoil@freescale.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/Benowit/android_kernel_motorola_msm8974/commits/5234d06949fa843098b29bffba499207c5cc4be4"},{"sha":"735fce9f255db1a6c8eb2f6187713a01ec1666f9","author":{"email":"d5ec0d24602845f6f4b6a35ef729998d1fba5507@redhat.com","name":"Dave Jones"},"message":"caif: Add missing braces to multiline if in cfctrl_linkup_request\n\n[ Upstream commit 0c1db731bfcf3a9fd6c58132134f8b0f423552f0 ]\n\nThe indentation here implies this was meant to be a multi-line if.\n\nIntroduced several years back in commit c85c2951d4da1236e32f1858db418221e624aba5\n(\"caif: Handle dev_queue_xmit errors.\")\n\nSigned-off-by: Dave Jones <davej@fedoraproject.org>\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/Benowit/android_kernel_motorola_msm8974/commits/735fce9f255db1a6c8eb2f6187713a01ec1666f9"}]}