{"push_id":843863408,"size":1000,"distinct_size":2498,"ref":"refs/heads/mkl-mr1","head":"c61d97ddcd38e29d647fcc12e1ebf5f1a7c80520","before":"68b87fd081bb8e77fa10a8004116df0f558ac4d2","commits":[{"sha":"a8bd97be9160ed1087d5f53b157315de126a4f75","author":{"email":"8d5319aa8b1ac990c652f52775783ffb96f7cbb5@redhat.com","name":"Myron Stowe"},"message":"PCI: Restore detection of read-only BARs\n\ncommit 36e8164882ca6d3c41cb91e6f09a3ed236841f80 upstream.\n\nCommit 6ac665c63dca (\"PCI: rewrite PCI BAR reading code\") masked off\nlow-order bits from 'l', but not from 'sz'.  Both are passed to pci_size(),\nwhich compares 'base == maxbase' to check for read-only BARs.  The masking\nof 'l' means that comparison will never be 'true', so the check for\nread-only BARs no longer works.\n\nResolve this by also masking off the low-order bits of 'sz' before passing\nit into pci_size() as 'maxbase'.  With this change, pci_size() will once\nagain catch the problems that have been encountered to date:\n\n  - AGP aperture BAR of AMD-7xx host bridges: if the AGP window is\n    disabled, this BAR is read-only and read as 0x00000008 [1]\n\n  - BARs 0-4 of ALi IDE controllers can be non-zero and read-only [1]\n\n  - Intel Sandy Bridge - Thermal Management Controller [8086:0103];\n    BAR 0 returning 0xfed98004 [2]\n\n  - Intel Xeon E5 v3/Core i7 Power Control Unit [8086:2fc0];\n    Bar 0 returning 0x00001a [3]\n\nLink: [1] https://git.kernel.org/cgit/linux/kernel/git/tglx/history.git/commit/drivers/pci/probe.c?id=1307ef6621991f1c4bc3cec1b5a4ebd6fd3d66b9 (\"PCI: probing read-only BARs\" (pre-git))\nLink: [2] https://bugzilla.kernel.org/show_bug.cgi?id=43331\nLink: [3] https://bugzilla.kernel.org/show_bug.cgi?id=85991\nReported-by: William Unruh <unruh@physics.ubc.ca>\nReported-by: Martin Lucina <martin@lucina.net>\nSigned-off-by: Myron Stowe <myron.stowe@redhat.com>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nCC: Matthew Wilcox <willy@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_motorola_apq8084/commits/a8bd97be9160ed1087d5f53b157315de126a4f75"},{"sha":"85505977007d4443aedb292474318e6d8b9f2e24","author":{"email":"35cb649d4681a38990d5580fac6cd08443a7331e@gmail.com","name":"Rob Herring"},"message":"pstore-ram: Fix hangs by using write-combine mappings\n\ncommit 7ae9cb81933515dc7db1aa3c47ef7653717e3090 upstream.\n\nCurrently trying to use pstore on at least ARMs can hang as we're\nmapping the peristent RAM with pgprot_noncached().\n\nOn ARMs, pgprot_noncached() will actually make the memory strongly\nordered, and as the atomic operations pstore uses are implementation\ndefined for strongly ordered memory, they may not work. So basically\natomic operations have undefined behavior on ARM for device or strongly\nordered memory types.\n\nLet's fix the issue by using write-combine variants for mappings. This\ncorresponds to normal, non-cacheable memory on ARM. For many other\narchitectures, this change does not change the mapping type as by\ndefault we have:\n\n#define pgprot_writecombine pgprot_noncached\n\nThe reason why pgprot_noncached() was originaly used for pstore\nis because Colin Cross <ccross@android.com> had observed lost\ndebug prints right before a device hanging write operation on some\nsystems. For the platforms supporting pgprot_noncached(), we can\nadd a an optional configuration option to support that. But let's\nget pstore working first before adding new features.\n\nCc: Arnd Bergmann <arnd@arndb.de>\nCc: Anton Vorontsov <cbouatmailru@gmail.com>\nCc: Colin Cross <ccross@android.com>\nCc: Olof Johansson <olof@lixom.net>\nCc: linux-kernel@vger.kernel.org\nAcked-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: Rob Herring <rob.herring@calxeda.com>\n[tony@atomide.com: updated description]\nSigned-off-by: Tony Lindgren <tony@atomide.com>\nSigned-off-by: Tony Luck <tony.luck@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_motorola_apq8084/commits/85505977007d4443aedb292474318e6d8b9f2e24"},{"sha":"63eb09ee2b450634f3e7f3f21ed9b6d9b9a04888","author":{"email":"1001e8702733cced254345e193c88aaa47a4f5de@atomide.com","name":"Tony Lindgren"},"message":"pstore-ram: Allow optional mapping with pgprot_noncached\n\ncommit 027bc8b08242c59e19356b4b2c189f2d849ab660 upstream.\n\nOn some ARMs the memory can be mapped pgprot_noncached() and still\nbe working for atomic operations. As pointed out by Colin Cross\n<ccross@android.com>, in some cases you do want to use\npgprot_noncached() if the SoC supports it to see a debug printk\njust before a write hanging the system.\n\nOn ARMs, the atomic operations on strongly ordered memory are\nimplementation defined. So let's provide an optional kernel parameter\nfor configuring pgprot_noncached(), and use pgprot_writecombine() by\ndefault.\n\nCc: Arnd Bergmann <arnd@arndb.de>\nCc: Rob Herring <robherring2@gmail.com>\nCc: Randy Dunlap <rdunlap@infradead.org>\nCc: Anton Vorontsov <anton@enomsg.org>\nCc: Colin Cross <ccross@android.com>\nCc: Olof Johansson <olof@lixom.net>\nCc: Russell King <linux@arm.linux.org.uk>\nAcked-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: Tony Lindgren <tony@atomide.com>\nSigned-off-by: Tony Luck <tony.luck@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_motorola_apq8084/commits/63eb09ee2b450634f3e7f3f21ed9b6d9b9a04888"},{"sha":"8d03064fcadff5f7923c05951457226bfaf04415","author":{"email":"320bca71fc381a4a025636043ca86e734e31cf8b@nod.at","name":"Richard Weinberger"},"message":"UBI: Fix invalid vfree()\n\ncommit f38aed975c0c3645bbdfc5ebe35726e64caaf588 upstream.\n\nThe logic of vfree()'ing vol->upd_buf is tied to vol->updating.\nIn ubi_start_update() vol->updating is set long before vmalloc()'ing\nvol->upd_buf. If we encounter a write failure in ubi_start_update()\nbefore vmalloc() the UBI device release function will try to vfree()\nvol->upd_buf because vol->updating is set.\nFix this by allocating vol->upd_buf directly after setting vol->updating.\n\nFixes:\n[   31.559338] UBI warning: vol_cdev_release: update of volume 2 not finished, volume is damaged\n[   31.559340] ------------[ cut here ]------------\n[   31.559343] WARNING: CPU: 1 PID: 2747 at mm/vmalloc.c:1446 __vunmap+0xe3/0x110()\n[   31.559344] Trying to vfree() nonexistent vm area (ffffc90001f2b000)\n[   31.559345] Modules linked in:\n[   31.565620]  0000000000000bba ffff88002a0cbdb0 ffffffff818f0497 ffff88003b9ba148\n[   31.566347]  ffff88002a0cbde0 ffffffff8156f515 ffff88003b9ba148 0000000000000bba\n[   31.567073]  0000000000000000 0000000000000000 ffff88002a0cbe88 ffffffff8156c10a\n[   31.567793] Call Trace:\n[   31.568034]  [<ffffffff818f0497>] dump_stack+0x4e/0x7a\n[   31.568510]  [<ffffffff8156f515>] ubi_io_write_vid_hdr+0x155/0x160\n[   31.569084]  [<ffffffff8156c10a>] ubi_eba_write_leb+0x23a/0x870\n[   31.569628]  [<ffffffff81569b36>] vol_cdev_write+0x226/0x380\n[   31.570155]  [<ffffffff81179265>] vfs_write+0xb5/0x1f0\n[   31.570627]  [<ffffffff81179f8a>] SyS_pwrite64+0x6a/0xa0\n[   31.571123]  [<ffffffff818fde12>] system_call_fastpath+0x16/0x1b\n\nSigned-off-by: Richard Weinberger <richard@nod.at>\nSigned-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_motorola_apq8084/commits/8d03064fcadff5f7923c05951457226bfaf04415"},{"sha":"aa5b3cd24f6e4743b378f9fb8a9218170e51ffb5","author":{"email":"320bca71fc381a4a025636043ca86e734e31cf8b@nod.at","name":"Richard Weinberger"},"message":"UBI: Fix double free after do_sync_erase()\n\ncommit aa5ad3b6eb8feb2399a5d26c8fb0060561bb9534 upstream.\n\nIf the erase worker is unable to erase a PEB it will\nfree the ubi_wl_entry itself.\nThe failing ubi_wl_entry must not free()'d again after\ndo_sync_erase() returns.\n\nSigned-off-by: Richard Weinberger <richard@nod.at>\nSigned-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_motorola_apq8084/commits/aa5b3cd24f6e4743b378f9fb8a9218170e51ffb5"},{"sha":"4cf0755ea3e070ea91cbc7ab3aabb5729cc877a7","author":{"email":"68ee766e574f18b34b683085865827393efe88bd@linux.intel.com","name":"Jiang Liu"},"message":"iommu/vt-d: Fix an off-by-one bug in __domain_mapping()\n\ncommit cc4f14aa170d895c9a43bdb56f62070c8a6da908 upstream.\n\nThere's an off-by-one bug in function __domain_mapping(), which may\ntrigger the BUG_ON(nr_pages < lvl_pages) when\n\t(nr_pages + 1) & superpage_mask == 0\n\nThe issue was introduced by commit 9051aa0268dc \"intel-iommu: Combine\ndomain_pfn_mapping() and domain_sg_mapping()\", which sets sg_res to\n\"nr_pages + 1\" to avoid some of the 'sg_res==0' code paths.\n\nIt's safe to remove extra \"+1\" because sg_res is only used to calculate\npage size now.\n\nReported-And-Tested-by: Sudeep Dutt <sudeep.dutt@intel.com>\nSigned-off-by: Jiang Liu <jiang.liu@linux.intel.com>\nAcked-By: David Woodhouse <David.Woodhouse@intel.com>\nSigned-off-by: Joerg Roedel <jroedel@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_motorola_apq8084/commits/4cf0755ea3e070ea91cbc7ab3aabb5729cc877a7"},{"sha":"f2536a3449dad1608e64fec01368786fc8e83297","author":{"email":"abfe2be44ce1109c5b4ede022c1c0e9619655785@invensense.com","name":"Jean-Baptiste Maneyrol"},"message":"HID: i2c-hid: fix race condition reading reports\n\ncommit 6296f4a8eb86f9abcc370fb7a1a116b8441c17fd upstream.\n\nCurrent driver uses a common buffer for reading reports either\nsynchronously in i2c_hid_get_raw_report() and asynchronously in\nthe interrupt handler.\nThere is race condition if an interrupt arrives immediately after\nthe report is received in i2c_hid_get_raw_report(); the common\nbuffer is modified by the interrupt handler with the new report\nand then i2c_hid_get_raw_report() proceed using wrong data.\n\nFix it by using a separate buffers for synchronous reports.\n\nSigned-off-by: Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>\n[Antonio Borneo: cleanup, rebase to v3.17, submit mainline]\nSigned-off-by: Antonio Borneo <borneo.antonio@gmail.com>\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/MoKee/android_kernel_motorola_apq8084/commits/f2536a3449dad1608e64fec01368786fc8e83297"},{"sha":"e0bff89ab6b6fd9d1d4ea67e2a72ec378488bcb0","author":{"email":"190c5a5edfcf62e0246559bf31fa7548674de3ad@chromium.org","name":"Gwendal Grignou"},"message":"HID: i2c-hid: prevent buffer overflow in early IRQ\n\ncommit d1c7e29e8d276c669e8790bb8be9f505ddc48888 upstream.\n\nBefore ->start() is called, bufsize size is set to HID_MIN_BUFFER_SIZE,\n64 bytes. While processing the IRQ, we were asking to receive up to\nwMaxInputLength bytes, which can be bigger than 64 bytes.\n\nLater, when ->start is run, a proper bufsize will be calculated.\n\nGiven wMaxInputLength is said to be unreliable in other part of the\ncode, set to receive only what we can even if it results in truncated\nreports.\n\nSigned-off-by: Gwendal Grignou <gwendal@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/MoKee/android_kernel_motorola_apq8084/commits/e0bff89ab6b6fd9d1d4ea67e2a72ec378488bcb0"},{"sha":"dc1d93b9e4cc57de48610a709e978b1d26657b58","author":{"email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com","name":"Dan Carpenter"},"message":"HID: roccat: potential out of bounds in pyra_sysfs_write_settings()\n\ncommit 606185b20caf4c57d7e41e5a5ea4aff460aef2ab upstream.\n\nThis is a static checker fix.  We write some binary settings to the\nsysfs file.  One of the settings is the \"->startup_profile\".  There\nisn't any checking to make sure it fits into the\npyra->profile_settings[] array in the profile_activated() function.\n\nI added a check to pyra_sysfs_write_settings() in both places because\nI wasn't positive that the other callers were correct.\n\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.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/MoKee/android_kernel_motorola_apq8084/commits/dc1d93b9e4cc57de48610a709e978b1d26657b58"},{"sha":"c533c63d190e42f327e9d21e7838d7a125e2df92","author":{"email":"ed666e53e33ef4cc337a3172b0063e5133b45a64@ntlworld.com","name":"Karl Relton"},"message":"HID: add battery quirk for USB_DEVICE_ID_APPLE_ALU_WIRELESS_2011_ISO keyboard\n\ncommit da940db41dcf8c04166f711646df2f35376010aa upstream.\n\nApple bluetooth wireless keyboard (sold in UK) has always reported zero\nfor battery strength no matter what condition the batteries are actually\nin. With this patch applied (applying same quirk as other Apple\nkeyboards), the battery strength is now correctly reported.\n\nSigned-off-by: Karl Relton <karllinuxtest.relton@ntlworld.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/MoKee/android_kernel_motorola_apq8084/commits/c533c63d190e42f327e9d21e7838d7a125e2df92"},{"sha":"da6dcf04df8332ee9c482ae63e2b0b7c346cfec6","author":{"email":"f1628506d066beb6229c6ca0fc8c69f80553b7c6@gmail.com","name":"Giedrius Statkevičius"},"message":"HID: Add a new id 0x501a for Genius MousePen i608X\n\ncommit 2bacedada682d5485424f5227f27a3d5d6eb551c upstream.\n\nNew Genius MousePen i608X devices have a new id 0x501a instead of the\nold 0x5011 so add a new #define with \"_2\" appended and change required\nplaces.\n\nThe remaining two checkpatch warnings about line length\nbeing over 80 characters are present in the original files too and this\npatch was made in the same style (no line break).\n\nJust adding a new id and changing the required places should make the\nnew device work without any issues according to the bug report in the\nfollowing url.\n\nThis patch was made according to and fixes:\nhttps://bugzilla.kernel.org/show_bug.cgi?id=67111\n\nSigned-off-by: Giedrius Statkevičius <giedrius.statkevicius@gmail.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/MoKee/android_kernel_motorola_apq8084/commits/da6dcf04df8332ee9c482ae63e2b0b7c346cfec6"},{"sha":"7d6bf19e873d364bfc61d1a2dc95db6535fef3b9","author":{"email":"2cc0d0d76de2e6f37b92deeb83c85cb306fc5dc1@amacapital.net","name":"Andy Lutomirski"},"message":"x86_64, vdso: Fix the vdso address randomization algorithm\n\ncommit 394f56fe480140877304d342dec46d50dc823d46 upstream.\n\nThe theory behind vdso randomization is that it's mapped at a random\noffset above the top of the stack.  To avoid wasting a page of\nmemory for an extra page table, the vdso isn't supposed to extend\npast the lowest PMD into which it can fit.  Other than that, the\naddress should be a uniformly distributed address that meets all of\nthe alignment requirements.\n\nThe current algorithm is buggy: the vdso has about a 50% probability\nof being at the very end of a PMD.  The current algorithm also has a\ndecent chance of failing outright due to incorrect handling of the\ncase where the top of the stack is near the top of its PMD.\n\nThis fixes the implementation.  The paxtest estimate of vdso\n\"randomisation\" improves from 11 bits to 18 bits.  (Disclaimer: I\ndon't know what the paxtest code is actually calculating.)\n\nIt's worth noting that this algorithm is inherently biased: the vdso\nis more likely to end up near the end of its PMD than near the\nbeginning.  Ideally we would either nix the PMD sharing requirement\nor jointly randomize the vdso and the stack to reduce the bias.\n\nIn the mean time, this is a considerable improvement with basically\nno risk of compatibility issues, since the allowed outputs of the\nalgorithm are unchanged.\n\nAs an easy test, doing this:\n\nfor i in `seq 10000`\n  do grep -P vdso /proc/self/maps |cut -d- -f1\ndone |sort |uniq -d\n\nused to produce lots of output (1445 lines on my most recent run).\nA tiny subset looks like this:\n\n7fffdfffe000\n7fffe01fe000\n7fffe05fe000\n7fffe07fe000\n7fffe09fe000\n7fffe0bfe000\n7fffe0dfe000\n\nNote the suspicious fe000 endings.  With the fix, I get a much more\npalatable 76 repeated addresses.\n\nReviewed-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: Andy Lutomirski <luto@amacapital.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_motorola_apq8084/commits/7d6bf19e873d364bfc61d1a2dc95db6535fef3b9"},{"sha":"bb82a012775da5b6a41670b627e90482a7c3709d","author":{"email":"2cc0d0d76de2e6f37b92deeb83c85cb306fc5dc1@amacapital.net","name":"Andy Lutomirski"},"message":"x86, vdso: Use asm volatile in __getcpu\n\ncommit 1ddf0b1b11aa8a90cef6706e935fc31c75c406ba upstream.\n\nIn Linux 3.18 and below, GCC hoists the lsl instructions in the\npvclock code all the way to the beginning of __vdso_clock_gettime,\nslowing the non-paravirt case significantly.  For unknown reasons,\npresumably related to the removal of a branch, the performance issue\nis gone as of\n\ne76b027e6408 x86,vdso: Use LSL unconditionally for vgetcpu\n\nbut I don't trust GCC enough to expect the problem to stay fixed.\n\nThere should be no correctness issue, because the __getcpu calls in\n__vdso_vlock_gettime were never necessary in the first place.\n\nNote to stable maintainers: In 3.18 and below, depending on\nconfiguration, gcc 4.9.2 generates code like this:\n\n     9c3:       44 0f 03 e8             lsl    %ax,%r13d\n     9c7:       45 89 eb                mov    %r13d,%r11d\n     9ca:       0f 03 d8                lsl    %ax,%ebx\n\nThis patch won't apply as is to any released kernel, but I'll send a\ntrivial backported version if needed.\n\n[\n Backported by Andy Lutomirski.  Should apply to all affected\n versions.  This fixes a functionality bug as well as a performance\n bug: buggy kernels can infinite loop in __vdso_clock_gettime on\n affected compilers.  See, for exammple:\n\n https://bugzilla.redhat.com/show_bug.cgi?id=1178975\n]\n\nFixes: 51c19b4f5927 x86: vdso: pvclock gettime support\nCc: Marcelo Tosatti <mtosatti@redhat.com>\nAcked-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Andy Lutomirski <luto@amacapital.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_motorola_apq8084/commits/bb82a012775da5b6a41670b627e90482a7c3709d"},{"sha":"45ef2be70ced1b0fcd6477dcf795e3d7fb1cb3c3","author":{"email":"7469de9b95ba379e2656fa9677689657c47a7690@redhat.com","name":"Alex Williamson"},"message":"driver core: Fix unbalanced device reference in drivers_probe\n\ncommit bb34cb6bbd287b57e955bc5cfd42fcde6aaca279 upstream.\n\nbus_find_device_by_name() acquires a device reference which is never\nreleased.  This results in an object leak, which on older kernels\nresults in failure to release all resources of PCI devices.  libvirt\nuses drivers_probe to re-attach devices to the host after assignment\nand is therefore a common trigger for this leak.\n\nExample:\n\n# cd /sys/bus/pci/\n# dmesg -C\n# echo 1 > devices/0000\\:01\\:00.0/sriov_numvfs\n# echo 0 > devices/0000\\:01\\:00.0/sriov_numvfs\n# dmesg | grep 01:10\n pci 0000:01:10.0: [8086:10ca] type 00 class 0x020000\n kobject: '0000:01:10.0' (ffff8801d79cd0a8): kobject_add_internal: parent: '0000:00:01.0', set: 'devices'\n kobject: '0000:01:10.0' (ffff8801d79cd0a8): kobject_uevent_env\n kobject: '0000:01:10.0' (ffff8801d79cd0a8): fill_kobj_path: path = '/devices/pci0000:00/0000:00:01.0/0000:01:10.0'\n kobject: '0000:01:10.0' (ffff8801d79cd0a8): kobject_uevent_env\n kobject: '0000:01:10.0' (ffff8801d79cd0a8): fill_kobj_path: path = '/devices/pci0000:00/0000:00:01.0/0000:01:10.0'\n kobject: '0000:01:10.0' (ffff8801d79cd0a8): kobject_uevent_env\n kobject: '0000:01:10.0' (ffff8801d79cd0a8): fill_kobj_path: path = '/devices/pci0000:00/0000:00:01.0/0000:01:10.0'\n kobject: '0000:01:10.0' (ffff8801d79cd0a8): kobject_cleanup, parent           (null)\n kobject: '0000:01:10.0' (ffff8801d79cd0a8): calling ktype release\n kobject: '0000:01:10.0': free name\n\n[kobject freed as expected]\n\n# dmesg -C\n# echo 1 > devices/0000\\:01\\:00.0/sriov_numvfs\n# echo 0000:01:10.0 > drivers_probe\n# echo 0 > devices/0000\\:01\\:00.0/sriov_numvfs\n# dmesg | grep 01:10\n pci 0000:01:10.0: [8086:10ca] type 00 class 0x020000\n kobject: '0000:01:10.0' (ffff8801d79ce0a8): kobject_add_internal: parent: '0000:00:01.0', set: 'devices'\n kobject: '0000:01:10.0' (ffff8801d79ce0a8): kobject_uevent_env\n kobject: '0000:01:10.0' (ffff8801d79ce0a8): fill_kobj_path: path = '/devices/pci0000:00/0000:00:01.0/0000:01:10.0'\n kobject: '0000:01:10.0' (ffff8801d79ce0a8): kobject_uevent_env\n kobject: '0000:01:10.0' (ffff8801d79ce0a8): fill_kobj_path: path = '/devices/pci0000:00/0000:00:01.0/0000:01:10.0'\n kobject: '0000:01:10.0' (ffff8801d79ce0a8): kobject_uevent_env\n kobject: '0000:01:10.0' (ffff8801d79ce0a8): fill_kobj_path: path = '/devices/pci0000:00/0000:00:01.0/0000:01:10.0'\n\n[no free]\n\nSigned-off-by: Alex Williamson <alex.williamson@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_motorola_apq8084/commits/45ef2be70ced1b0fcd6477dcf795e3d7fb1cb3c3"},{"sha":"e1495e6281f554d90255eb2e2e25c75f5f73c38c","author":{"email":"4f158856819fc06480b815ac43e72f73d2745502@redhat.com","name":"Jiri Jaburek"},"message":"ALSA: usb-audio: extend KEF X300A FU 10 tweak to Arcam rPAC\n\ncommit d70a1b9893f820fdbcdffac408c909c50f2e6b43 upstream.\n\nThe Arcam rPAC seems to have the same problem - whenever anything\n(alsamixer, udevd, 3.9+ kernel from 60af3d037eb8c, ..) attempts to\naccess mixer / control interface of the card, the firmware \"locks up\"\nthe entire device, resulting in\n  SNDRV_PCM_IOCTL_HW_PARAMS failed (-5): Input/output error\nfrom alsa-lib.\n\nOther operating systems can somehow read the mixer (there seems to be\nplayback volume/mute), but any manipulation is ignored by the device\n(which has hardware volume controls).\n\nSigned-off-by: Jiri Jaburek <jjaburek@redhat.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/MoKee/android_kernel_motorola_apq8084/commits/e1495e6281f554d90255eb2e2e25c75f5f73c38c"},{"sha":"218591eae7533fb3a8bbf7b9da1af7c20a608d4a","author":{"email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com","name":"Dan Carpenter"},"message":"ALSA: hda - using uninitialized data\n\ncommit 69eba10e606a80665f8573221fec589430d9d1cb upstream.\n\nIn olden times the snd_hda_param_read() function always set \"*start_id\"\nbut in 2007 we introduced a new return and it causes uninitialized data\nbugs in a couple of the callers: print_codec_info() and\nhdmi_parse_codec().\n\nFixes: e8a7f136f5ed ('[ALSA] hda-intel - Improve HD-audio codec probing robustness')\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.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/MoKee/android_kernel_motorola_apq8084/commits/218591eae7533fb3a8bbf7b9da1af7c20a608d4a"},{"sha":"eee0ce2b1c9a4d67130133dbdc8b014f44695911","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"ALSA: hda - Fix wrong gpio_dir & gpio_mask hint setups for IDT/STAC codecs\n\ncommit c507de88f6a336bd7296c9ec0073b2d4af8b4f5e upstream.\n\nstac_store_hints() does utterly wrong for masking the values for\ngpio_dir and gpio_data, likely due to copy&paste errors.  Fortunately,\nthis feature is used very rarely, so the impact must be really small.\n\nReported-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>\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/MoKee/android_kernel_motorola_apq8084/commits/eee0ce2b1c9a4d67130133dbdc8b014f44695911"},{"sha":"5c8afe0f7f45f88d29e877ba37812d67ae67c314","author":{"email":"4645f7897fd33786a2ee1264d590b3c400559d85@linuxfoundation.org","name":"Greg Kroah-Hartman"},"message":"USB: cdc-acm: check for valid interfaces\n\ncommit 403dff4e2c94f275e24fd85f40b2732ffec268a1 upstream.\n\nWe need to check that we have both a valid data and control inteface for both\ntypes of headers (union and not union.)\n\nReferences: https://bugzilla.kernel.org/show_bug.cgi?id=83551\nReported-by: Simon Schubert <2+kernel@0x2c.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_motorola_apq8084/commits/5c8afe0f7f45f88d29e877ba37812d67ae67c314"},{"sha":"076e921326c3e88b5d6ce9bd842bb215dddc2bf7","author":{"email":"cd8c6775e60d6f67a6984377324e5290df3d5358@fb.com","name":"Jens Axboe"},"message":"genhd: check for int overflow in disk_expand_part_tbl()\n\ncommit 5fabcb4c33fe11c7e3afdf805fde26c1a54d0953 upstream.\n\nWe can get here from blkdev_ioctl() -> blkpg_ioctl() -> add_partition()\nwith a user passed in partno value. If we pass in 0x7fffffff, the\nnew target in disk_expand_part_tbl() overflows the 'int' and we\naccess beyond the end of ptbl->part[] and even write to it when we\ndo the rcu_assign_pointer() to assign the new partition.\n\nReported-by: David Ramos <daramos@stanford.edu>\nSigned-off-by: Jens Axboe <axboe@fb.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_motorola_apq8084/commits/076e921326c3e88b5d6ce9bd842bb215dddc2bf7"},{"sha":"4b6ea4904cb03b8666143caa8ca32640c34084ea","author":{"email":"bfee72d94d376f4e00f72b756466867d7f9eb24e@suse.de","name":"Oliver Neukum"},"message":"cdc-acm: memory leak in error case\n\ncommit d908f8478a8d18e66c80a12adb27764920c1f1ca upstream.\n\nIf probe() fails not only the attributes need to be removed\nbut also the memory freed.\n\nReported-by: Ahmed Tamrawi <ahmedtamrawi@gmail.com>\nSigned-off-by: Oliver Neukum <oneukum@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/MoKee/android_kernel_motorola_apq8084/commits/4b6ea4904cb03b8666143caa8ca32640c34084ea"}]}