3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Joerg Roedel
commit cbf3ccd09d683abf1cacd36e3640872ee912d99b upstream.
During device assignment/deassignment the flags in the DTE
get lost, which might cause spurious faults, for example
when
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Thornber
commit 2871c69e025e8bc507651d5a9cf81a8a7da9d24b upstream.
Commit 4c7e309340ff ("dm btree remove: fix bug in redistribute3") wasn't
a complete fix for redistribute3().
The
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Charles Keepax
commit 97aff2c03a1e4d343266adadb52313613efb027f upstream.
There are 24 EQ registers not 25, I suspect this bug came about because
the registers start at EQ1 not zero. The bug
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Snitzer
commit 4dcb8b57df3593dcb20481d9d6cf79d1dc1534be upstream.
btree_split_beneath()'s error path had an outstanding FIXME that speaks
directly to the potential for _not_ cleaning up
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit 3b4739b8951d650becbcd855d7d6f18ac98a9a85 upstream.
If a host fails to wake up a isochronous SuperSpeed device from U1/U2
in time for a isoch transfer it will generate a
On 06/11/15 11:49, Kapil Hali wrote:
> Add SMP support for Broadcom's Northstar Plus SoC
> cpu enable method. This changes also consolidates
> iProc family's - BCM NSP and BCM Kona, platform
> SMP handling in a common file.
>
> Northstar Plus SoC is based on ARM Cortex-A9
> revision r3p0 which
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Dryomov
commit 1f2c6651f69c14d0d3a9cfbda44ea101b02160ba upstream.
Currently we leak parent_spec and trigger a "parent reference
underflow" warning if rbd_dev_create() in
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit f5f3497cad8c8416a74b9aaceb127908755d020a upstream.
On 32-bit systems, the initial_page_table is reused by
efi_call_phys_prolog as an identity map to call
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 275d7d44d802ef271a42dc87ac091a495ba72fc5 upstream.
Poma (on the way to another bug) reported an assertion triggering:
[] module_assert_mutex_or_preempt+0x49/0x90
[]
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit 3fc89adb9fa4beff31374a4bf50b3d099d88ae83 upstream.
Currently a number of Crypto API operations may fail when a signal
occurs. This causes nasty problems as the caller of
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jes Sorensen
commit 203d27b0226a05202438ddb39ef0ef1acb14a759 upstream.
This was introduced with 9e882242c6193ae6f416f2d8d8db0d9126bd996b
which changed the return value of submit_bio_wait() to
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Laura Abbott
commit fd7cd061adcf5f7503515ba52b6a724642a839c8 upstream.
We received several reports of systems rebooting and powering on
after an attempted shutdown. Testing showed that
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jes Sorensen
commit 681ab4696062f5aa939c9e04d058732306a97176 upstream.
This was introduced with 9e882242c6193ae6f416f2d8d8db0d9126bd996b
which changed the return value of submit_bio_wait() to
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ronny Hegewald
commit bae818ee1577c27356093901a0ea48f672eda514 upstream.
rbd requires stable pages, as it performs a crc of the page data before
they are send to the OSDs.
But since kernel
On Mon, 5 Oct 2015, Petr Mladek wrote:
> WORK_STRUCT_PENDING is a mask for testing the pending bit.
> test_bit() expects the number of the bit and we need to
> use WORK_STRUCT_PENDING_BIT there.
>
> Also work_data_bits() is defined in workqueues.h now.
>
> I have noticed this just by chance
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Roman Gushchin
commit b8a9d66d043ffac116100775a469f05f5158c16f upstream.
After commit 566c09c53455 ("raid5: relieve lock contention in
get_active_stripe()")
__find_stripe() is called under
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit d01552a76d71f9879af448e9142389ee9be6e95b upstream.
This reverts commit 7eb418851f3278de67126ea0c427641ab4792c57.
This commit is poorly justified, I can find not discusison
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Doron Tsur
commit 0ca81a2840f77855bbad1b9f172c545c4dc9e6a4 upstream.
ib_send_cm_sidr_rep could sometimes erase the node from the sidr
(depending on errors in the process). Since
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Soeren Grunewald
commit be32c0cf0462c36f482b5ddcff1d8371be1e183c upstream.
The Exar XR17V358 can also be combined with a XR17V354 chip to act as a
single 12 port chip. This works the same way
On Thu, Nov 5, 2015 at 2:23 PM, Guenter Roeck wrote:
> On Thu, Nov 05, 2015 at 04:19:21PM -0500, Akshay Bhat wrote:
>> From: Tim Harvey
>>
>> The IMX6 watchdog supports assertion of a signal (WDOG_B) which
>> can be pinmux'd to an external pin. This is typically used for boards that
>> have
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Soeren Grunewald
commit 96a5d18bc1338786fecac73599f1681f59a59a8e upstream.
The Exar XR17V358 chip usually provides only 8 ports. But two chips can be
combined to act as a single 16 port chip.
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Dryomov
commit 6d69bb536bac0d403d83db1ca841444981b280cd upstream.
Mapping an image with a long parent chain (e.g. image foo, whose parent
is bar, whose parent is baz, etc) currently
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 296291cdd1629c308114504b850dc343eabc2782 upstream.
Currently a simple program below issues a sendfile(2) system call which
takes about 62 days to complete in my test KVM
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ilia Mirkin
commit 2a6c521bb41ce862e43db46f52e7681d33e8d771 upstream.
On nv50+, we restrict the valid domains to just the one where the buffer
was originally created. However after the buffer
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Vasant Hegde
commit 8832317f662c06f5c06e638f57bfe89a71c9b266 upstream.
Currently we do not validate rtas.entry before calling enter_rtas(). This
leads to a kernel oops when user space calls
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 49abb26651167c892393cd9f2ad23df429645ed9 upstream.
Fixes a harmless error message caused by:
51a4726b04e880fdd9b4e0e58b13f70b0a68a7f5
Signed-off-by: Alex Deucher
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 029cd0370241641eb70235d205aa0b90c84dce44 upstream.
ath9k inserts padding between the 802.11 header and the data area (to
align it). Since it didn't declare this extra
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Ronny Hegewald
commit bae818ee1577c27356093901a0ea48f672eda514 upstream.
rbd requires stable pages, as it performs a crc of the page data before
they are send to the OSDs.
But since kernel
Add a compatible string "brcm,bcm-nsp-smp" for Broadcom's
Northstar Plus CPU to the 32-bit ARM CPU device tree binding
documentation file and create a new binding documentation for
Northstar Plus CPU.
Signed-off-by: Kapil Hali
---
.../bindings/arm/bcm/brcm,nsp-cpu-method.txt | 36
From: Jon Mason
Add SMP support for Broadcom's 4708 SoCs.
Signed-off-by: Jon Mason
Acked-by: Hauke Mehrtens
Tested-by: Hauke Mehrtens
Signed-off-by: Kapil Hali
---
arch/arm/boot/dts/bcm4708.dtsi | 2 ++
arch/arm/mach-bcm/Kconfig | 1 +
arch/arm/mach-bcm/Makefile | 3 +++
3 files
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 9702970c7bd3e2d6fecb642a190269131d4ac16c upstream.
This reverts commit e306dfd06fcb44d21c80acb8e5a88d55f3d1cf63.
With this patch applied, we were the only architecture
Add device tree changes required for providing SMP support
for Broadcom Northstar Plus SoC.
Signed-off-by: Kapil Hali
---
arch/arm/boot/dts/bcm-nsp.dtsi | 33 +
1 file changed, 21 insertions(+), 12 deletions(-)
diff --git a/arch/arm/boot/dts/bcm-nsp.dtsi
This is the second iteration in the series.
Changes in v2:
Removed the pen_holding method of SMP bringup for NSP SoC and
replaced it with simple wakeup of secondary core using ARM IPI.
This series adds SMP support for Broadcom's Northstar Plus SoC.
There are similar SMP enablement methods for
Add SMP support for Broadcom's Northstar Plus SoC
cpu enable method. This changes also consolidates
iProc family's - BCM NSP and BCM Kona, platform
SMP handling in a common file.
Northstar Plus SoC is based on ARM Cortex-A9
revision r3p0 which requires configuration for ARM
Errata 764369 for SMP.
3.14-stable review patch. If anyone has any objections, please let me know.
--
Fixes the backport of 0b34a166f291d255755be46e43ed5497cdd194f2 upstream
Commit 0b34a166f291d255755be46e43ed5497cdd194f2 "x86/xen: Support
kexec/kdump in HVM guests by doing a soft reset" has been
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit 3b4739b8951d650becbcd855d7d6f18ac98a9a85 upstream.
If a host fails to wake up a isochronous SuperSpeed device from U1/U2
in time for a isoch transfer it will generate a
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Snitzer
commit 4dcb8b57df3593dcb20481d9d6cf79d1dc1534be upstream.
btree_split_beneath()'s error path had an outstanding FIXME that speaks
directly to the potential for _not_ cleaning up
On Fri, Nov 06, 2015 at 08:33:15PM +0100, Borislav Petkov wrote:
> Hi Greg,
>
> this one is b0rked and a proper fix is still being discussed. You should
> drop it from the queue.
Thanks for letting me know, now dropped from all trees. If it ever gets
fixed up, please resend the git commit ids
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Cathy Avery
commit a54c8f0f2d7df525ff997e2afe71866a1a013064 upstream.
xen-blkfront will crash if the check to talk_to_blkback()
in blkback_changed()(XenbusStateInitWait) returns an error.
The
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Thornber
commit 2871c69e025e8bc507651d5a9cf81a8a7da9d24b upstream.
Commit 4c7e309340ff ("dm btree remove: fix bug in redistribute3") wasn't
a complete fix for redistribute3().
The
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Dryomov
commit 1f2c6651f69c14d0d3a9cfbda44ea101b02160ba upstream.
Currently we leak parent_spec and trigger a "parent reference
underflow" warning if rbd_dev_create() in
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 275d7d44d802ef271a42dc87ac091a495ba72fc5 upstream.
Poma (on the way to another bug) reported an assertion triggering:
[] module_assert_mutex_or_preempt+0x49/0x90
[]
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit 3fc89adb9fa4beff31374a4bf50b3d099d88ae83 upstream.
Currently a number of Crypto API operations may fail when a signal
occurs. This causes nasty problems as the caller of
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Jes Sorensen
commit 681ab4696062f5aa939c9e04d058732306a97176 upstream.
This was introduced with 9e882242c6193ae6f416f2d8d8db0d9126bd996b
which changed the return value of submit_bio_wait() to
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Jes Sorensen
commit 203d27b0226a05202438ddb39ef0ef1acb14a759 upstream.
This was introduced with 9e882242c6193ae6f416f2d8d8db0d9126bd996b
which changed the return value of submit_bio_wait() to
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 5bd166872d8f99f156fac191299d24f828bb2348 upstream.
The code to send the RX PN data (for each TID) to the firmware
has a devastating bug: it overwrites the data for TID 0
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Doron Tsur
commit 0ca81a2840f77855bbad1b9f172c545c4dc9e6a4 upstream.
ib_send_cm_sidr_rep could sometimes erase the node from the sidr
(depending on errors in the process). Since
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 2cf5eb3ab7bb7f2e3a70edcef236cd62c87db030 upstream.
The code to send the RX PN data (for each TID) to the firmware
has a devastating bug: it overwrites the data for TID 0
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Dryomov
commit 6d69bb536bac0d403d83db1ca841444981b280cd upstream.
Mapping an image with a long parent chain (e.g. image foo, whose parent
is bar, whose parent is baz, etc) currently
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Charles Keepax
commit 97aff2c03a1e4d343266adadb52313613efb027f upstream.
There are 24 EQ registers not 25, I suspect this bug came about because
the registers start at EQ1 not zero. The bug
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit f5f3497cad8c8416a74b9aaceb127908755d020a upstream.
On 32-bit systems, the initial_page_table is reused by
efi_call_phys_prolog as an identity map to call
Hi,
On Sat, Oct 31, 2015 at 06:28:16PM +0800, Chen-Yu Tsai wrote:
> Hi,
>
> On Fri, Oct 30, 2015 at 10:20 PM, Maxime Ripard
> wrote:
> > The A10 SoCs and its relatives has a special clock controller to drive the
> > display engines (both frontend and backend).
> >
> > Add a driver for it.
> >
>
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Joerg Roedel
commit cbf3ccd09d683abf1cacd36e3640872ee912d99b upstream.
During device assignment/deassignment the flags in the DTE
get lost, which might cause spurious faults, for example
when
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Ilia Mirkin
commit 2a6c521bb41ce862e43db46f52e7681d33e8d771 upstream.
On nv50+, we restrict the valid domains to just the one where the buffer
was originally created. However after the buffer
This is the start of the stable review cycle for the 3.10.93 release.
There are 24 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 Sun Nov 8 19:23:41 UTC 2015.
Anything
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 296291cdd1629c308114504b850dc343eabc2782 upstream.
Currently a simple program below issues a sendfile(2) system call which
takes about 62 days to complete in my test KVM
4.2-stable review patch. If anyone has any objections, please let me know.
--
Fixes the backport of 0b34a166f291d255755be46e43ed5497cdd194f2 upstream
Commit 0b34a166f291d255755be46e43ed5497cdd194f2 "x86/xen: Support
kexec/kdump in HVM guests by doing a soft reset" has been
On Fri, Nov 06, 2015 at 11:31:30AM -0800, Florian Fainelli wrote:
> DSA expects the mii_bus pointer to be the device structure associated
> with the MDIO bus controller driver. First commit breaking that was
> c3a07134e6aa ("mv643xx_eth: convert to use the Marvell Orion MDIO
> driver"), and then,
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Vasant Hegde
commit 8832317f662c06f5c06e638f57bfe89a71c9b266 upstream.
Currently we do not validate rtas.entry before calling enter_rtas(). This
leads to a kernel oops when user space calls
3.10-stable review patch. If anyone has any objections, please let me know.
--
Fixes the backport of 0b34a166f291d255755be46e43ed5497cdd194f2 upstream
Commit 0b34a166f291d255755be46e43ed5497cdd194f2 "x86/xen: Support
kexec/kdump in HVM guests by doing a soft reset" has been
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Cathy Avery
commit a54c8f0f2d7df525ff997e2afe71866a1a013064 upstream.
xen-blkfront will crash if the check to talk_to_blkback()
in blkback_changed()(XenbusStateInitWait) returns an error.
The
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Hellstrom
commit 54c12bc374408faddbff75dbf1a6167c19af39c4 upstream.
If user space calls unreference on a user_dmabuf it will typically
kill the struct ttm_base_object member which is
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Lucas Stach
commit 209da39154837ec1b69fb34f438041939911e4b4 upstream.
The LIC doesn't deal with the different types of interrupts itself
but needs to forward calls to set the appropriate type
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Mika Westerberg
commit 39ce8150a079e3ae6ed9abf26d7918a558ef7c19 upstream.
There is a hardware issue in Intel Baytrail where concurrent GPIO register
access might result reads of 0x and
On Thu, Nov 5, 2015 at 7:18 AM, Caesar Wang wrote:
> The RK3368 SoCs support to 2 channel TS-ADC, the temperature criteria
> of each channel can be configurable.
>
> The system has two Temperature Sensors, channel 0 is for CPU,
> and channel 1 is for GPU.
>
> Signed-off-by: Caesar Wang
> ---
>
>
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Minchan Kim
commit 47aee4d8e314384807e98b67ade07f6da476aa75 upstream.
Use is_zero_pfn() on pteval only after pte_present() check on pteval
(It might be better idea to introduce is_zero_pte()
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Mika Westerberg
commit 78e1c896932df5b8bcdff7bf5417d8e72a4d0d6b upstream.
The Intel Baytrail pinctrl driver implements irqchip callbacks which are
called with desc->lock raw_spinlock held. In
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Soeren Grunewald
commit be32c0cf0462c36f482b5ddcff1d8371be1e183c upstream.
The Exar XR17V358 can also be combined with a XR17V354 chip to act as a
single 12 port chip. This works the same way
4.1-stable review patch. If anyone has any objections, please let me know.
--
Fixes the backport of 0b34a166f291d255755be46e43ed5497cdd194f2 upstream
Commit 0b34a166f291d255755be46e43ed5497cdd194f2 "x86/xen: Support
kexec/kdump in HVM guests by doing a soft reset" has been
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Ronny Hegewald
commit bae818ee1577c27356093901a0ea48f672eda514 upstream.
rbd requires stable pages, as it performs a crc of the page data before
they are send to the OSDs.
But since kernel
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Dong Aisheng
commit 89c1a8cf63f8c69dfddb6e377c04df8b25ab1c88 upstream.
cd-gpios polarity should be changed to GPIO_ACTIVE_LOW and wp-gpios
should be changed to GPIO_ACTIVE_HIGH.
Otherwise, the
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Walleij
commit 22869a9eca4ea5b534538d160b68c7aef44e378a upstream.
This defines a new compatible option for MFD devices "simple-mfd" that will
make the OF core spawn child devices for all
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Doron Tsur
commit 0ca81a2840f77855bbad1b9f172c545c4dc9e6a4 upstream.
ib_send_cm_sidr_rep could sometimes erase the node from the sidr
(depending on errors in the process). Since
Hi Gregory,
> I also choose to associate all the TX queues on the same CPU that the
> one associated to the RX queue. It allows to contain all the
> interrupts on the same CPU. I think that an improvement on this side
> would be the support of the XPS.
>
Did you make some tries? E.g. after
Hi Chen-Yu,
On Fri, Oct 30, 2015 at 11:20:41PM +0800, Chen-Yu Tsai wrote:
> On Fri, Oct 30, 2015 at 10:21 PM, Maxime Ripard
> wrote:
> > The TV encoder is used to drive VGA and composite display.
> >
> > Enable it on the CHIP
>
> The commit message does not match the contents. Missing a patch?
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Christian Engelmayer
commit 0f89abf56abbd0e1c6e3cef9813e6d9f05383c1e upstream.
Commit 8eb934591f8b ("btrfs: check unsupported filters in balance
arguments") adds a jump to exit label out_bargs
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Srinivas Pandruvada
commit 8e601a9f97a00bab031980de34f9a81891c1f82f upstream.
This is a workaround for KNL platform, where in some cases MPERF counter
will not have updated value before next
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Sudeep Holla
commit af391b15f7b56ce19f52862d36595637dd42b575 upstream.
This patch renames __cpu_suspend to cpu_suspend so that it's aligned
with ARM32. It also removes the redundant wrapper
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Lorenzo Pieralisi
commit e13d918a19a7b6cba62b32884f5e336e764c2cc6 upstream.
Commit dd006da21646 ("arm64: mm: increase VA range of identity map")
introduced a mechanism to extend the virtual
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 029cd0370241641eb70235d205aa0b90c84dce44 upstream.
ath9k inserts padding between the 802.11 header and the data area (to
align it). Since it didn't declare this extra
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Keith Busch
commit 0dfc70c33409afc232ef0b9ec210535dfbf9bc61 upstream.
Resources are reallocated for requeued commands, so unmap and release
the iod for the failed command.
It's a pretty bad
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Seth Jennings
commit 2900ea609616c2651dec65312beeb2a6e536bc50 upstream.
In commit
7d375bffa524 ("sb_edac: Fix support for systems with two home agents per
socket")
NUM_CHANNELS was
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 5bd166872d8f99f156fac191299d24f828bb2348 upstream.
The code to send the RX PN data (for each TID) to the firmware
has a devastating bug: it overwrites the data for TID 0
With x86_64_defconfig:
GCC thinks that in nfulnl_recv_config flags parameter is not inited but
it was under the same condition (nfula[NFULA_CFG_FLAGS] == true).
Suppress this warning:
net/netfilter/nfnetlink_log.c: In function ‘nfulnl_recv_config’:
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 2cf5eb3ab7bb7f2e3a70edcef236cd62c87db030 upstream.
The code to send the RX PN data (for each TID) to the firmware
has a devastating bug: it overwrites the data for TID 0
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit b5a48134f8af08f5243328f8a0b05fc5ae7cf343 upstream.
The MODULE_FIRMWARE() for 3160 should be using the 7260 version as
it's done in the device configuration struct instead
Hi Greg,
this one is b0rked and a proper fix is still being discussed. You should
drop it from the queue.
On Fri, Nov 06, 2015 at 11:18:38AM -0800, Greg Kroah-Hartman wrote:
> 4.2-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Paolo
On 06/11/15 11:19, Greg Kroah-Hartman wrote:
> 4.2-stable review patch. If anyone has any objections, please let me know.
Thanks this patch is also applicable all the way down to 3.18. I have
sent a reply for the 3.10 through 3.17 kernels as the structure member
had a slightly different name.
>
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Luca Coelho
commit f08f625876476b6c4a87834dc86e3b927f4697d2 upstream.
Add 3 new subdevice IDs for the 0x095A device ID and 2 for the 0x095B
device ID.
Reported-by: Jeremy
Signed-off-by:
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 589cb22bbedacf325951014c07a35a2b01ca57f6 upstream.
If the STXR instruction fails in the SWP emulation code, we leave *data
overwritten with the loaded value, therefore
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Arik Nemtsov
commit 1a3fe0b2b6778b7866e2b3f5c9a299d5e9bbd89c upstream.
During the CT-kill exit flow, the card is powered up and partially
initialized to check if the temperature is already low
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Dryomov
commit 1f2c6651f69c14d0d3a9cfbda44ea101b02160ba upstream.
Currently we leak parent_spec and trigger a "parent reference
underflow" warning if rbd_dev_create() in
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Dryomov
commit 6d69bb536bac0d403d83db1ca841444981b280cd upstream.
Mapping an image with a long parent chain (e.g. image foo, whose parent
is bar, whose parent is baz, etc) currently leads
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Luca Abeni
commit 5aa5050787f449e7eaef2c5ec93c7b357aa7dcdc upstream.
Commit:
9d5142624256 ("sched/deadline: Reduce rq lock contention by eliminating
locking of non-feasible target")
broke
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Larry Finger
commit 54328e64047a54b8fc2362c2e1f0fa16c90f739f upstream.
In commit 1277fa2ab2f9 ("rtlwifi: Remove the clear interrupt routine from all
drivers"), the code that cleared all
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Konstantin Khlebnikov
commit 5ffdbe8bf1e485026e1c7e4714d2841553cf0b40 upstream.
This fixes memory leak after umount.
Kmemleak report:
unreferenced object 0x8800ba791010 (size 8):
comm
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Konstantin Khlebnikov
commit 0f95502ad84874b3c05fc7cdd9d4d9d5cddf7859 upstream.
This fixes small memory leak after mount.
Kmemleak report:
unreferenced object 0x88003683fe00 (size 16):
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: David Howells
commit 0480334fa60488d12ae101a02d7d9e1a3d03d7dd upstream.
Open the lower file with O_LARGEFILE in ovl_copy_up().
Pass O_LARGEFILE unconditionally in ovl_copy_up_data() as it's
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Alim Akhtar
commit b8bb9baad27e455c467e8fac47eebadbe765c18f upstream.
Since commit 2fad972d45c4 ("ARM: dts: Add mclk entry for Peach boards"),
sound card detection is broken on peach boards
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit b02176f30cd30acccd3b633ab7d9aed8b5da52ff upstream.
bdi's are initialized in two steps, bdi_init() and bdi_register(), but
destroyed in a single step by bdi_destroy() which,
401 - 500 of 1954 matches
Mail list logo
