Re: Linux 4.12.12

diff --git a/Makefile b/Makefile index e7b2b54b032c..e96306381ee8 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 12 -SUBLEVEL = 11 +SUBLEVEL = 12 EXTRAVERSION = NAME = Fearless Coyote diff --git a/arch/s390/include/asm/pgtable.h

Re: Linux 4.12.12

diff --git a/Makefile b/Makefile index e7b2b54b032c..e96306381ee8 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 12 -SUBLEVEL = 11 +SUBLEVEL = 12 EXTRAVERSION = NAME = Fearless Coyote diff --git a/arch/s390/include/asm/pgtable.h

Linux 4.9.49

I'm announcing the release of the 4.9.49 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.9.49

diff --git a/Makefile b/Makefile index cfa188b427b1..1ebc553f5464 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 48 +SUBLEVEL = 49 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/s390/include/asm/pgtable.h b/arch/s390/include/asm/pgtable.h

Linux 4.9.49

I'm announcing the release of the 4.9.49 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.9.49

diff --git a/Makefile b/Makefile index cfa188b427b1..1ebc553f5464 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 48 +SUBLEVEL = 49 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/s390/include/asm/pgtable.h b/arch/s390/include/asm/pgtable.h

Linux 4.12.12

I'm announcing the release of the 4.12.12 kernel. All users of the 4.12 kernel series must upgrade. The updated 4.12.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.12.y and can be browsed at the normal kernel.org git web

Linux 4.12.12

I'm announcing the release of the 4.12.12 kernel. All users of the 4.12 kernel series must upgrade. The updated 4.12.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.12.y and can be browsed at the normal kernel.org git web

Linux 4.13.1

I'm announcing the release of the 4.13.1 kernel. All users of the 4.13 kernel series must upgrade. The updated 4.13.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.13.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.13.1

diff --git a/Makefile b/Makefile index ed65d7278bb3..41a976854cad 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 13 -SUBLEVEL = 0 +SUBLEVEL = 1 EXTRAVERSION = NAME = Fearless Coyote diff --git a/arch/s390/include/asm/pgtable.h b/arch/s390/include/asm/pgtable.h

Linux 4.13.1

I'm announcing the release of the 4.13.1 kernel. All users of the 4.13 kernel series must upgrade. The updated 4.13.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.13.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.13.1

diff --git a/Makefile b/Makefile index ed65d7278bb3..41a976854cad 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 13 -SUBLEVEL = 0 +SUBLEVEL = 1 EXTRAVERSION = NAME = Fearless Coyote diff --git a/arch/s390/include/asm/pgtable.h b/arch/s390/include/asm/pgtable.h

[PATCH 0/5] Drivers: hv: Miscellaneous fixes

From: "K. Y. Srinivasan" Miscellaneous fixes. Dexuan Cui (2): vmbus: don't acquire the mutex in vmbus_hvsock_device_unregister() vmbus: suppress uevents for hv_sock devices Olaf Hering (1): Drivers: hv: fcopy: restore correct transfer length Stephen Hemminger (2):

[PATCH 0/5] Drivers: hv: Miscellaneous fixes

From: "K. Y. Srinivasan" Miscellaneous fixes. Dexuan Cui (2): vmbus: don't acquire the mutex in vmbus_hvsock_device_unregister() vmbus: suppress uevents for hv_sock devices Olaf Hering (1): Drivers: hv: fcopy: restore correct transfer length Stephen Hemminger (2): vmbus: add

Re: [Outreachy kernel] [PATCH] Staging: ccree: Merge assignment with return

On Sat, Sep 9, 2017 at 10:29 PM, Julia Lawall wrote: > > > On Sat, 9 Sep 2017, Srishti Sharma wrote: > >> Merge the assignment and return statements to return the value >> directly. Done using coccinelle. > > Coccinelle is not always perfect about pretty printing, so you

Re: [Outreachy kernel] [PATCH] Staging: ccree: Merge assignment with return

On Sat, Sep 9, 2017 at 10:29 PM, Julia Lawall wrote: > > > On Sat, 9 Sep 2017, Srishti Sharma wrote: > >> Merge the assignment and return statements to return the value >> directly. Done using coccinelle. > > Coccinelle is not always perfect about pretty printing, so you have to > watch out for

Re: [PATCH v8] vfio: platform: reset: Add Broadcom FlexRM reset module

On Fri, Sep 8, 2017 at 9:28 PM, Auger Eric wrote: > Hi Anup, > > On 06/09/2017 13:18, Anup Patel wrote: >> This patch adds Broadcom FlexRM low-level reset for >> VFIO platform. >> >> It will do the following: >> 1. Disable/Deactivate each FlexRM ring >> 2. Flush each FlexRM

Re: [PATCH v8] vfio: platform: reset: Add Broadcom FlexRM reset module

On Fri, Sep 8, 2017 at 9:28 PM, Auger Eric wrote: > Hi Anup, > > On 06/09/2017 13:18, Anup Patel wrote: >> This patch adds Broadcom FlexRM low-level reset for >> VFIO platform. >> >> It will do the following: >> 1. Disable/Deactivate each FlexRM ring >> 2. Flush each FlexRM ring >> >> The cleanup

[PATCH v2] Staging: ccree: Merge assignment with return

Merge the assignment and return statements to return the value directly. Done using the following semantic patch by coccinelle. @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Srishti Sharma --- Changes in v2: -Correct

[PATCH v2] Staging: ccree: Merge assignment with return

Merge the assignment and return statements to return the value directly. Done using the following semantic patch by coccinelle. @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Srishti Sharma --- Changes in v2: -Correct coding style problems

Re: [GIT PULL] Security subsystem updates for 4.14

On Sun, 10 Sep 2017, James Morris wrote: > next-apparmor-next (JJ's next branch) > next-integrity-next (Mimi's) > next-tpm-next(Jarkko's) without '-next' on the end... (editing while jetlagged). -- James Morris

Re: [GIT PULL] Security subsystem updates for 4.14

On Sun, 10 Sep 2017, James Morris wrote: > next-apparmor-next (JJ's next branch) > next-integrity-next (Mimi's) > next-tpm-next(Jarkko's) without '-next' on the end... (editing while jetlagged). -- James Morris

Re: Current mainline git (24e700e291d52bd2) hangs when building e.g. perf

On Sat, Sep 9, 2017 at 12:37 PM, Borislav Petkov wrote: > On Sat, Sep 09, 2017 at 12:28:30PM -0700, Andy Lutomirski wrote: >> I propose the following fix. If PCID is on, then, in >> enter_lazy_tlb(), we switch to init_mm with the no-flush flag set. >> (And we give init_mm its own

Re: Current mainline git (24e700e291d52bd2) hangs when building e.g. perf

On Sat, Sep 9, 2017 at 12:37 PM, Borislav Petkov wrote: > On Sat, Sep 09, 2017 at 12:28:30PM -0700, Andy Lutomirski wrote: >> I propose the following fix. If PCID is on, then, in >> enter_lazy_tlb(), we switch to init_mm with the no-flush flag set. >> (And we give init_mm its own dedicated ASID

Re: [GIT PULL] Security subsystem updates for 4.14

On Fri, 8 Sep 2017, Paul Moore wrote: > > This is also why I tend to prefer getting multiple branches for > > independent things. [...] > > Is it time to start sending pull request for each LSM and thing under > security/ directly? I'm not sure I have a strong preference either > way, I just

Re: [GIT PULL] Security subsystem updates for 4.14

On Fri, 8 Sep 2017, Paul Moore wrote: > > This is also why I tend to prefer getting multiple branches for > > independent things. [...] > > Is it time to start sending pull request for each LSM and thing under > security/ directly? I'm not sure I have a strong preference either > way, I just

[GIT PULL] Security susbsystem updates for v4.14 (v2)

Here's an updated pull request with the IMA integrity_read() patch reverted. Note that this restores the orginal buggy behavior with XFS/IMA deadlock the builtin ima_tcb policy wand XFS rootfs. Everything else is the same as the last pull request. AppArmor: - Add mediation of mountpoints

[GIT PULL] Security susbsystem updates for v4.14 (v2)

Here's an updated pull request with the IMA integrity_read() patch reverted. Note that this restores the orginal buggy behavior with XFS/IMA deadlock the builtin ima_tcb policy wand XFS rootfs. Everything else is the same as the last pull request. AppArmor: - Add mediation of mountpoints

nios2 crash due to 'init/main.c: extract early boot entropy from the passed cmdline'

Hi, I noticed that nios2 images crash in mainline. Bisect points to commit 33d72f3822d7 ("init/main.c: extract early boot entropy from the passed cmdline"). Bisect log is attached. As far as I can see, the problem is seen because add_device_randomness() calls random_get_entropy(). However, the

nios2 crash due to 'init/main.c: extract early boot entropy from the passed cmdline'

Hi, I noticed that nios2 images crash in mainline. Bisect points to commit 33d72f3822d7 ("init/main.c: extract early boot entropy from the passed cmdline"). Bisect log is attached. As far as I can see, the problem is seen because add_device_randomness() calls random_get_entropy(). However, the

[GIT] Sparc

1) Use register window state adjustment instructions when available, from Anthony Yznaga. 2) Add VCC console concentrator driver, from Jag Raman. 3) Add 16GB hugepage support, from Nitin Gupta. 4) Support cpu 'poke' hypercall, from Vijay Kumar. 5) Add M7/M8 optimized

[GIT] Sparc

1) Use register window state adjustment instructions when available, from Anthony Yznaga. 2) Add VCC console concentrator driver, from Jag Raman. 3) Add 16GB hugepage support, from Nitin Gupta. 4) Support cpu 'poke' hypercall, from Vijay Kumar. 5) Add M7/M8 optimized

Re: iov_iter_pipe warning.

On Sat, Sep 09, 2017 at 09:07:56PM -0400, Dave Jones wrote: > With this in place, I'm still seeing -EBUSY from invalidate_inode_pages2_range > which doesn't end well... Different issue, and I'm not sure why that WARN_ON() is there in the first place. Note that in a similar situation

Re: iov_iter_pipe warning.

On Sat, Sep 09, 2017 at 09:07:56PM -0400, Dave Jones wrote: > With this in place, I'm still seeing -EBUSY from invalidate_inode_pages2_range > which doesn't end well... Different issue, and I'm not sure why that WARN_ON() is there in the first place. Note that in a similar situation

Re: [GIT PULL] Security subsystem updates for 4.14

On Fri, 8 Sep 2017, Theodore Ts'o wrote: > On Fri, Sep 08, 2017 at 02:48:51PM +1000, James Morris wrote: > > > > Mimi and Christoph worked together on this over several iterations -- I'll > > let them respond. > > Mimi --- we should chat next week in LA. I've been working on a > design

Re: [GIT PULL] Security subsystem updates for 4.14

On Fri, 8 Sep 2017, Theodore Ts'o wrote: > On Fri, Sep 08, 2017 at 02:48:51PM +1000, James Morris wrote: > > > > Mimi and Christoph worked together on this over several iterations -- I'll > > let them respond. > > Mimi --- we should chat next week in LA. I've been working on a > design

Re: iov_iter_pipe warning.

On Fri, Sep 08, 2017 at 02:04:41AM +0100, Al Viro wrote: > There's at least one suspicious place in iomap_dio_actor() - > if (!(dio->flags & IOMAP_DIO_WRITE)) { > iov_iter_zero(length, dio->submit.iter); > dio->size += length;

Re: iov_iter_pipe warning.

On Fri, Sep 08, 2017 at 02:04:41AM +0100, Al Viro wrote: > There's at least one suspicious place in iomap_dio_actor() - > if (!(dio->flags & IOMAP_DIO_WRITE)) { > iov_iter_zero(length, dio->submit.iter); > dio->size += length;

Re: [PATCH v6 11/11] lkdtm: Add test for XPFO

Hi Juerg, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.13] [cannot apply to mmotm/master next-20170908] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v6 11/11] lkdtm: Add test for XPFO

Hi Juerg, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.13] [cannot apply to mmotm/master next-20170908] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH 3.2 002/106] af_key: Fix slab-out-of-bounds in pfkey_compile_policy.

3.2.93-rc1 review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert commit d90c902449a7561f1b1d58ba5a0d11728ce8b0b2 upstream. The sadb_x_sec_len is stored in the unit 'byte divided by eight'. So we have to

[PATCH 3.2 001/106] xfrm: fix stack access out of bounds with CONFIG_XFRM_SUB_POLICY

3.2.93-rc1 review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca commit 9b3eb54106cf6acd03f07cf0ab01c13676a226c2 upstream. When CONFIG_XFRM_SUB_POLICY=y, xfrm_dst stores a copy of the flowi for that dst. Unfortunately,

[PATCH 3.2 002/106] af_key: Fix slab-out-of-bounds in pfkey_compile_policy.

3.2.93-rc1 review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert commit d90c902449a7561f1b1d58ba5a0d11728ce8b0b2 upstream. The sadb_x_sec_len is stored in the unit 'byte divided by eight'. So we have to multiply this value by eight before

[PATCH 3.2 001/106] xfrm: fix stack access out of bounds with CONFIG_XFRM_SUB_POLICY

3.2.93-rc1 review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca commit 9b3eb54106cf6acd03f07cf0ab01c13676a226c2 upstream. When CONFIG_XFRM_SUB_POLICY=y, xfrm_dst stores a copy of the flowi for that dst. Unfortunately, the code that

[PATCH 3.2 009/106] ahci: Acer SA5-271 SSD Not Detected Fix

3.2.93-rc1 review patch. If anyone has any objections, please let me know. -- From: Sui Chen commit 8bfd174312629866efa535193d9e563768ff4307 upstream. (Correction in this resend: fixed function name acer_sa5_271_workaround; fixed the always-true condition

[PATCH 3.2 014/106] USB: iowarrior: fix info ioctl on big-endian hosts

3.2.93-rc1 review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit dd5ca753fa92fb736b1395db892bd29f78e6d408 upstream. Drop erroneous le16_to_cpu when returning the USB device speed which is already in host byte order.

[PATCH 3.2 009/106] ahci: Acer SA5-271 SSD Not Detected Fix

3.2.93-rc1 review patch. If anyone has any objections, please let me know. -- From: Sui Chen commit 8bfd174312629866efa535193d9e563768ff4307 upstream. (Correction in this resend: fixed function name acer_sa5_271_workaround; fixed the always-true condition in the function;

[PATCH 3.2 014/106] USB: iowarrior: fix info ioctl on big-endian hosts

3.2.93-rc1 review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit dd5ca753fa92fb736b1395db892bd29f78e6d408 upstream. Drop erroneous le16_to_cpu when returning the USB device speed which is already in host byte order. Found using sparse:

[PATCH 3.16 116/233] alarmtimer: Rate limit periodic intervals

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit ff86bf0c65f14346bf2440534f9ba5ac232c39a0 upstream. The alarmtimer code has another source of potentially rearming itself too fast. Interval timers

[PATCH 3.16 095/233] tcp: avoid fastopen API to be used on AF_UNSPEC

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Wei Wang commit ba615f675281d76fd19aa03558777f81fb6b6084 upstream. Fastopen API should be used to perform fastopen operations on the TCP socket. It does not make sense to

[PATCH 3.16 116/233] alarmtimer: Rate limit periodic intervals

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit ff86bf0c65f14346bf2440534f9ba5ac232c39a0 upstream. The alarmtimer code has another source of potentially rearming itself too fast. Interval timers with a very samll

[PATCH 3.16 095/233] tcp: avoid fastopen API to be used on AF_UNSPEC

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Wei Wang commit ba615f675281d76fd19aa03558777f81fb6b6084 upstream. Fastopen API should be used to perform fastopen operations on the TCP socket. It does not make sense to use fastopen API to

[PATCH 3.16 062/233] serial: ifx6x60: fix use-after-free on module unload

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 1e948479b3d63e3ac0ecca13cbf4921c7d17c168 upstream. Make sure to deregister the SPI driver before releasing the tty driver to avoid use-after-free in the

[PATCH 3.16 092/233] drm/radeon: Unbreak HPD handling for r600+

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Lyude commit 3d18e33735a02b1a90aecf14410bf3edbfd4d3dc upstream. We end up reading the interrupt register for HPD5, and then writing it to HPD6 which on systems without

[PATCH 3.16 062/233] serial: ifx6x60: fix use-after-free on module unload

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 1e948479b3d63e3ac0ecca13cbf4921c7d17c168 upstream. Make sure to deregister the SPI driver before releasing the tty driver to avoid use-after-free in the SPI remove

[PATCH 3.16 092/233] drm/radeon: Unbreak HPD handling for r600+

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Lyude commit 3d18e33735a02b1a90aecf14410bf3edbfd4d3dc upstream. We end up reading the interrupt register for HPD5, and then writing it to HPD6 which on systems without anything using HPD5

[PATCH 3.16 161/233] net: ethoc: enable NAPI before poll may be scheduled

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit d220b942a4b6a0640aee78841608f4aa5e8e185e upstream. ethoc_reset enables device interrupts, ethoc_interrupt may schedule a NAPI poll before NAPI is

[PATCH 3.16 161/233] net: ethoc: enable NAPI before poll may be scheduled

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit d220b942a4b6a0640aee78841608f4aa5e8e185e upstream. ethoc_reset enables device interrupts, ethoc_interrupt may schedule a NAPI poll before NAPI is enabled in the

[PATCH 3.16 026/233] dm space map disk: fix some book keeping in the disk space map

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Joe Thornber commit 0377a07c7a035e0d033cd8b29f0cb15244c0916a upstream. When decrementing the reference count for a block, the free count wasn't being updated if the reference

[PATCH 3.16 096/233] net: ethernet: ax88796: don't call free_irq without request_irq first

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Uwe Kleine-König commit 82533ad9a1ce3a7a6863849a552c2cc041b55e0d upstream. The function ax_init_dev (which is called only from the driver's .probe function)

[PATCH 3.16 026/233] dm space map disk: fix some book keeping in the disk space map

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Joe Thornber commit 0377a07c7a035e0d033cd8b29f0cb15244c0916a upstream. When decrementing the reference count for a block, the free count wasn't being updated if the reference count went to

[PATCH 3.16 096/233] net: ethernet: ax88796: don't call free_irq without request_irq first

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Uwe Kleine-König commit 82533ad9a1ce3a7a6863849a552c2cc041b55e0d upstream. The function ax_init_dev (which is called only from the driver's .probe function) calls free_irq in the error path

[PATCH 3.16 051/233] net: fix compile error in skb_orphan_partial()

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 9142e9007f2d7ab58a587a1e1d921b0064a339aa upstream. If CONFIG_INET is not set, net/core/sock.c can not compile : net/core/sock.c: In function

[PATCH 3.16 051/233] net: fix compile error in skb_orphan_partial()

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 9142e9007f2d7ab58a587a1e1d921b0064a339aa upstream. If CONFIG_INET is not set, net/core/sock.c can not compile : net/core/sock.c: In function ‘skb_orphan_partial’:

[PATCH 3.16 143/233] HID: Fix boot delay for Creative SB Omni Surround 5.1 with quirk

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Nazar Mokrynskyi commit 567a44ecb44eb2584ddb93e962cfb133ce77e0bb upstream. Needed for v2 of the device firmware, otherwise kernel will stuck for few seconds and throw

[PATCH 3.16 143/233] HID: Fix boot delay for Creative SB Omni Surround 5.1 with quirk

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Nazar Mokrynskyi commit 567a44ecb44eb2584ddb93e962cfb133ce77e0bb upstream. Needed for v2 of the device firmware, otherwise kernel will stuck for few seconds and throw "usb_submit_urb(ctrl)

[PATCH 3.16 028/233] kvm: arm/arm64: Force reading uncached stage2 PGD

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Suzuki K Poulose commit 2952a6070e07ebdd5896f1f5b861acad677caded upstream. Make sure we don't use a cached value of the KVM stage2 PGD while resetting the PGD. Cc:

[PATCH 3.16 094/233] xfs: Fix missed holes in SEEK_HOLE implementation

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 5375023ae1266553a7baa0845e82917d8803f48c upstream. XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as can be seen by the following command:

[PATCH 3.16 028/233] kvm: arm/arm64: Force reading uncached stage2 PGD

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Suzuki K Poulose commit 2952a6070e07ebdd5896f1f5b861acad677caded upstream. Make sure we don't use a cached value of the KVM stage2 PGD while resetting the PGD. Cc: Marc Zyngier

[PATCH 3.16 094/233] xfs: Fix missed holes in SEEK_HOLE implementation

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 5375023ae1266553a7baa0845e82917d8803f48c upstream. XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as can be seen by the following command: xfs_io -c

[PATCH 3.16 105/233] btrfs: use correct types for page indices in btrfs_page_exists_in_range

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: David Sterba commit cc2b702c52094b637a351d7491ac5200331d0445 upstream. Variables start_idx and end_idx are supposed to hold a page index derived from the file offsets. The

[PATCH 3.16 077/233] i2c: i2c-tiny-usb: fix buffer not being DMA capable

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Sebastian Reichel commit 5165da5923d6c7df6f2927b0113b2e4d9288661e upstream. Since v4.9 i2c-tiny-usb generates the below call trace and longer works, since

[PATCH 3.16 181/233] excessive checks in ufs_write_failed() and ufs_evict_inode()

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Al Viro commit babef37dccbaa49249a22bae9150686815d7be71 upstream. As it is, short copy in write() to append-only file will fail to truncate the excessive allocated

[PATCH 3.16 105/233] btrfs: use correct types for page indices in btrfs_page_exists_in_range

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: David Sterba commit cc2b702c52094b637a351d7491ac5200331d0445 upstream. Variables start_idx and end_idx are supposed to hold a page index derived from the file offsets. The int type is not the

[PATCH 3.16 077/233] i2c: i2c-tiny-usb: fix buffer not being DMA capable

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Sebastian Reichel commit 5165da5923d6c7df6f2927b0113b2e4d9288661e upstream. Since v4.9 i2c-tiny-usb generates the below call trace and longer works, since it can't communicate with the USB

[PATCH 3.16 181/233] excessive checks in ufs_write_failed() and ufs_evict_inode()

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Al Viro commit babef37dccbaa49249a22bae9150686815d7be71 upstream. As it is, short copy in write() to append-only file will fail to truncate the excessive allocated blocks. As the matter of

[PATCH 3.16 080/233] ALSA: hda - apply STAC_9200_DELL_M22 quirk for Dell Latitude D430

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Alexander Tsoy commit 1fc2e41f7af4572b07190f9dec28396b418e9a36 upstream. This model is actually called 92XXM2-8 in Windows driver. But since pin configs for M22 and M28 are

[PATCH 3.16 080/233] ALSA: hda - apply STAC_9200_DELL_M22 quirk for Dell Latitude D430

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Alexander Tsoy commit 1fc2e41f7af4572b07190f9dec28396b418e9a36 upstream. This model is actually called 92XXM2-8 in Windows driver. But since pin configs for M22 and M28 are identical, just

[PATCH 3.16 089/233] scsi: qla2xxx: don't disable a not previously enabled PCI device

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Johannes Thumshirn commit ddff7ed45edce4a4c92949d3c61cd25d229c4a14 upstream. When pci_enable_device() or pci_enable_device_mem() fail in qla2x00_probe_one() we bail out

[PATCH 3.16 089/233] scsi: qla2xxx: don't disable a not previously enabled PCI device

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Johannes Thumshirn commit ddff7ed45edce4a4c92949d3c61cd25d229c4a14 upstream. When pci_enable_device() or pci_enable_device_mem() fail in qla2x00_probe_one() we bail out but do a call to

[PATCH 3.16 166/233] perf script: Fix documentation errors

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: SeongJae Park commit 34d4453dac257be53c21abf2f713c992fb692b5c upstream. This commit fixes two errors in documents for perf-script-python and perf-script-perl as below: -

[PATCH 3.16 166/233] perf script: Fix documentation errors

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: SeongJae Park commit 34d4453dac257be53c21abf2f713c992fb692b5c upstream. This commit fixes two errors in documents for perf-script-python and perf-script-perl as below: -

[PATCH 3.16 167/233] perf script python: Fix wrong code snippets in documentation

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: SeongJae Park commit 26ddb8722df865aa67fbe459107d2f3f8e5c6829 upstream. This commit fixes wrong code snippets for trace_begin() and trace_end() function example

[PATCH 3.16 167/233] perf script python: Fix wrong code snippets in documentation

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: SeongJae Park commit 26ddb8722df865aa67fbe459107d2f3f8e5c6829 upstream. This commit fixes wrong code snippets for trace_begin() and trace_end() function example definition. Signed-off-by:

[PATCH 3.16 144/233] HID: usbhid: quirks for Corsair RGB keyboard & mice (K70R, K95RGB, M65RGB, K70RGB, K65RGB)

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Trent Lloyd commit 282bf1fe6dca4b768d6bedc14aea1b82c36241c1 upstream. These devices feature multiple interfaces/endpoints: a legacy BIOS/boot interface (endpoint 0x81), as

[PATCH 3.16 144/233] HID: usbhid: quirks for Corsair RGB keyboard & mice (K70R, K95RGB, M65RGB, K70RGB, K65RGB)

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Trent Lloyd commit 282bf1fe6dca4b768d6bedc14aea1b82c36241c1 upstream. These devices feature multiple interfaces/endpoints: a legacy BIOS/boot interface (endpoint 0x81), as well as 2

[PATCH 3.16 070/233] KVM: X86: Fix read out-of-bounds vulnerability in kvm pio emulation

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Wanpeng Li commit cbfc6c9184ce71b52df4b1d82af5afc81a709178 upstream. Huawei folks reported a read out-of-bounds vulnerability in kvm pio emulation. - "inb"

[PATCH 3.16 035/233] uio: fix incorrect memory leak cleanup

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Suman Anna commit 0d83539092ddb1ab79b4d65bccb866bf07ea2ccd upstream. Commit 75f0aef6220d ("uio: fix memory leak") has fixed up some memory leaks during the failure paths of the

[PATCH 3.16 070/233] KVM: X86: Fix read out-of-bounds vulnerability in kvm pio emulation

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Wanpeng Li commit cbfc6c9184ce71b52df4b1d82af5afc81a709178 upstream. Huawei folks reported a read out-of-bounds vulnerability in kvm pio emulation. - "inb" instruction to access PIT

[PATCH 3.16 035/233] uio: fix incorrect memory leak cleanup

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Suman Anna commit 0d83539092ddb1ab79b4d65bccb866bf07ea2ccd upstream. Commit 75f0aef6220d ("uio: fix memory leak") has fixed up some memory leaks during the failure paths of the addition of

[PATCH 3.16 113/233] staging/lustre/lov: remove set_fs() call from lov_getstripe()

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Oleg Drokin commit 0a33252e060e97ed3fbdcec9517672f1e91aaef3 upstream. lov_getstripe() calls set_fs(KERNEL_DS) so that it can handle a struct lov_user_md pointer from

[PATCH 3.16 113/233] staging/lustre/lov: remove set_fs() call from lov_getstripe()

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Oleg Drokin commit 0a33252e060e97ed3fbdcec9517672f1e91aaef3 upstream. lov_getstripe() calls set_fs(KERNEL_DS) so that it can handle a struct lov_user_md pointer from user- or kernel-space.

[PATCH 3.16 091/233] drm/radeon/ci: disable mclk switching for high refresh rates (v2)

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 58d7e3e427db1bd68f33025519a9468140280a75 upstream. Even if the vblank period would allow it, it still seems to be problematic on some cards.

[PATCH 3.16 091/233] drm/radeon/ci: disable mclk switching for high refresh rates (v2)

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 58d7e3e427db1bd68f33025519a9468140280a75 upstream. Even if the vblank period would allow it, it still seems to be problematic on some cards. v2: fix logic inversion

[PATCH 3.16 106/233] btrfs: fix memory leak in update_space_info failure path

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Jeff Mahoney commit 896533a7da929136d0432713f02a3edffece2826 upstream. If we fail to add the space_info kobject, we'll leak the memory for the percpu counter. Fixes:

[PATCH 3.16 106/233] btrfs: fix memory leak in update_space_info failure path

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Jeff Mahoney commit 896533a7da929136d0432713f02a3edffece2826 upstream. If we fail to add the space_info kobject, we'll leak the memory for the percpu counter. Fixes: 6ab0a2029c (btrfs:

[PATCH 3.16 064/233] sh_eth: Use platform device for printing before register_netdev()

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit 5f5c5449acad0cd3322e53e1ac68c044483b0aa5 upstream. The MDIO initialization failure message is printed using the network device, before it

[PATCH 3.16 204/233] drm/radeon: add a quirk for Toshiba Satellite L20-183

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit acfd6ee4fa7ebeee75511825fe02be3f7ac1d668 upstream. Fixes resume from suspend. bug: https://bugzilla.kernel.org/show_bug.cgi?id=196121

[PATCH 3.16 073/233] ext4: fix SEEK_HOLE

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 7d95eddf313c88b24f99d4ca9c2411a4b82fef33 upstream. Currently, SEEK_HOLE implementation in ext4 may both return that there's a hole at some offset although that

[PATCH 3.16 046/233] USB: hub: fix non-SS hub-descriptor handling

3.16.48-rc1 review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit bec444cd1c94c48df409a35ad4e5b143c245c3f7 upstream. Add missing sanity check on the non-SuperSpeed hub-descriptor length in order to avoid parsing and

  1   2   3   4   5   6   7   8   9   10   >