[PATCH 4.4 46/69] scsi: scsi_debug: Fix memory leak if LBP enabled and module is unloaded

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ewan D. Milne commit 4d2b496f19f3c2cfaca1e8fa0710688b5ff3811d upstream. map_storep was not being vfree()'d in the module_exit call. Signed-off-by: Ewan D. Milne Reviewed-by: Laurence Oberman

[PATCH 4.4 51/69] drm/radeon/si_dpm: workaround for SI kickers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 7dc86ef5ac91642dfc3eb93ee0f0458e702a343e upstream. Consolidate existing quirks. Fixes stability issues on some kickers. Signed-off-by: Alex Deucher Signed-off-by: Alex

[PATCH 4.4 47/69] scsi: arcmsr: Send SYNCHRONIZE_CACHE command to firmware

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ching Huang commit 2bf7dc8443e113844d078fd6541b7f4aa544f92f upstream. The arcmsr driver failed to pass SYNCHRONIZE CACHE to controller firmware. Depending on how drive

[PATCH 4.4 37/69] parisc: Ensure consistent state when switching to kernel stack at syscall entry

4.4-stable review patch. If anyone has any objections, please let me know. -- From: John David Anglin commit 6ed518328d0189e0fdf1bb7c73290d546143ea66 upstream. We have one critical section in the syscall entry path in which we switch from the userspace

[PATCH 4.4 47/69] scsi: arcmsr: Send SYNCHRONIZE_CACHE command to firmware

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ching Huang commit 2bf7dc8443e113844d078fd6541b7f4aa544f92f upstream. The arcmsr driver failed to pass SYNCHRONIZE CACHE to controller firmware. Depending on how drive caches are handled

[PATCH 4.4 37/69] parisc: Ensure consistent state when switching to kernel stack at syscall entry

4.4-stable review patch. If anyone has any objections, please let me know. -- From: John David Anglin commit 6ed518328d0189e0fdf1bb7c73290d546143ea66 upstream. We have one critical section in the syscall entry path in which we switch from the userspace stack to kernel stack.

Re: [PATCH v4 0/3] spi-nor: Add support for Intel SPI serial flash controller

On Mon, Oct 17, 2016 at 05:58:55PM +0300, Mika Westerberg wrote: > This is fourth version of the series. Previous versions can be found: > > v3: https://lwn.net/Articles/697231/ > v2: http://lists.infradead.org/pipermail/linux-mtd/2016-June/068277.html > v1:

Re: [PATCH v4 0/3] spi-nor: Add support for Intel SPI serial flash controller

On Mon, Oct 17, 2016 at 05:58:55PM +0300, Mika Westerberg wrote: > This is fourth version of the series. Previous versions can be found: > > v3: https://lwn.net/Articles/697231/ > v2: http://lists.infradead.org/pipermail/linux-mtd/2016-June/068277.html > v1:

Re: [PATCH net-next 1/2] bpf, mlx4: fix prog refcount in mlx4_en_try_alloc_resources error path

Hi Daniel, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Daniel-Borkmann/bpf-mlx4-fix-prog-refcount-in-mlx4_en_try_alloc_resources-error-path/20161109-182712 config: x86_64-acpi-redef (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0

Re: [PATCH net-next 1/2] bpf, mlx4: fix prog refcount in mlx4_en_try_alloc_resources error path

Hi Daniel, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Daniel-Borkmann/bpf-mlx4-fix-prog-refcount-in-mlx4_en_try_alloc_resources-error-path/20161109-182712 config: x86_64-acpi-redef (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0

Re: KASAN & the vmalloc area

On Tue, Nov 08, 2016 at 02:09:27PM -0800, Dmitry Vyukov wrote: > On Tue, Nov 8, 2016 at 11:03 AM, Mark Rutland wrote: > > When KASAN is selected, we allocate shadow for the whole vmalloc area, > > using common zero pte, pmd, pud tables. Walking over these in the ptdump > >

Re: KASAN & the vmalloc area

On Tue, Nov 08, 2016 at 02:09:27PM -0800, Dmitry Vyukov wrote: > On Tue, Nov 8, 2016 at 11:03 AM, Mark Rutland wrote: > > When KASAN is selected, we allocate shadow for the whole vmalloc area, > > using common zero pte, pmd, pud tables. Walking over these in the ptdump > > code takes a *very*

[PATCH v3] z3fold: use per-page read/write lock

Most of z3fold operations are in-page, such as modifying z3fold page header or moving z3fold objects within a page. Taking per-pool spinlock to protect per-page objects is therefore suboptimal, and the idea of having a per-page spinlock (or rwlock) has been around for some time. However, adding

[PATCH v3] z3fold: use per-page read/write lock

Most of z3fold operations are in-page, such as modifying z3fold page header or moving z3fold objects within a page. Taking per-pool spinlock to protect per-page objects is therefore suboptimal, and the idea of having a per-page spinlock (or rwlock) has been around for some time. However, adding

Re: linux-next: build warning after merge of the akpm-current tree

On Wed, Nov 09, 2016 at 03:10:06PM +1100, Stephen Rothwell wrote: Hi Stephen, > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > mm/hugetlb.c:1166:21: warning: 'alloc_gigantic_page' defined but not used >

Re: linux-next: build warning after merge of the akpm-current tree

On Wed, Nov 09, 2016 at 03:10:06PM +1100, Stephen Rothwell wrote: Hi Stephen, > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > mm/hugetlb.c:1166:21: warning: 'alloc_gigantic_page' defined but not used >

[PATCH 4.4 10/69] ALSA: hda - Merge RIRB_PRE_DELAY into CTX_WORKAROUND caps

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit ef85f299c74e6c5dd98ec0230183be33f4c2813d upstream. AZX_DCAPS_RIRB_PRE_DELAY is always tied with AZX_DCAPS_CTX_WORKAROUND, which is Creative's XFi specific.

[PATCH 4.4 20/69] mei: txe: dont clean an unprocessed interrupt cause.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Usyskin commit 43605e293eb13c07acb546c14f407a271837af17 upstream. SEC registers are not accessible when the TXE device is in low power state, hence the

[PATCH 4.4 20/69] mei: txe: dont clean an unprocessed interrupt cause.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Usyskin commit 43605e293eb13c07acb546c14f407a271837af17 upstream. SEC registers are not accessible when the TXE device is in low power state, hence the SEC interrupt cannot be

[PATCH 4.4 10/69] ALSA: hda - Merge RIRB_PRE_DELAY into CTX_WORKAROUND caps

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit ef85f299c74e6c5dd98ec0230183be33f4c2813d upstream. AZX_DCAPS_RIRB_PRE_DELAY is always tied with AZX_DCAPS_CTX_WORKAROUND, which is Creative's XFi specific. So, we can

[PATCH 4.4 07/69] mm: memcontrol: do not recurse in direct reclaim

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Weiner commit 89a2848381b5fcd9c4d9c0cd97680e3b28730e31 upstream. On 4.0, we saw a stack corruption from a page fault entering direct memory cgroup reclaim, calling

[PATCH 4.4 08/69] KEYS: Fix short sprintf buffer in /proc/keys show function

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Howells commit 03dab869b7b239c4e013ec82aea22e181e441cfc upstream. This fixes CVE-2016-7042. Fix a short sprintf buffer in proc_keys_show(). If the gcc stack

Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver

On Tuesday 08 November 2016 08:40 PM, Arnd Bergmann wrote: On Tuesday, November 8, 2016 1:49:43 PM CET John Garry wrote: Hi Arnd, Thanks for the reference. I think the i2c interface doesn't fully satisfy our requirements as we need more than just a slave bus address when accessing the slave

[PATCH 4.4 07/69] mm: memcontrol: do not recurse in direct reclaim

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Weiner commit 89a2848381b5fcd9c4d9c0cd97680e3b28730e31 upstream. On 4.0, we saw a stack corruption from a page fault entering direct memory cgroup reclaim, calling into

[PATCH 4.4 08/69] KEYS: Fix short sprintf buffer in /proc/keys show function

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Howells commit 03dab869b7b239c4e013ec82aea22e181e441cfc upstream. This fixes CVE-2016-7042. Fix a short sprintf buffer in proc_keys_show(). If the gcc stack protector is turned on,

Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver

On Tuesday 08 November 2016 08:40 PM, Arnd Bergmann wrote: On Tuesday, November 8, 2016 1:49:43 PM CET John Garry wrote: Hi Arnd, Thanks for the reference. I think the i2c interface doesn't fully satisfy our requirements as we need more than just a slave bus address when accessing the slave

[PATCH 4.4 02/69] i2c: core: fix NULL pointer dereference under race condition

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vladimir Zapolskiy commit 147b36d5b70c083cc76770c47d60b347e8eaf231 upstream. Race condition between registering an I2C device driver and deregistering an I2C

[PATCH 4.4 02/69] i2c: core: fix NULL pointer dereference under race condition

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vladimir Zapolskiy commit 147b36d5b70c083cc76770c47d60b347e8eaf231 upstream. Race condition between registering an I2C device driver and deregistering an I2C adapter device which is assumed to

[PATCH 4.4 13/69] ALSA: hda - Adding a new group of pin cfg into ALC295 pin quirk table

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hui Wang commit f771d5bb71d4df9573d12386400540516672208b upstream. We have a new Dell laptop model which uses ALC295, the pin definition is different from the existing

[PATCH 4.4 13/69] ALSA: hda - Adding a new group of pin cfg into ALC295 pin quirk table

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hui Wang commit f771d5bb71d4df9573d12386400540516672208b upstream. We have a new Dell laptop model which uses ALC295, the pin definition is different from the existing ones in the pin quirk

[PATCH 4.4 18/69] ubifs: Abort readdir upon error

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Richard Weinberger commit c83ed4c9dbb358b9e7707486e167e940d48bfeed upstream. If UBIFS is facing an error while walking a directory, it reports this error and ubifs_readdir()

[PATCH 4.4 29/69] hv: do not lose pending heartbeat vmbus packets

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Long Li commit 407a3aee6ee2d2cb46d9ba3fc380bc29f35d020c upstream. The host keeps sending heartbeat packets independent of the guest responding to them. Even though we

[PATCH 4.4 17/69] btrfs: fix races on root_log_ctx lists

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chris Mason commit 570dd45042a7c8a7aba1ee029c5dd0f5ccf41b9b upstream. btrfs_remove_all_log_ctxs takes a shortcut where it avoids walking the list because it knows all of the

[PATCH 4.4 23/69] USB: serial: ftdi_sio: add support for Infineon TriBoard TC2X7

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Tauner commit ca006f785fbfd7a5c901900bd3fe2b26e946a1ee upstream. This adds support to ftdi_sio for the Infineon TriBoard TC2X7 engineering board for

[PATCH 4.4 25/69] usb: increase ohci watchdog delay to 275 msec

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Bryan Paluch commit ed6d6f8f42d7302f6f9b6245f34927ec20d26c12 upstream. Increase ohci watchout delay to 275 ms. Previous delay was 250 ms with 20 ms of slack, after

[PATCH 4.4 31/69] tty: limit terminal size to 4M chars

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Vyukov commit 32b2921e6a7461fe63b71217067a6cf4bddb132f upstream. Size of kmalloc() in vc_do_resize() is controlled by user. Too large kmalloc() size triggers WARNING

[PATCH 4.4 18/69] ubifs: Abort readdir upon error

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Richard Weinberger commit c83ed4c9dbb358b9e7707486e167e940d48bfeed upstream. If UBIFS is facing an error while walking a directory, it reports this error and ubifs_readdir() returns the error

[PATCH 4.4 29/69] hv: do not lose pending heartbeat vmbus packets

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Long Li commit 407a3aee6ee2d2cb46d9ba3fc380bc29f35d020c upstream. The host keeps sending heartbeat packets independent of the guest responding to them. Even though we respond to the heartbeat

[PATCH 4.4 17/69] btrfs: fix races on root_log_ctx lists

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chris Mason commit 570dd45042a7c8a7aba1ee029c5dd0f5ccf41b9b upstream. btrfs_remove_all_log_ctxs takes a shortcut where it avoids walking the list because it knows all of the waiters are

[PATCH 4.4 23/69] USB: serial: ftdi_sio: add support for Infineon TriBoard TC2X7

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Tauner commit ca006f785fbfd7a5c901900bd3fe2b26e946a1ee upstream. This adds support to ftdi_sio for the Infineon TriBoard TC2X7 engineering board for first-generation Aurix SoCs with

[PATCH 4.4 25/69] usb: increase ohci watchdog delay to 275 msec

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Bryan Paluch commit ed6d6f8f42d7302f6f9b6245f34927ec20d26c12 upstream. Increase ohci watchout delay to 275 ms. Previous delay was 250 ms with 20 ms of slack, after removing slack time some

[PATCH 4.4 31/69] tty: limit terminal size to 4M chars

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Vyukov commit 32b2921e6a7461fe63b71217067a6cf4bddb132f upstream. Size of kmalloc() in vc_do_resize() is controlled by user. Too large kmalloc() size triggers WARNING message on console.

[PATCH 4.4 27/69] Fix potential infoleak in older kernels

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds Not upstream as it is not needed there. So a patch something like this might be a safe way to fix the potential infoleak in older kernels. THIS

[PATCH 4.4 09/69] ALSA: usb-audio: Add quirk for Syntek STK1160

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Marcel Hasler commit bdc3478f90cd4d2928197f36629d5cf93b64dbe9 upstream. The stk1160 chip needs QUIRK_AUDIO_ALIGN_TRANSFER. This patch resolves the issue reported on the

[PATCH 4.4 28/69] vt: clear selection before resizing

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Scot Doyle commit 009e39ae44f4191188aeb6dfbf661b771dbbe515 upstream. When resizing a vt its selection may exceed the new size, resulting in an invalid memory access [1].

[PATCH 4.4 09/69] ALSA: usb-audio: Add quirk for Syntek STK1160

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Marcel Hasler commit bdc3478f90cd4d2928197f36629d5cf93b64dbe9 upstream. The stk1160 chip needs QUIRK_AUDIO_ALIGN_TRANSFER. This patch resolves the issue reported on the mailing list

[PATCH 4.4 28/69] vt: clear selection before resizing

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Scot Doyle commit 009e39ae44f4191188aeb6dfbf661b771dbbe515 upstream. When resizing a vt its selection may exceed the new size, resulting in an invalid memory access [1]. Clear the selection

[PATCH 4.4 27/69] Fix potential infoleak in older kernels

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds Not upstream as it is not needed there. So a patch something like this might be a safe way to fix the potential infoleak in older kernels. THIS IS UNTESTED. It's a very obvious

[PATCH 4.4 30/69] xhci: add restart quirk for Intel Wildcatpoint PCH

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Nyman commit 4c39135aa412d2f1381e43802523da110ca7855c upstream. xHC in Wildcatpoint-LP PCH is similar to LynxPoint-LP and need the same quirks to prevent

[PATCH 4.4 12/69] ALSA: hda - allow 40 bit DMA mask for NVidia devices

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 3ab7511eafdd5c4f40d2832f09554478dfbea170 upstream. Commit 49d9e77e72cf ("ALSA: hda - Fix system panic when DMA > 40 bits for Nvidia audio

[PATCH 4.4 33/69] dm: free io_barrier after blk_cleanup_queue call

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tahsin Erdogan commit d09960b0032174eb493c4c13be5b9c9ef36dc9a7 upstream. dm_old_request_fn() has paths that access md->io_barrier. The party destroying io_barrier should

[PATCH 4.4 11/69] ALSA: hda - Raise AZX_DCAPS_RIRB_DELAY handling into top drivers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 7d9a180895ee8c301df7f9447429009795c56c21 upstream. AZX_DCAPS_RIRB_DELAY is dedicated only for Nvidia and its purpose is just to set a flag in bus. So it's

[PATCH 4.4 30/69] xhci: add restart quirk for Intel Wildcatpoint PCH

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Nyman commit 4c39135aa412d2f1381e43802523da110ca7855c upstream. xHC in Wildcatpoint-LP PCH is similar to LynxPoint-LP and need the same quirks to prevent machines from spurious restart

[PATCH 4.4 12/69] ALSA: hda - allow 40 bit DMA mask for NVidia devices

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 3ab7511eafdd5c4f40d2832f09554478dfbea170 upstream. Commit 49d9e77e72cf ("ALSA: hda - Fix system panic when DMA > 40 bits for Nvidia audio controllers") simply disabled

[PATCH 4.4 33/69] dm: free io_barrier after blk_cleanup_queue call

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tahsin Erdogan commit d09960b0032174eb493c4c13be5b9c9ef36dc9a7 upstream. dm_old_request_fn() has paths that access md->io_barrier. The party destroying io_barrier should ensure that no future

[PATCH 4.4 11/69] ALSA: hda - Raise AZX_DCAPS_RIRB_DELAY handling into top drivers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 7d9a180895ee8c301df7f9447429009795c56c21 upstream. AZX_DCAPS_RIRB_DELAY is dedicated only for Nvidia and its purpose is just to set a flag in bus. So it's better to be set

[PATCH 4.4 32/69] USB: serial: cp210x: fix tiocmget error handling

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit de24e0a108bc48062e1c7acaa97014bce32a919f upstream. The current tiocmget implementation would fail to report errors up the stack and instead leaked a few

[PATCH 4.4 14/69] ALSA: hda - Fix headset mic detection problem for two Dell laptops

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hui Wang commit 6aecd8715802d23dc6a0859b50c62d2b0a99de3a upstream. They uses the codec ALC255, and have the different pin cfg definition from the ones in the existing

[PATCH 4.4 14/69] ALSA: hda - Fix headset mic detection problem for two Dell laptops

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hui Wang commit 6aecd8715802d23dc6a0859b50c62d2b0a99de3a upstream. They uses the codec ALC255, and have the different pin cfg definition from the ones in the existing pin quirk table. Now

[PATCH 4.4 32/69] USB: serial: cp210x: fix tiocmget error handling

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit de24e0a108bc48062e1c7acaa97014bce32a919f upstream. The current tiocmget implementation would fail to report errors up the stack and instead leaked a few bits from the stack

[PATCH 4.4 06/69] mm/list_lru.c: avoid error-path NULL pointer deref

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Polakov commit 1bc11d70b5db7c6bb1414b283d7f09b1fe1ac0d0 upstream. As described in https://bugzilla.kernel.org/show_bug.cgi?id=177821: After some analysis it

[PATCH 4.4 24/69] xhci: use default USB_RESUME_TIMEOUT when resuming ports.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Nyman commit 7d3b016a6f5a0fa610dfd02b05654c08fa4ae514 upstream. USB2 host inititated resume, and system suspend bus resume need to use the same

[PATCH 4.4 06/69] mm/list_lru.c: avoid error-path NULL pointer deref

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Polakov commit 1bc11d70b5db7c6bb1414b283d7f09b1fe1ac0d0 upstream. As described in https://bugzilla.kernel.org/show_bug.cgi?id=177821: After some analysis it seems to be that the

[PATCH 4.4 24/69] xhci: use default USB_RESUME_TIMEOUT when resuming ports.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Nyman commit 7d3b016a6f5a0fa610dfd02b05654c08fa4ae514 upstream. USB2 host inititated resume, and system suspend bus resume need to use the same USB_RESUME_TIMEOUT as elsewhere. This

[PATCH 4.4 19/69] ubifs: Fix regression in ubifs_readdir()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Richard Weinberger commit a00052a296e54205cf238c75bd98d17d5d02a6db upstream. Commit c83ed4c9dbb35 ("ubifs: Abort readdir upon error") broke overlayfs support because the fix

[PATCH 4.4 19/69] ubifs: Fix regression in ubifs_readdir()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Richard Weinberger commit a00052a296e54205cf238c75bd98d17d5d02a6db upstream. Commit c83ed4c9dbb35 ("ubifs: Abort readdir upon error") broke overlayfs support because the fix exposed an

[PATCH 4.4 05/69] libxfs: clean up _calc_dquots_per_chunk

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 58d789678546d46d7bbd809dd7dab417c0f23655 upstream. The function xfs_calc_dquots_per_chunk takes a parameter in units of basic blocks. The

[PATCH 4.4 22/69] USB: serial: fix potential NULL-dereference at probe

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 126d26f66d9890a69158812a6caa248c05359daa upstream. Make sure we have at least one port before attempting to register a console. Currently, at least one

[PATCH 4.4 26/69] GenWQE: Fix bad page access during abort of resource allocation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gerald Schaefer commit a7a7aeefbca2982586ba2c9fd7739b96416a6d1d upstream. When interrupting an application which was allocating DMAable memory, it was possible,

[PATCH 4.4 05/69] libxfs: clean up _calc_dquots_per_chunk

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 58d789678546d46d7bbd809dd7dab417c0f23655 upstream. The function xfs_calc_dquots_per_chunk takes a parameter in units of basic blocks. The kernel seems to get the units

[PATCH 4.4 22/69] USB: serial: fix potential NULL-dereference at probe

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 126d26f66d9890a69158812a6caa248c05359daa upstream. Make sure we have at least one port before attempting to register a console. Currently, at least one driver binds to a

[PATCH 4.4 26/69] GenWQE: Fix bad page access during abort of resource allocation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gerald Schaefer commit a7a7aeefbca2982586ba2c9fd7739b96416a6d1d upstream. When interrupting an application which was allocating DMAable memory, it was possible, that the DMA memory was

[PATCH 4.4 01/69] i2c: xgene: Avoid dma_buffer overrun

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hoan Tran commit 603616017c35f4d0fbdbcace72adf9bf949c4a65 upstream. SMBus block command uses the first byte of buffer for the data length. The dma_buffer should be increased by

[PATCH 4.4 04/69] h8300: fix syscall restarting

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mark Rutland commit 21753583056d48a5fad964d6f272e28168426845 upstream. Back in commit f56141e3e2d9 ("all arches, signal: move restart_block to struct task_struct"), all

[PATCH 4.4 00/69] 4.4.31-stable review

This is the start of the stable review cycle for the 4.4.31 release. There are 69 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 Nov 11 10:28:46 UTC 2016. Anything

[PATCH 4.4 01/69] i2c: xgene: Avoid dma_buffer overrun

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hoan Tran commit 603616017c35f4d0fbdbcace72adf9bf949c4a65 upstream. SMBus block command uses the first byte of buffer for the data length. The dma_buffer should be increased by 1 to avoid the

[PATCH 4.4 04/69] h8300: fix syscall restarting

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mark Rutland commit 21753583056d48a5fad964d6f272e28168426845 upstream. Back in commit f56141e3e2d9 ("all arches, signal: move restart_block to struct task_struct"), all architectures and core

[PATCH 4.4 00/69] 4.4.31-stable review

This is the start of the stable review cycle for the 4.4.31 release. There are 69 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 Nov 11 10:28:46 UTC 2016. Anything

[PATCH v2] leds: ledtrig-heartbeat: Make top brightness adjustable

LED class heartbeat trigger allowed only for blinking with max_brightness value. This patch adds more flexibility by exploiting part of LED core software blink infrastructure. Signed-off-by: Jacek Anaszewski Cc: Pavel Machek Cc: Hans de Goede

[PATCH v2] leds: ledtrig-heartbeat: Make top brightness adjustable

LED class heartbeat trigger allowed only for blinking with max_brightness value. This patch adds more flexibility by exploiting part of LED core software blink infrastructure. Signed-off-by: Jacek Anaszewski Cc: Pavel Machek Cc: Hans de Goede --- Changes since v1: - after introduction of

Re: module: When modifying a module's text ignore modules which are going away too

+++ Aaron Tomlin [07/11/16 11:46 +]: Hi Jessica, Any thoughts? Hi Aaron, Thanks for your patience as I slowly work through a large swath of emails :-) Anyway, this looks fine to me. A going module's text should be (or soon will be) rw anyway, so checking for going modules in the ro case

Re: module: When modifying a module's text ignore modules which are going away too

+++ Aaron Tomlin [07/11/16 11:46 +]: Hi Jessica, Any thoughts? Hi Aaron, Thanks for your patience as I slowly work through a large swath of emails :-) Anyway, this looks fine to me. A going module's text should be (or soon will be) rw anyway, so checking for going modules in the ro case

Re: [PATCH -v4 1/8] locking/drm: Kill mutex trickery

On Fri, Oct 07, 2016 at 05:43:51PM +0200, Peter Zijlstra wrote: > On Fri, Oct 07, 2016 at 04:52:44PM +0200, Peter Zijlstra wrote: > > Poking at lock internals is not cool. Since I'm going to change the > > implementation this will break, take it out. > > > So something like the below would serve

Re: [PATCH -v4 1/8] locking/drm: Kill mutex trickery

On Fri, Oct 07, 2016 at 05:43:51PM +0200, Peter Zijlstra wrote: > On Fri, Oct 07, 2016 at 04:52:44PM +0200, Peter Zijlstra wrote: > > Poking at lock internals is not cool. Since I'm going to change the > > implementation this will break, take it out. > > > So something like the below would serve

Re: [PATCH v3 2/3] PCI: qcom: add support to msm8996 PCIE controller

Hi, On Fri, Nov 4, 2016 at 6:29 PM, Srinivas Kandagatla wrote: > This patch adds support to msm8996/apq8096 pcie, MSM8996 supports > Gen 1/2, One lane, 3 pcie root-complex with support to MSI and > legacy interrupts and it conforms to PCI Express Base 2.1

Re: [PATCH v3 2/3] PCI: qcom: add support to msm8996 PCIE controller

Hi, On Fri, Nov 4, 2016 at 6:29 PM, Srinivas Kandagatla wrote: > This patch adds support to msm8996/apq8096 pcie, MSM8996 supports > Gen 1/2, One lane, 3 pcie root-complex with support to MSI and > legacy interrupts and it conforms to PCI Express Base 2.1 specification. > > This patch adds

Re: [PATCH v2 00/12] mm: page migration enhancement for thp

On 11/08/2016 05:01 AM, Naoya Horiguchi wrote: > Hi everyone, > > I've updated thp migration patches for v4.9-rc2-mmotm-2016-10-27-18-27 > with feedbacks for ver.1. > > General description (no change since ver.1) > === > > This patchset enhances page

Re: [PATCH v2 00/12] mm: page migration enhancement for thp

On 11/08/2016 05:01 AM, Naoya Horiguchi wrote: > Hi everyone, > > I've updated thp migration patches for v4.9-rc2-mmotm-2016-10-27-18-27 > with feedbacks for ver.1. > > General description (no change since ver.1) > === > > This patchset enhances page

Re: [PATCH v10 3/7] x86/arch_prctl: Add do_arch_prctl_common

On Tue, Nov 08, 2016 at 10:39:52AM -0800, Kyle Huey wrote: > Add do_arch_prctl_common to handle arch_prctls that are not specific to 64 do_arch_prctl_common() > bits. Call it from the syscall entry point, but not any of the other "... to 64-bit mode." Or something like that... >

Re: [PATCH v10 3/7] x86/arch_prctl: Add do_arch_prctl_common

On Tue, Nov 08, 2016 at 10:39:52AM -0800, Kyle Huey wrote: > Add do_arch_prctl_common to handle arch_prctls that are not specific to 64 do_arch_prctl_common() > bits. Call it from the syscall entry point, but not any of the other "... to 64-bit mode." Or something like that... >

Re: [PATCH] [RFC] drivers: dma-coherent: use MEMREMAP_WB instead of MEMREMAP_WC

Hi, On Wed, Nov 09, 2016 at 06:47:26PM +0900, Jaewon Kim wrote: On 2016년 11월 09일 18:27, Brian Starkey wrote: Hi Jaewon, On Wed, Nov 09, 2016 at 06:10:09PM +0900, Jaewon Kim wrote: Commit 6b03ae0d42bf (drivers: dma-coherent: use MEMREMAP_WC for DMA_MEMORY_MA) added MEMREMAP_WC for

Re: [PATCH] [RFC] drivers: dma-coherent: use MEMREMAP_WB instead of MEMREMAP_WC

Hi, On Wed, Nov 09, 2016 at 06:47:26PM +0900, Jaewon Kim wrote: On 2016년 11월 09일 18:27, Brian Starkey wrote: Hi Jaewon, On Wed, Nov 09, 2016 at 06:10:09PM +0900, Jaewon Kim wrote: Commit 6b03ae0d42bf (drivers: dma-coherent: use MEMREMAP_WC for DMA_MEMORY_MA) added MEMREMAP_WC for

Re: [PATCH] net/mlx4_en: Fix bpf_prog_add ref_cnt in mlx4

On 11/09/2016 10:45 AM, Zhiyi Sun wrote: On Wed, Nov 09, 2016 at 10:05:31AM +0100, Daniel Borkmann wrote: On 11/09/2016 08:35 AM, Zhiyi Sun wrote: There are rx_ring_num queues. Each queue will load xdp prog. So bpf_prog_add() should add rx_ring_num to ref_cnt. Signed-off-by: Zhiyi Sun

Re: [PATCH] net/mlx4_en: Fix bpf_prog_add ref_cnt in mlx4

On 11/09/2016 10:45 AM, Zhiyi Sun wrote: On Wed, Nov 09, 2016 at 10:05:31AM +0100, Daniel Borkmann wrote: On 11/09/2016 08:35 AM, Zhiyi Sun wrote: There are rx_ring_num queues. Each queue will load xdp prog. So bpf_prog_add() should add rx_ring_num to ref_cnt. Signed-off-by: Zhiyi Sun Your

Re: [PATCH] proc: optimize render_sigset_t()

On Wed, Nov 9, 2016 at 12:37 AM, Andrei Vagin wrote: > @@ -245,10 +247,13 @@ void render_sigset_t(struct seq_file *m, const char > *header, > if (sigismember(set, i+2)) x |= 2; > if (sigismember(set, i+3)) x |= 4; > if

Re: [PATCH] proc: optimize render_sigset_t()

On Wed, Nov 9, 2016 at 12:37 AM, Andrei Vagin wrote: > @@ -245,10 +247,13 @@ void render_sigset_t(struct seq_file *m, const char > *header, > if (sigismember(set, i+2)) x |= 2; > if (sigismember(set, i+3)) x |= 4; > if (sigismember(set, i+4)) x |=

Re: [PATCH v4 0/4] MIPS: Remote processor driver

On Wed, 2 Nov 2016, Matt Redfearn wrote: > The MIPS remote processor driver allows non-Linux firmware to take > control of and execute on one of the systems VPEs. The CPU must be > offlined from Linux first. A sysfs interface is created which allows > firmware to be loaded and changed at runtime.

Re: [PATCH v4 0/4] MIPS: Remote processor driver

On Wed, 2 Nov 2016, Matt Redfearn wrote: > The MIPS remote processor driver allows non-Linux firmware to take > control of and execute on one of the systems VPEs. The CPU must be > offlined from Linux first. A sysfs interface is created which allows > firmware to be loaded and changed at runtime.

Re: [PATCH v7 3/3] drm/fence: add out-fences support

On Wed, Nov 09, 2016 at 11:39:11AM +0900, Gustavo Padovan wrote: > > On Tue, Nov 08, 2016 at 03:54:50PM +0900, Gustavo Padovan wrote: > > > + if (!access_ok(VERIFY_WRITE, fence_ptr, sizeof(*fence_ptr))) > > > + return -EFAULT; > > > > Same comment about igt coverage I made

Re: [PATCH v7 3/3] drm/fence: add out-fences support

On Wed, Nov 09, 2016 at 11:39:11AM +0900, Gustavo Padovan wrote: > > On Tue, Nov 08, 2016 at 03:54:50PM +0900, Gustavo Padovan wrote: > > > + if (!access_ok(VERIFY_WRITE, fence_ptr, sizeof(*fence_ptr))) > > > + return -EFAULT; > > > > Same comment about igt coverage I made

<    13   14   15   16   17   18   19   20   >