4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 4f9785cc99feeb3673993b471f646b4dbaec2cc1 upstream.
In case a device is left in "boot-mode" we must not register any port
devices in order to avoid a NULL-pointer dereference
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit a323fefc6f5079844dc62ffeb54f491d0242ca35 upstream.
Fix NULL-pointer dereference when clearing halt at open should a
malicious device lack the expected endpoints when in down
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit c4ac4496e835b78a45dfbf74f6173932217e4116 upstream.
Make sure to free the URB transfer buffer in case submission fails (e.g.
due to a disconnect).
Fixes: 1da177e4c3f4 ("Linu
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit faab50984fe6636e616c7cc3d30308ba391d36fd upstream.
Andrey Konovalov reports that fuzz testing with syzkaller causes a
KASAN warning in gadgetfs:
BUG: KASAN: slab-out-of-bound
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit cc0909248258f679c4bb4cd315565d40abaf6bc6 upstream.
Fix NULL-pointer dereference in open() should the device lack the
expected endpoints:
Unable to handle kernel NULL pointe
On Tue, Jan 10, 2017 at 03:47:25PM +0300, Nikita Yushchenko wrote:
> With this direction, semantics of dma mask becomes even more
> questionable. I'd say dma_mask is candidate for removal (or to move to
> swiotlb's or iommu's local area)
We need the dma mask so that the device can advertise what a
OPOS6UL is an i.MX6UL based SoM.
OPOS6ULDev is a carrier board for the OPOS6UL SoM.
For more details see:
http://www.opossom.com/english/products-processor_boards-opos6ul.html
http://www.opossom.com/english/products-development_boards-opos6ul_dev.html
Signed-off-by: Sébastien Szymanski
---
Chang
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit f09d1886a41e9063b43da493ef0e845ac8afd2fa upstream.
The write URB was being killed using the synchronous interface while
holding a spin lock in close().
Simply drop the lock
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Lu Baolu
commit 4dea70778c0f48b4385c7720c363ec8d37a401b4 upstream.
In command timer function, xhci_handle_command_timeout(), xhci->lock
is unlocked before call into xhci_abort_cmd_ring(). This
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit a5a1b9514154437aa1ed35c291191f82fd3e941a upstream.
If we get a command completion event at the same time as the command
timeout work starts on another cpu we might end up a
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit a5bc01949e3b19d8a23b5eabc6fc71bb50dc820e upstream.
Fix NULL-pointer dereferences at open() and disconnect() should the
device lack the expected bulk-out endpoints:
Unable t
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit ee8665e28e8d90ce69d4abe5a469c14a8707ae0e upstream.
the tt_info provided by a HS hub might be in use to by a child device
Make sure we free the devices in the correct order.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Lu Baolu
commit 90797aee5d6902b49a453c97d83c326408aeb5a8 upstream.
xhci_setup_device() should return failure with correct error number
when xhci host has died, removed or halted.
During usb de
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Baolin Wang
commit 2a7cfdf37b7c08ac29df4c62ea5ccb01474b6597 upstream.
When current command was supposed to be aborted, host will free the command
in handle_cmd_completion() function. But it mig
On 01/10/2017 08:32 AM, Juergen Gross wrote:
> The default for the number of tx/rx queues of one interface is the
> number of vcpus of the system today. As each queue pair reserves 512
> grant pages this default consumes a ridiculous number of grants for
> large guests.
>
> Limit the queue number t
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 0994b0a257557e18ee8f0b7c5f0f73fe2b54eec1 upstream.
Andrey Konovalov reported that we were not properly checking the upper
limit before of a device configuration size b
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit c7efff9284dfde95a11aaa811c9d8ec8167f0f6e upstream.
Although the old quirk table showed ASUS X71SL with ALC663 codec being
compatible with asus-mode3 fixup, the bugzilla repo
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Akinobu Mita
commit b4e8a0eb718749455601fa7b283febc42cca8957 upstream.
According to the datasheet, the shortest available integration time for
ALS ADC conversion is 1.5625ms but illuminance_int
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
commit e7c9a3d9e432200fd4c17855c2c23ac784d6e833 upstream.
The Octeon driver calls into PHYLIB which now checks for
net_device->dev.parent, so make sure we do set it before call
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Bartosz Golaszewski
commit ef37427ac5677331145ab27a17e6f5f1b43f0c11 upstream.
Similarly to the aemif clock - this screws up the linked list of clock
children. Create a separate clock for mdio i
Hi,
here are the last two patches that remain to be merged in this series,
rebased on today's drm-tip.
Thanks,
Tomeu
Tomeu Vizoso (2):
drm/i915: Use new CRC debugfs API
drm/i915: Put "cooked" vlank counters in frame CRC lines
drivers/gpu/drm/i915/i915_drv.h | 1 +
drivers/gpu/drm/
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Bin Liu
commit c48400baa02155a5ddad63e8554602e48782278c upstream.
During dma teardown for dequque urb, if musb load is high, musb might
generate bogus rx ep interrupt even when the rx fifo is f
On Tue, Jan 10, 2017 at 09:39:39PM +0800, Hanjun Guo wrote:
[...]
> >What you can do is create a wrapper, say iort_node_map_platform_id()
> >(whose signature is equivalent to iort_node_map_rid() minus rid_in)
> >that carries out the two steps outlined above.
> >
> >To do that I suggest the follow
> -Original Message-
> From: Arnd Bergmann [mailto:a...@arndb.de]
> Sent: Tuesday, January 10, 2017 6:19 AM
> To: Shawn Guo
> Cc: Thomas Gleixner ; Arnd Bergmann
> ; Sascha Hauer ; Fabio Estevam
> ; Russell King ; Frank Li
> ; linux-arm-ker...@lists.infradead.org; linux-
> ker...@vger.ke
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ioan-Adrian Ratiu
commit 1d0f953086f090a022f2c0e1448300c15372db46 upstream.
Commit 16200948d83 ("ALSA: usb-audio: Fix race at stopping the stream") was
incomplete causing another more severe ke
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Helge Deller
commit 41744213602a206f24adcb4a2b7551db3c700e72 upstream.
The cr16 interval timer of each CPU is not syncronized to other cr16
timers in other CPUs in a SMP system. So, delay the r
On Tue, Jan 10, 2017 at 01:25:12PM +, Robin Murphy wrote:
> We still need a way for drivers to communicate a device's probed
> addressing capability to SWIOTLB, so there's always going to have to be
> *some* sort of public interface. Personally, the change in semantics I'd
> like to see is to m
Use drm_accurate_vblank_count so we have the full 32 bit to represent
the frame counter and userspace has a simpler way of knowing when the
counter wraps around.
Signed-off-by: Tomeu Vizoso
Reviewed-by: Emil Velikov
Reviewed-by: Robert Foss
---
drivers/gpu/drm/i915/i915_irq.c | 6 +++---
1 fi
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit a2c435cc99862fd3d165e1b66bf48ac72c839c62 upstream.
The AES implementation using pure NEON instructions relies on the generic
AES key schedule generation routines, which st
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Srinivas Pandruvada
commit 143fca77cce906d35f7a60ccef648e888df589f2 upstream.
While applying patch d443a0aa3a29: "HID: hid-sensor-hub: clear memory to
avoid random data", there was some issues
The core provides now an ABI to userspace for generation of frame CRCs,
so implement the ->set_crc_source() callback and reuse as much code as
possible with the previous ABI implementation.
When handling the pageflip interrupt, we skip 1 or 2 frames depending on
the HW because they contain wrong v
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit ee71e5f1e7d25543ee63a80451871f8985b8d431 upstream.
The SHA1 digest is an array of 5 32-bit quantities, so we should refer
to them as such in order for this code to work co
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit 1803b9a52c4e5a5dbb8a27126f6bc06939359753 upstream.
The core AES cipher implementation that uses ARMv8 Crypto Extensions
instructions erroneously loads the round keys as 64
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit 58010fa6f71c9577922b22e46014b95a4ec80fa0 upstream.
The AES key schedule generation is mostly endian agnostic, with the
exception of the rotation and the incorporation of t
On Tue, Jan 10, 2017 at 02:42:23PM +0100, Arnd Bergmann wrote:
> It's a much rarer problem for the IOMMU case though, because it only
> impacts devices that are restricted to addressing of less than 32-bits.
>
> If you have an IOMMU enabled, the dma-mapping interface does not care
> if the device
Vitaly,
On Tue, 10 Jan 2017, Vitaly Kuznetsov wrote:
> Thomas Gleixner writes:
> > 1) do_adjtimex() is assuming that there is a single client connected which
> >is responsible for the updates. So I seriously doubt that a NTP client
> >running in the guest will cooperate nicely with that t
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
commit f0b0faff78c2c2e8efe843de55405a1f0470b8c4 upstream.
Smatch complains about where the au8293_data is placed:
drivers/media/pci/cx23885/cx23885-dvb.c:2174 dvb_registe
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit 174122c39c369ed924d2608fc0be0171997ce800 upstream.
The SHA256 digest is an array of 8 32-bit quantities, so we should refer
to them as such in order for this code to work
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Lorenzo Bianconi
commit 65c8aea07de11b6507efa175edb44bd8b4488218 upstream.
Using realbits as i2c/spi read len, when that value is not byte aligned
(e.g 12 bits), lead to skip msb part of out da
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 57e7c8cef224af166b8ec932b5e383641418c005 upstream.
When CONFIG_PCI_MSI is disabled, we get warnings about unused functions
in the vxge driver:
drivers/net/ethernet/neterio
On Tuesday, January 10, 2017 1:25:12 PM CET Robin Murphy wrote:
> On 10/01/17 12:47, Nikita Yushchenko wrote:
> >> The point here is that an IOMMU doesn't solve your issue, and the
> >> IOMMU-backed DMA ops need the same treatment. In light of that, it really
> >> feels to me like the DMA masks sho
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Tony Lindgren
commit bed570307ed78f21b77cb04a1df781dee4a8f05a upstream.
I noticed some wakeirq flakeyness with consumer drivers not using
autosuspend. For drivers not using autosuspend, the wak
On Tue, 2017-01-10 at 15:03 +0100, Johannes Berg wrote:
> From: Johannes Berg
>
> The script says that it won't warn:
> "No structs that should be const will be found [...]"
>
> but then that doesn't work and it warns on every single struct
> instead, since the regular expression ends up empty.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: OGAWA Hirofumi
commit cb4d5ce588c5ff68e0fdd30370a0e6bc2c0a736b upstream.
This is preparation to fix abort operation race (See "xhci: Fix race
related to abort operation"). To make timeout sleep
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 9e6e7c74315095fd40f41003850690c711e44420 upstream.
We added some new locking but forgot to unlock on error.
Fixes: 57127645d79d ("s390/zcrypt: Introduce new SHA-512 based
On 10/01/17 15:53, Boris Ostrovsky wrote:
> On 01/10/2017 08:32 AM, Juergen Gross wrote:
>> The default for the number of tx/rx queues of one interface is the
>> number of vcpus of the system today. As each queue pair reserves 512
>> grant pages this default consumes a ridiculous number of grants f
On Tuesday, January 10, 2017 3:44:53 PM CET Christoph Hellwig wrote:
> On Tue, Jan 10, 2017 at 11:47:42AM +0100, Arnd Bergmann wrote:
> > I see that we have CONFIG_ARCH_PHYS_ADDR_T_64BIT on a couple of
> > 32-bit architectures without swiotlb (arc, arm, some mips32), and
> > there are several 64-bi
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
commit 34c535793bcbf9263cf22f8a52101f796cdfab8e upstream.
We did not implement an irq_cpu_offline callback for our irqchip, yet we
support setting a given IRQ's affinity. This
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 21ce57840243c7b70fbc1ebd3dceeb70bb6e9e09 upstream.
Fix NULL-pointer dereference in write() should the device lack the
expected interrupt-out endpoint:
Unable to handle kern
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: H Hartley Sweeten
commit f6b1160eb27f990cc1c48b67a5f83cb63115284e upstream.
Arnd Bergmann pointed out that gcc-6 warns about passing negative signed
integer into swab16() due to the macro expan
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: OGAWA Hirofumi
commit 1c111b6c3844a142e03bcfc2fa17bfbdea08e9dc upstream.
Current abort operation has race.
xhci_handle_command_timeout()
xhci_abort_cmd_ring()
xhci_write_64(C
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 91a1ff4d53c5184d383d0baeeaeab6f9736f2ff3 upstream.
The interrupt URB was submitted on probe but never stopped on probe
errors. This can lead to use-after-free issues in the
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit af15769ffab13d777e55fdef09d0762bf0c249c4 upstream.
gcc-7 notices that the condition in mvs_94xx_command_active looks
suspicious:
drivers/scsi/mvsas/mv_94xx.c: In function
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 75dd211e773afcbc264677b0749d1cf7d937ab2d upstream.
Do not submit the interrupt URB until after the parport has been
successfully registered to avoid another use-after-free i
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Pan Bian
commit 20979202ee6e4c68dab7bcf408787225a656d18e upstream.
Fix bug https://bugzilla.kernel.org/show_bug.cgi?id=188561. Function
wm831x_clkout_is_prepared() returns "true" when it fails
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jacob Pan
commit 65ca7f5f7d1cdde6c25172fe6107cd16902f826f upstream.
Different encodings are used to represent supported PASID bits
and number of PASID table entries.
The current code assigns ec
On Tuesday, January 10, 2017 2:16:57 PM CET Robin Murphy wrote:
> On 10/01/17 13:42, Arnd Bergmann wrote:
> > On Tuesday, January 10, 2017 1:25:12 PM CET Robin Murphy wrote:
> >> On 10/01/17 12:47, Nikita Yushchenko wrote:
> The point here is that an IOMMU doesn't solve your issue, and the
> >
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Xunlei Pang
commit aec0e86172a79eb5e44aff1055bb953fe4d47c59 upstream.
We met the DMAR fault both on hpsa P420i and P421 SmartArray controllers
under kdump, it can be steadily reproduced on seve
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 24c790fbf5d8f54c8c82979db11edea8855b74bf upstream.
We should set "ret" to -EINVAL if iommu_group_get() fails.
Fixes: 55c99a4dc50f ("iommu/amd: Use iommu_attach_group()")
S
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit 4fccd4a1e8944033bcd7693ea4e8fb478cd2059a upstream.
Fix overflows seen when writing into fan speed limit attributes.
Also fix crash due to division by zero, seen when certai
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Huang Rui
commit 432abf68a79332282329286d190e21fe3ac02a31 upstream.
The generic command buffer entry is 128 bits (16 bytes), so the offset
of tail and head pointer should be 16 bytes aligned an
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit e36ce99ee0815d7919a7b589bfb66f3de50b6bc7 upstream.
Module test reports:
temp1_max: Suspected overflow: [16 vs. 0]
temp1_min: Suspected overflow: [16 vs. 0]
This i
On Tue, 2017-01-10 at 07:01 -0800, Joe Perches wrote:
> On Tue, 2017-01-10 at 15:03 +0100, Johannes Berg wrote:
> > From: Johannes Berg
> >
> > The script says that it won't warn:
> > "No structs that should be const will be found [...]"
> >
> > but then that doesn't work and it warns on every s
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Shaohua Li
commit 82a301cb0ea2df8a5c88213094a01660067c7fb4 upstream.
Fixes: 90f5f7ad4f38("md: Wait for md_check_recovery before attempting device
removal.")
Reviewed-by: NeilBrown
Signed-off-
From: Corey Minyard
It's only function pointers.
Signed-off-by: Corey Minyard
---
drivers/char/ipmi/ipmi_devintf.c| 2 +-
drivers/char/ipmi/ipmi_msghandler.c | 4 ++--
drivers/char/ipmi/ipmi_watchdog.c | 2 +-
include/linux/ipmi.h| 2 +-
4 files changed, 5 insertions(+),
On Tuesday, January 10, 2017 3:48:39 PM CET Christoph Hellwig wrote:
> On Tue, Jan 10, 2017 at 12:01:05PM +0100, Arnd Bergmann wrote:
> > Another workaround me might need is to limit amount of concurrent DMA
> > in the NVMe driver based on some platform quirk. The way that NVMe works,
> > it can ha
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Felipe Balbi
commit d62145929992f331fdde924d5963ab49588ccc7d upstream.
commit 0416e494ce7d ("usb: dwc3: ep0: correct cache
sync issue in case of ep0_bounced") introduced a bug
where we would le
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Javier Martinez Canillas
commit 13edb767aa609b6efb7c0c2b57fbd72a6ded0eed upstream.
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 4763601a56f155ddf94ef35fc2c41504a2de15f5 upstream.
The function returns -EINVAL even if it builds the stream properly.
The bogus error code sneaked in during the code refact
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Pan Bian
commit 3c3dd1e058cb01e835dcade4b54a6f13ffaeaf7c upstream.
Function klsi_105_open() calls usb_control_msg() (to "enable read") and
checks its return value. When the return value is unex
Hi Murali,
On Wed, Jan 04, 2017 at 02:32:30PM -0500, Murali Karicheri wrote:
> Recent fixes for iATU unroll support introduced a bug that causes
> asynchronous external abort in Keystone PCIe h/w which doesn't have
> ATU port and the corresponding register. So the check should be moved
> below whe
This makes the handlers for IPMI users able to be const, then
sets all the users const. Trivial, but I need an ack from the
ACPI people on this. Thanks.
With CONFIG_DYNAMIC_DEBUG if dyndbg enables debug output in
8250_port.c deadlock happens inevitably on UART IRQ handling.
That's the problematic execution path:
>8
UART IRQ:
serial8250_interrupt() ->
serial8250_handle_irq(): lock "port->loc
On Tue, Jan 10, 2017 at 07:46:17PM +0800, Cao jin wrote:
>
>
> On 01/10/2017 07:04 AM, Michael S. Tsirkin wrote:
> > On Sat, Dec 31, 2016 at 05:15:36PM +0800, Cao jin wrote:
> >> Support serious device error recovery
> >
> > serious?
> >
>
> Sorry for my poor vocabulary if it confuses people. I
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 015105b12183556771e111e93f5266851e7c5582 upstream.
Make sure to drop the references taken by of_parse_phandle() and
bus_find_device() before returning from am335x_get_phy_co
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
[resolves a messed up backport, so no matching upstream commit]
The backport of upstream commit 777c6e0daebb ("hotplug: Make
register and unregister notifier API symmetric") to li
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit b05aebc25fdc5aeeac3ee29f0dc9f58dd07c13cc upstream.
Fix NULL-pointer dereference at port open if a device lacks the expected
bulk in and out endpoints.
Unable to handle kern
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Usyskin
commit 5026c9cb0744a9cd40242743ca91a5d712f468c6 upstream.
Adjust function name in KDoc.
Fixes: d49dc5e76fc9 (mei: bus: use mei_cldev_ prefix for the API functions)
Signed-off
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit e35d6d7c4e6532a89732cf4bace0e910ee684c88 upstream.
Bind to the interface, but do not register any ports, after having
downloaded the firmware. The device will still disconne
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nicolas Iooss
commit 31b239824ece321c09bdb8e61e1d14814eaba38b upstream.
The word "background" contains 10 characters so the third argument of
strncmp() need to be 10 in order to match this pref
Hi Lorenzo,
On 2017/1/5 23:15, Lorenzo Pieralisi wrote:
On Thu, Jan 05, 2017 at 08:45:37PM +0800, Hanjun Guo wrote:
Hi Lorenzo,
On 2017/1/5 3:18, Lorenzo Pieralisi wrote:
On Mon, Jan 02, 2017 at 09:31:36PM +0800, Hanjun Guo wrote:
For devices connecting to ITS, it needs dev id to identify
it
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit c4ac4496e835b78a45dfbf74f6173932217e4116 upstream.
Make sure to free the URB transfer buffer in case submission fails (e.g.
due to a disconnect).
Fixes: 1da177e4c3f4 ("Linu
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Bartosz Golaszewski
commit ef37427ac5677331145ab27a17e6f5f1b43f0c11 upstream.
Similarly to the aemif clock - this screws up the linked list of clock
children. Create a separate clock for mdio i
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 0dd408425eb21ddf26a692b3c8044c9e7d1a7948 upstream.
Fix NULL-pointer dereference when initialising URBs at open should a
non-EPIC device lack a bulk-in or interrupt-in endpoi
On Tue, Jan 10, 2017 at 06:11:25PM +0530, Bhumika Goyal wrote:
> On Tue, Jan 10, 2017 at 10:41 AM, Michael S. Tsirkin wrote:
> > On Mon, Jan 09, 2017 at 08:51:02PM +0530, Bhumika Goyal wrote:
> >> Declare target_core_fabric_ops strucrues as const as they are only
> >> passed as an argument to the
This is the start of the stable review cycle for the 4.4.42 release.
There are 101 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Thu Jan 12 13:15:04 UTC 2017.
Anything receiv
ACK - smc_splice_read() is just a place holder at the moment. Its
implementation for AF_SMC will follow.
Regards, Ursula Braun
On 01/10/2017 12:59 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> n
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit f09d1886a41e9063b43da493ef0e845ac8afd2fa upstream.
The write URB was being killed using the synchronous interface while
holding a spin lock in close().
Simply drop the lock
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Lu Baolu
commit 2b985467371a58ae44d76c7ba12b0951fee6ed98 upstream.
handle_cmd_completion() frees a command structure which might be still
referenced by xhci->current_cmd.
This might cause probl
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit a5bc01949e3b19d8a23b5eabc6fc71bb50dc820e upstream.
Fix NULL-pointer dereferences at open() and disconnect() should the
device lack the expected bulk-out endpoints:
Unable t
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit 346e99736c3ce328fd42d678343b70243aca5f36 upstream.
If a device is unplugged and replugged during Sx system suspend
some Intel xHC hosts will overwrite the CAS (Cold attach
Ingo, Thomas,
Please pull the vtime/accumulate-for-tip branch that can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
vtime/accumulate-for-tip
HEAD: 0fe66425659da25269280c106f39b333a0cfb9a9
---
The cputime accounting functions (account_system_time
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Felipe Balbi
commit e71d363d9c611c99fb78f53bfee99616e7fe352c upstream.
Now that we're handling so many transfers at a time
and for some dwc3 revisions LPM events *must* be
enabled, we can fall
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit cc0909248258f679c4bb4cd315565d40abaf6bc6 upstream.
Fix NULL-pointer dereference in open() should the device lack the
expected endpoints:
Unable to handle kernel NULL pointe
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ioan-Adrian Ratiu
commit 1d0f953086f090a022f2c0e1448300c15372db46 upstream.
Commit 16200948d83 ("ALSA: usb-audio: Fix race at stopping the stream") was
incomplete causing another more severe ke
On 10/01/2017 at 14:18:32 +0100, Peter Rosin wrote :
> Hi!
>
> changes v5 -> v6
> - drop the &main clock-frequency
> - add some text to the commit messages
> - make config additions modules
>
> changes v4 -> v5
> - comment from Rob about the memory node made me look closer and
> the memory size
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Baolin Wang
commit 2a7cfdf37b7c08ac29df4c62ea5ccb01474b6597 upstream.
When current command was supposed to be aborted, host will free the command
in handle_cmd_completion() function. But it mig
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 85bcf96caba8b4a7c080638629ba3c67ea0c upstream.
ASUS ROG Ranger VIII with ALC1150 codec requires the extra GPIO pin to
up for the front panel. Just use the existing fixu
On Fri, Jan 6, 2017 at 8:41 AM, Clemens Gruber
wrote:
> Hi,
>
> with the current mainline 4.10-rc2 kernel, I can no longer boot from
> the eMMC on my i.MX6Q board.
>
> Details:
> The eMMC is a Micron MTFC4GACAJCN-1M WT but as the i.MX6Q only supports
> eMMC 4.41 features and we did not implement v
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit 0a8fd1346254974c3a852338508e4a4cddbb35f1 upstream.
When checking a new device's descriptors, the USB core does not check
for duplicate endpoint addresses. This can cause a pr
501 - 600 of 1266 matches
Mail list logo
