[PATCH 4.3 0/2] 4.3.2-stable review

This is the start of the stable review cycle for the 4.3.2 release. There are 2 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 Fri Dec 11 18:02:18 UTC 2015. Anything received

Re: [PATCH] kvm: x86: move tracepoints outside extended quiescent state

On Thu, Dec 10, 2015 at 06:38:57PM +0100, Paolo Bonzini wrote: > Invoking tracepoints within kvm_guest_enter/kvm_guest_exit causes a > lockdep splat. > > Cc: stable@vger.kernel.org > Reported-by: Borislav Petkov > Signed-off-by: Paolo Bonzini > --- >

Re: [PATCH] arm64: mm: ensure that the zero page is visible to the page table walker

Hi Will, On Thu, Dec 10, 2015 at 05:39:59PM +, Will Deacon wrote: > In paging_init, we allocate the zero page, memset it to zero and then > point TTBR0 to it in order to avoid speculative fetches through the > identity mapping. > > In order to guarantee that the freshly zeroed page is indeed

[PATCH] kvm: x86: move tracepoints outside extended quiescent state

Invoking tracepoints within kvm_guest_enter/kvm_guest_exit causes a lockdep splat. Cc: stable@vger.kernel.org Reported-by: Borislav Petkov Signed-off-by: Paolo Bonzini --- arch/x86/kvm/svm.c | 4 ++-- arch/x86/kvm/vmx.c | 3 ++- arch/x86/kvm/x86.c | 2 +- 3

[PATCH] arm64: mm: ensure that the zero page is visible to the page table walker

In paging_init, we allocate the zero page, memset it to zero and then point TTBR0 to it in order to avoid speculative fetches through the identity mapping. In order to guarantee that the freshly zeroed page is indeed visible to the page table walker, we need to execute a dsb instruction prior to

Re: [PATCH] X.509: Fix the time validation [ver #3]

Am 12.11.2015 um 12:38 schrieb David Howells: This fixes CVE-2015-5327. It affects kernels from 4.3-rc1 onwards. Fix the X.509 time validation to use month number-1 when looking up the number of days in that month. Also put the month number validation before doing the lookup so as not to risk

Re: [Intel-gfx] [PATCH v2] drm/i915: Do a better job at disabling primary plane in the noatomic case.

On Mon, Nov 23, 2015 at 10:25:28AM +0100, Maarten Lankhorst wrote: > Op 13-11-15 om 14:28 schreef Ander Conselvan De Oliveira: > > On Thu, 2015-11-12 at 14:58 +0100, Maarten Lankhorst wrote: > >> Op 12-11-15 om 14:37 schreef Ander Conselvan De Oliveira: > >>> On Wed, 2015-11-11 at 15:36 +0100,

[PATCH v4 01/58] mtd: nand: denali: add missing nand_release() call in denali_remove()

Unregister the NAND device from the NAND subsystem when removing a denali NAND controller, otherwise the MTD attached to the NAND device is still exposed by the MTD layer, and accesses to this device will likely crash the system. Signed-off-by: Boris Brezillon

Re: [PATCH v2] wlcore/wl12xx: spi: fix oops on firmware load

Sorry, sent out by mistake. On 12/10/2015 09:38 AM, Uri Mashiach wrote: The maximum chunks used by the function is (SPI_AGGR_BUFFER_SIZE / WSPI_MAX_CHUNK_SIZE + 1). The original commands array had space for (SPI_AGGR_BUFFER_SIZE / WSPI_MAX_CHUNK_SIZE) commands. When the last chunk is used (len

Re: [Intel-gfx] [PATCH] drm/i915: Unbreak check_digital_port_conflicts()

On Mon, Dec 07, 2015 at 11:13:20PM +0200, ville.syrj...@linux.intel.com wrote: > From: Ville Syrjälä > > Atomic changes broke check_digital_port_conflicts(). It needs to look > at the global situation instead of just trying to find a conflict > within the current

Re: ARM: socfpga: fix build error due to secondary_startup

On 12/07/2015 09:57 AM, Dinh Nguyen wrote: > On 12/05/2015 11:50 PM, Greg KH wrote: >> On Fri, Dec 04, 2015 at 11:32:21AM -0600, Dinh Nguyen wrote: >>> Hi, >>> >>> Please apply the following patch to v4.1.13: >>> >>> commit 4d268234f6611c4b8b6cd7036d10bd22da97c04a >>> Author: Kevin Hilman

Re: [PATCH 1/7] drm: Don't overwrite UNVERFIED mode status to OK

On Fri, Dec 04, 2015 at 09:17:28AM +0100, Daniel Vetter wrote: > On Thu, Dec 03, 2015 at 11:14:09PM +0200, ville.syrj...@linux.intel.com wrote: > > From: Ville Syrjälä > > > > The way the mode probing works is this: > > 1. All modes currently on the mode list are

Re: [PATCH 4.3 0/2] 4.3.2-stable review

On 12/10/2015 11:03 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.3.2 release. > There are 2 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

Re: [PATCH 4.3 0/2] 4.3.2-stable review

On Thu, Dec 10, 2015 at 01:58:43PM -0700, Shuah Khan wrote: > On 12/10/2015 11:03 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.3.2 release. > > There are 2 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.3 0/2] 4.3.2-stable review

On Thu, Dec 10, 2015 at 01:03:46PM -0500, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.3.2 release. > There are 2 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.

[to-be-updated] ocfs2-dlm-fix-deadlock-due-to-nested-lock.patch removed from -mm tree

The patch titled Subject: ocfs2: dlm: fix deadlock due to nested lock has been removed from the -mm tree. Its filename was ocfs2-dlm-fix-deadlock-due-to-nested-lock.patch This patch was dropped because an updated version will be merged

Re: [PATCH v4 01/58] mtd: nand: denali: add missing nand_release() call in denali_remove()

On Thu, Dec 10, 2015 at 08:59:45AM +0100, Boris Brezillon wrote: > Unregister the NAND device from the NAND subsystem when removing a denali > NAND controller, otherwise the MTD attached to the NAND device is still > exposed by the MTD layer, and accesses to this device will likely crash > the

Re: [PATCH] ideapad-laptop: Add Lenovo ideapad Y700-17ISK to no_hw_rfkill dmi list

On Wed, Dec 09, 2015 at 09:12:52PM -0500, Josh Boyer wrote: > One of the newest ideapad models also lacks a physical hw rfkill switch, > and trying to read the hw rfkill switch through the ideapad module > causes it to always reported blocking breaking wifi. > > Fix it by adding this model to the

Re: Linux 4.3.2

diff --git a/Makefile b/Makefile index 266eeacc1490..1a4953b3e10f 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 3 -SUBLEVEL = 1 +SUBLEVEL = 2 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/crypto/asymmetric_keys/x509_cert_parser.c

Re: [PATCH 4.3 0/2] 4.3.2-stable review

On Thu, Dec 10, 2015 at 01:48:28PM -0800, Guenter Roeck wrote: > On Thu, Dec 10, 2015 at 01:03:46PM -0500, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.3.2 release. > > There are 2 patches in this series, all will be posted as a response > > to this one. If

Linux 4.3.2

I'm announcing the release of the 4.3.2 kernel. This release fixes a bug with regards to X.509 certificates, more details can be found in the commit log. If you don't use these certificates, no need to upgrade from 4.3.1. Note, the bug is also in 4.3.0, it is not new in 4.3.1. The updated

Re: [Intel-gfx] [PATCH] drm/i915: Unbreak check_digital_port_conflicts()

On Thu, 10 Dec 2015, Daniel Vetter wrote: > On Mon, Dec 07, 2015 at 11:13:20PM +0200, ville.syrj...@linux.intel.com wrote: >> From: Ville Syrjälä >> >> Atomic changes broke check_digital_port_conflicts(). It needs to look >> at the global

Re: Linux 4.3.1

On Thu, Dec 10, 2015 at 06:12:17PM +0100, Jörg-Volker Peetz wrote: > Greg KH wrote on 12/09/15 21:16: > > I'm announcing the release of the 4.3.1 kernel. > > > > All users of the 4.3 kernel series must upgrade. > > > > The updated 4.3.y git tree can be found at: > >

Re: [PATCH 4.3 0/2] 4.3.2-stable review

On Thu, Dec 10, 2015 at 07:38:47PM +0100, Alexander Holler wrote: > Am 10.12.2015 um 19:03 schrieb Greg Kroah-Hartman: > >This is the start of the stable review cycle for the 4.3.2 release. > >There are 2 patches in this series, all will be posted as a response > >to this one. If anyone has any

[PATCH v2] kvm: x86: move tracepoints outside extended quiescent state

Invoking tracepoints within kvm_guest_enter/kvm_guest_exit causes a lockdep splat. Cc: stable@vger.kernel.org Reported-by: Borislav Petkov Signed-off-by: Paolo Bonzini --- arch/x86/kvm/svm.c | 4 ++-- arch/x86/kvm/vmx.c | 3 ++- arch/x86/kvm/x86.c | 4 ++--

[PATCH 4.3 1/2] crypto: asymmetric_keys - remove always false comparison

4.3-stable review patch. If anyone has any objections, please let me know. -- From: sudip commit 4dd17c9c8a30c8d8cd1c9d4b94f08aca4b038d3e upstream. hour, min and sec are unsigned int and they can never be less than zero. Signed-off-by: Sudip

Re: [PATCH] kvm: x86: move tracepoints outside extended quiescent state

On 10/12/2015 19:09, Borislav Petkov wrote: > On Thu, Dec 10, 2015 at 06:38:57PM +0100, Paolo Bonzini wrote: >> Invoking tracepoints within kvm_guest_enter/kvm_guest_exit causes a >> lockdep splat. >> >> Cc: stable@vger.kernel.org >> Reported-by: Borislav Petkov >>

Re: [PATCH] X.509: Fix the time validation [ver #3]

On Thu, Dec 10, 2015 at 07:00:46PM +0100, Alexander Holler wrote: > Am 10.12.2015 um 16:34 schrieb Alexander Holler: > >Am 10.12.2015 um 16:26 schrieb Greg Kroah-Hartman: > >>On Thu, Dec 10, 2015 at 04:15:22PM +0100, Alexander Holler wrote: > > > >>>Just in case of, I would suggest to quickly push

Re: [PATCH] X.509: Fix the time validation [ver #3]

Am 10.12.2015 um 19:09 schrieb Greg Kroah-Hartman: We already have one other report of this problem hitting them. I've now released 4.3.2-rc1, with a "quick" review period of 24 hours before I release 4.3.2 with just this fix. If you could verify I didn't mess anything up I would appreciate

Re: [PATCH] X.509: Fix the time validation [ver #3]

Am 10.12.2015 um 16:34 schrieb Alexander Holler: Am 10.12.2015 um 16:26 schrieb Greg Kroah-Hartman: On Thu, Dec 10, 2015 at 04:15:22PM +0100, Alexander Holler wrote: Just in case of, I would suggest to quickly push out 4.3.2 (only 4.3 seems to be affected) which contains at least the patch

[PATCH 4.3 2/2] X.509: Fix the time validation [ver #2]

4.3-stable review patch. If anyone has any objections, please let me know. -- From: David Howells commit cc25b994acfbc901429da682d0f73c190e960206 upstream. This fixes CVE-2015-5327. It affects kernels from 4.3-rc1 onwards. Fix the X.509 time validation

[PATCH] jffs2: bug fix of creating node when gc or find space

From: gaoyongliang 1. create inode by insert_inode_locked, and return inode with I_NEW. 2. has writed the dnode successfully in the end of one block, then release the c->alloc_sem, but the dirent is not written yet. 3. the gc or jffs2_reserve_space which has got the

Re: [PATCH] jffs2: bug fix of creating node when gc or find space

+ David (JFFS2 "maintainer") David, Looks like there was a similar patch / bug report from Huawei about a year ago, though this one has some modifications: http://patchwork.ozlabs.org/patch/416301/ It's among the outstanding jffs2 patches from the last 2 years, after I filtered out the noise:

Re: [Intel-gfx] [PATCH v2] drm/i915: Do a better job at disabling primary plane in the noatomic case.

On Thu, 10 Dec 2015, Daniel Vetter wrote: > On Mon, Nov 23, 2015 at 10:25:28AM +0100, Maarten Lankhorst wrote: >> Op 13-11-15 om 14:28 schreef Ander Conselvan De Oliveira: >> > On Thu, 2015-11-12 at 14:58 +0100, Maarten Lankhorst wrote: >> >> Op 12-11-15 om 14:37 schreef Ander

Re: [Intel-gfx] [PATCH] drm/i915: Unbreak check_digital_port_conflicts()

On Thu, Dec 10, 2015 at 01:39:47PM +0200, Jani Nikula wrote: > On Thu, 10 Dec 2015, Daniel Vetter wrote: > > On Mon, Dec 07, 2015 at 11:13:20PM +0200, ville.syrj...@linux.intel.com > > wrote: > >> From: Ville Syrjälä > >> > >> Atomic changes

Re: Linux 4.3.1

Greg KH wrote on 12/09/15 21:16: > I'm announcing the release of the 4.3.1 kernel. > > All users of the 4.3 kernel series must upgrade. > > The updated 4.3.y git tree can be found at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git > linux-4.3.y > and can be

Patch "crypto: asymmetric_keys - remove always false comparison" has been added to the 4.3-stable tree

This is a note to let you know that I've just added the patch titled crypto: asymmetric_keys - remove always false comparison to the 4.3-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is:

Patch "X.509: Fix the time validation [ver #2]" has been added to the 4.3-stable tree

This is a note to let you know that I've just added the patch titled X.509: Fix the time validation [ver #2] to the 4.3-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is:

Re: [PATCH 4.3 0/2] 4.3.2-stable review

Am 10.12.2015 um 19:03 schrieb Greg Kroah-Hartman: This is the start of the stable review cycle for the 4.3.2 release. There are 2 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

[PATCH v9 16/60] PCI: Don't release fixed resource for realloc

We should not release bridge resource if there is fixed resources under it, otherwise the children firmware would stop working. Reported-by: Paul Johnson Suggested-by: Bjorn Helgaas Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=92351 Signed-off-by:

[PATCH v9 18/60] PCI: Set resource to FIXED for LSI devices

LSI HBA firmware stop responding pci read from host if pci core ever change pci device BAR values. Set their resources to FIXED, so will allow realloc to skip them. Reported-by: Paul Johnson Suggested-by: Bjorn Helgaas Bugzilla:

Re: usb: gadget: composite: enable BESL support

Hi, John Youn writes: > Hi, > > I would like to request the following commit be applied for kernel > 3.12 and 3.14. > > It could also be applied to any version from 3.1-3.17. > > > commit a6615937bcd9234e6d6bb817c3701fce44d0a84d > Author: Felipe Balbi >

Re: [PATCH] X.509: Fix the time validation [ver #3]

On Thu, Dec 10, 2015 at 04:15:22PM +0100, Alexander Holler wrote: > Am 10.12.2015 um 10:23 schrieb Alexander Holler: > >Am 12.11.2015 um 12:38 schrieb David Howells: > >>This fixes CVE-2015-5327. It affects kernels from 4.3-rc1 onwards. > >> > >>Fix the X.509 time validation to use month number-1

Re: [PATCH] X.509: Fix the time validation [ver #3]

Am 10.12.2015 um 10:23 schrieb Alexander Holler: Am 12.11.2015 um 12:38 schrieb David Howells: This fixes CVE-2015-5327. It affects kernels from 4.3-rc1 onwards. Fix the X.509 time validation to use month number-1 when looking up the number of days in that month. Also put the month number

Re: [PATCH] X.509: Fix the time validation [ver #3]

Am 10.12.2015 um 16:26 schrieb Greg Kroah-Hartman: On Thu, Dec 10, 2015 at 04:15:22PM +0100, Alexander Holler wrote: Just in case of, I would suggest to quickly push out 4.3.2 (only 4.3 seems to be affected) which contains at least the patch mentioned in the subject

[PATCH v2] drm/i915: Unbreak check_digital_port_conflicts()

From: Ville Syrjälä Atomic changes broke check_digital_port_conflicts(). It needs to look at the global situation instead of just trying to find a conflict within the current atomic state. This bug made my HSW explode spectacularly after I had split the DDI

Re: [PATCH 3.19.y-ckt 084/164] thermal: exynos: Fix unbalanced regulator disable on probe failure

On Thu, 2015-12-10 at 09:49 +0900, Krzysztof Kozlowski wrote: > On 09.12.2015 22:24, Krzysztof Kozlowski wrote: > > W dniu 03.12.2015 o 01:58, Kamal Mostafa pisze: > >> 3.19.8-ckt11 -stable review patch. If anyone has any objections, please > >> let me know. > >> > >> -- > >> >

Re: [Intel-gfx] [PATCH v5] drm/i915: Pin the ifbdev for the info->system_base GGTT mmapping

On Thu, 10 Dec 2015 17:36:04 +0100, Ville Syrjälä wrote: > > On Fri, Dec 04, 2015 at 04:05:26PM +, Chris Wilson wrote: > > A long time ago (before 3.14) we relied on a permanent pinning of the > > ifbdev to lock the fb in place inside the GGTT. However, the > > introduction of stealing the

Re: [Intel-gfx] [PATCH v5] drm/i915: Pin the ifbdev for the info->system_base GGTT mmapping

On Fri, Dec 04, 2015 at 04:05:26PM +, Chris Wilson wrote: > A long time ago (before 3.14) we relied on a permanent pinning of the > ifbdev to lock the fb in place inside the GGTT. However, the > introduction of stealing the BIOS framebuffer and reusing its address in > the GGTT for the fbdev