[RFC PATCH] mtd: spi-nor: rockchip_sfc_runtime_suspend() can be static

Fixes: dbc2d867929a ("mtd: spi-nor: add rockchip serial flash controller driver") Signed-off-by: Fengguang Wu --- rockchip-sfc.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/mtd/spi-nor/rockchip-sfc.c

Re: [PATCH 0/3] Fix broken bananapi m2 devicetree/regulators

On 02/11/2018 01:07 AM, Philipp Rossak wrote: On 10.02.2018 22:08, Sergey Suloev wrote: On 02/11/2018 12:01 AM, Philipp Rossak wrote: Hey Sergey, Thanks for mentioning, but I think the problem has nothing to do with those patches. I tested them with the v4.15.0 Kernel since this is the

[RFC PATCH] mtd: spi-nor: rockchip_sfc_runtime_suspend() can be static

Fixes: dbc2d867929a ("mtd: spi-nor: add rockchip serial flash controller driver") Signed-off-by: Fengguang Wu --- rockchip-sfc.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/mtd/spi-nor/rockchip-sfc.c b/drivers/mtd/spi-nor/rockchip-sfc.c index

Re: [PATCH 0/3] Fix broken bananapi m2 devicetree/regulators

On 02/11/2018 01:07 AM, Philipp Rossak wrote: On 10.02.2018 22:08, Sergey Suloev wrote: On 02/11/2018 12:01 AM, Philipp Rossak wrote: Hey Sergey, Thanks for mentioning, but I think the problem has nothing to do with those patches. I tested them with the v4.15.0 Kernel since this is the

Re: [PATCH v8 2/3] mtd: spi-nor: add rockchip serial flash controller driver

Hi Shawn, I love your patch! Perhaps something to improve: [auto build test WARNING on robh/for-next] [also build test WARNING on v4.15 next-20180209] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v8 2/3] mtd: spi-nor: add rockchip serial flash controller driver

Hi Shawn, I love your patch! Perhaps something to improve: [auto build test WARNING on robh/for-next] [also build test WARNING on v4.15 next-20180209] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 5/7] watchdog: mtk: allow setting timeout in devicetree

On Sat, 2018-02-10 at 17:52 -0800, Guenter Roeck wrote: > On 02/10/2018 12:12 PM, Marcus Folkesson wrote: > > Hello Sean, > > > > On Sat, Feb 10, 2018 at 01:43:28PM +0100, Marcus Folkesson wrote: > >> Hello Sean, > >> > >> On Sat, Feb 10, 2018 at 07:10:02PM +0800, Sean Wang wrote: > >>> > >>> Hi,

Re: [PATCH v2 5/7] watchdog: mtk: allow setting timeout in devicetree

On Sat, 2018-02-10 at 17:52 -0800, Guenter Roeck wrote: > On 02/10/2018 12:12 PM, Marcus Folkesson wrote: > > Hello Sean, > > > > On Sat, Feb 10, 2018 at 01:43:28PM +0100, Marcus Folkesson wrote: > >> Hello Sean, > >> > >> On Sat, Feb 10, 2018 at 07:10:02PM +0800, Sean Wang wrote: > >>> > >>> Hi,

Re: [PATCH 3.2 39/79] ocfs2: should wait dio before inode lock in ocfs2_setattr()

Hi Ben, ocfs2_dio_end_io_write() was introduced in 4.6 and the problem this patch fixes is only exist in the kernel 4.6 and above 4.6. Thanks, Alex On 2018/2/11 12:20, Ben Hutchings wrote: > 3.2.99-rc1 review patch. If anyone has any objections, please let me know. > > -- > >

Re: [PATCH 3.2 39/79] ocfs2: should wait dio before inode lock in ocfs2_setattr()

Hi Ben, ocfs2_dio_end_io_write() was introduced in 4.6 and the problem this patch fixes is only exist in the kernel 4.6 and above 4.6. Thanks, Alex On 2018/2/11 12:20, Ben Hutchings wrote: > 3.2.99-rc1 review patch. If anyone has any objections, please let me know. > > -- > >

Re: [PATCH 0/3] Fix broken bananapi m2 devicetree/regulators

On 02/11/2018 01:07 AM, Philipp Rossak wrote: On 10.02.2018 22:08, Sergey Suloev wrote: On 02/11/2018 12:01 AM, Philipp Rossak wrote: Hey Sergey, Thanks for mentioning, but I think the problem has nothing to do with those patches. I tested them with the v4.15.0 Kernel since this is the

Re: [PATCH 0/3] Fix broken bananapi m2 devicetree/regulators

On 02/11/2018 01:07 AM, Philipp Rossak wrote: On 10.02.2018 22:08, Sergey Suloev wrote: On 02/11/2018 12:01 AM, Philipp Rossak wrote: Hey Sergey, Thanks for mentioning, but I think the problem has nothing to do with those patches. I tested them with the v4.15.0 Kernel since this is the

Re: [RFC PATCH 4/7] kconfig: support new special property shell=

On Sat, Feb 10, 2018 at 8:46 PM, Linus Torvalds wrote: > > Argh. I wanted to get rid of all that entirely, and simplify this all. > The mentioned script (and bugzilla) was from 2006, I assumed this was > all historical. > > But if it has broken again since, I guess

Re: [RFC PATCH 4/7] kconfig: support new special property shell=

On Sat, Feb 10, 2018 at 8:46 PM, Linus Torvalds wrote: > > Argh. I wanted to get rid of all that entirely, and simplify this all. > The mentioned script (and bugzilla) was from 2006, I assumed this was > all historical. > > But if it has broken again since, I guess we need to have a silly script.

/kbuild/src/consumer/include/linux/kasan.h:28:41: error: 'KASAN_SHADOW_SCALE_SHIFT' undeclared; did you mean 'KASAN_SHADOW_START'?

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d48fcbd864a008802a90c58a9ceddd9436d11a49 commit: 917538e212a2c080af95ccb4376c5387fac08176 kasan: clean up KASAN_SHADOW_SCALE_SHIFT usage date: 4 days ago config: xtensa-allyesconfig (attached as .config)

/kbuild/src/consumer/include/linux/kasan.h:28:41: error: 'KASAN_SHADOW_SCALE_SHIFT' undeclared; did you mean 'KASAN_SHADOW_START'?

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d48fcbd864a008802a90c58a9ceddd9436d11a49 commit: 917538e212a2c080af95ccb4376c5387fac08176 kasan: clean up KASAN_SHADOW_SCALE_SHIFT usage date: 4 days ago config: xtensa-allyesconfig (attached as .config)

Re: [PATCHv2 1/2] zsmalloc: introduce zs_huge_object() function

Some more nitpicks :) On Sat, Feb 10, 2018 at 05:23:21PM +0900, Sergey Senozhatsky wrote: > Not every object can be share its zspage with other objects, e.g. > when the object is as big as zspage or nearly as big a zspage. > For such objects zsmalloc has a so called huge class - every object >

Re: [PATCHv2 1/2] zsmalloc: introduce zs_huge_object() function

Some more nitpicks :) On Sat, Feb 10, 2018 at 05:23:21PM +0900, Sergey Senozhatsky wrote: > Not every object can be share its zspage with other objects, e.g. > when the object is as big as zspage or nearly as big a zspage. > For such objects zsmalloc has a so called huge class - every object >

[PATCH v2] Input: gpio_keys: Add level trigger support for GPIO keys

On some platforms (such as Spreadtrum platform), the GPIO keys can only be triggered by level type. So this patch introduces one property to indicate if the GPIO trigger type is level trigger or edge trigger. Signed-off-by: Baolin Wang --- Changes since v1: - Diable the

[PATCH v2] Input: gpio_keys: Add level trigger support for GPIO keys

On some platforms (such as Spreadtrum platform), the GPIO keys can only be triggered by level type. So this patch introduces one property to indicate if the GPIO trigger type is level trigger or edge trigger. Signed-off-by: Baolin Wang --- Changes since v1: - Diable the GPIO irq until reversing

The usage of page_mapping() in architecture code

Sorry for bothering, forget to Cc LKML in the original email. Hi, All, To optimize the scalability of swap cache, it is made more dynamic than before. That is, after being swapped off, the address space of the swap device will be freed too. So the usage of page_mapping() need to be audited to

The usage of page_mapping() in architecture code

Sorry for bothering, forget to Cc LKML in the original email. Hi, All, To optimize the scalability of swap cache, it is made more dynamic than before. That is, after being swapped off, the address space of the swap device will be freed too. So the usage of page_mapping() need to be audited to

drivers/net/ethernet/intel/i40e/i40e_ethtool.c:4326:6: error: implicit declaration of function 'cmpxchg64'; did you mean 'cmpxchg'?

Hi Alice, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d48fcbd864a008802a90c58a9ceddd9436d11a49 commit: 60f481b9703867330dc6010868054f68f6d52f7a i40e: change flags to use 64 bits date: 2 weeks ago config:

drivers/net/ethernet/intel/i40e/i40e_ethtool.c:4326:6: error: implicit declaration of function 'cmpxchg64'; did you mean 'cmpxchg'?

Hi Alice, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d48fcbd864a008802a90c58a9ceddd9436d11a49 commit: 60f481b9703867330dc6010868054f68f6d52f7a i40e: change flags to use 64 bits date: 2 weeks ago config:

Re: [PATCH] f2fs: set_code_data in move_data_block

OK, Got it. On 2018/2/11 11:50, Chao Yu wrote: On 2018/2/11 11:34, Yunlong Song wrote: Ping... move_data_block misses set_cold_data, then the F2FS_WB_CP_DATA will lack these data pages in move_data_block, and write_checkpoint can not make sure this pages committed to the flash. Hmm.. data

Re: [PATCH] f2fs: set_code_data in move_data_block

OK, Got it. On 2018/2/11 11:50, Chao Yu wrote: On 2018/2/11 11:34, Yunlong Song wrote: Ping... move_data_block misses set_cold_data, then the F2FS_WB_CP_DATA will lack these data pages in move_data_block, and write_checkpoint can not make sure this pages committed to the flash. Hmm.. data

Re: [PATCH] seq_file: remove redundant assignment of index to m->index

On Sun, Feb 11, 2018 at 9:02 AM, Matthew Wilcox wrote: > On Sat, Feb 10, 2018 at 10:04:23AM -0800, Joe Perches wrote: >> > @@ -120,14 +120,12 @@ static int traverse(struct seq_file *m, loff_t >> > offset) >> > if (pos + m->count > offset) { >> > m->from

Re: [PATCH] seq_file: remove redundant assignment of index to m->index

On Sun, Feb 11, 2018 at 9:02 AM, Matthew Wilcox wrote: > On Sat, Feb 10, 2018 at 10:04:23AM -0800, Joe Perches wrote: >> > @@ -120,14 +120,12 @@ static int traverse(struct seq_file *m, loff_t >> > offset) >> > if (pos + m->count > offset) { >> > m->from = offset - pos; >> >

Re: [kselftests] compaction_test is blocked

On 02/10/2018 05:11 AM, Dan Rue wrote: On Fri, Feb 09, 2018 at 03:53:59PM +0800, Li Zhijian wrote: Hi kselftests is integrated Intel 0Day project. Sometimes we found compaction_test is blocked for more than 1 hours until i kill it. Try to figure out where it is running, i added some log to

Re: [kselftests] compaction_test is blocked

On 02/10/2018 05:11 AM, Dan Rue wrote: On Fri, Feb 09, 2018 at 03:53:59PM +0800, Li Zhijian wrote: Hi kselftests is integrated Intel 0Day project. Sometimes we found compaction_test is blocked for more than 1 hours until i kill it. Try to figure out where it is running, i added some log to

Re: [PATCH] KVM: lapic: stop advertising DIRECTED_EOI when in-kernel IOAPIC is in use

On Fri, Feb 09, 2018 at 02:01:33PM +0100, Vitaly Kuznetsov wrote: > Devices which use level-triggered interrupts under Windows 2016 with > Hyper-V role enabled don't work: Windows disables EOI broadcast in SPIV > unconditionally. Our in-kernel IOAPIC implementation emulates an old IOAPIC > version

Re: [PATCH] KVM: lapic: stop advertising DIRECTED_EOI when in-kernel IOAPIC is in use

On Fri, Feb 09, 2018 at 02:01:33PM +0100, Vitaly Kuznetsov wrote: > Devices which use level-triggered interrupts under Windows 2016 with > Hyper-V role enabled don't work: Windows disables EOI broadcast in SPIV > unconditionally. Our in-kernel IOAPIC implementation emulates an old IOAPIC > version

[PATCH 3.2 08/79] KVM: nVMX: set IDTR and GDTR limits when loading L1 host state

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Ladi Prosek commit 21f2d551183847bc7fbe8d866151d00cdad18752 upstream. Intel SDM 27.5.2 Loading Host Segment and Descriptor-Table Registers: "The GDTR and IDTR limits are

[PATCH 3.2 04/79] PCI/AER: Report non-fatal errors only to the affected endpoint

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Gabriele Paoloni commit 86acc790717fb60fb51ea3095084e331d8711c74 upstream. Previously, if an non-fatal error was reported by an endpoint, we called

[PATCH 3.2 79/79] kaiser: Set _PAGE_NX only if supported

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Lepton Wu This finally resolve crash if loaded under qemu + haxm. Haitao Shan pointed out that the reason of that crash is that NX bit get set for page tables. It seems we

[PATCH 3.2 08/79] KVM: nVMX: set IDTR and GDTR limits when loading L1 host state

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Ladi Prosek commit 21f2d551183847bc7fbe8d866151d00cdad18752 upstream. Intel SDM 27.5.2 Loading Host Segment and Descriptor-Table Registers: "The GDTR and IDTR limits are each set to H."

[PATCH 3.2 04/79] PCI/AER: Report non-fatal errors only to the affected endpoint

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Gabriele Paoloni commit 86acc790717fb60fb51ea3095084e331d8711c74 upstream. Previously, if an non-fatal error was reported by an endpoint, we called report_error_detected() for the endpoint,

[PATCH 3.2 79/79] kaiser: Set _PAGE_NX only if supported

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Lepton Wu This finally resolve crash if loaded under qemu + haxm. Haitao Shan pointed out that the reason of that crash is that NX bit get set for page tables. It seems we missed checking if

[PATCH 3.2 06/79] USB: serial: garmin_gps: fix memory leak on probe errors

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 74d471b598444b7f2d964930f7234779c80960a0 upstream. Make sure to free the port private data before returning after a failed probe attempt. Fixes:

[PATCH 3.2 01/79] Input: adxl34x - do not treat FIFO_MODE() as boolean

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 1dbc080c9ef6bcfba652ef0d6ae919b8c7c85a1d upstream. FIFO_MODE() is a macro expression with a '<<' operator, which gcc points out could be misread as a '<':

[PATCH 3.2 06/79] USB: serial: garmin_gps: fix memory leak on probe errors

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 74d471b598444b7f2d964930f7234779c80960a0 upstream. Make sure to free the port private data before returning after a failed probe attempt. Fixes: 1da177e4c3f4

[PATCH 3.2 01/79] Input: adxl34x - do not treat FIFO_MODE() as boolean

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 1dbc080c9ef6bcfba652ef0d6ae919b8c7c85a1d upstream. FIFO_MODE() is a macro expression with a '<<' operator, which gcc points out could be misread as a '<':

[PATCH 3.2 00/79] 3.2.99-rc1 review

This is the start of the stable review cycle for the 3.2.99 release. There are 79 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Tue Feb 13 12:00:00 UTC 2018. Anything

[PATCH 3.2 03/79] rtc: set the alarm to the next expiring timer

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Alexandre Belloni commit 74717b28cb32e1ad3c1042cafd76b264c8c0f68d upstream. If there is any non expired timer in the queue, the RTC alarm is never set.

[PATCH 3.2 02/79] rtc: interface: ignore expired timers when enqueuing new timers

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Colin Ian King commit 2b2f5ff00f63847d95adad6289bd8b05f5983dd5 upstream. This patch fixes a RTC wakealarm issue, namely, the event fires during hibernate and is not

[PATCH 3.2 00/79] 3.2.99-rc1 review

This is the start of the stable review cycle for the 3.2.99 release. There are 79 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Tue Feb 13 12:00:00 UTC 2018. Anything

[PATCH 3.2 03/79] rtc: set the alarm to the next expiring timer

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Alexandre Belloni commit 74717b28cb32e1ad3c1042cafd76b264c8c0f68d upstream. If there is any non expired timer in the queue, the RTC alarm is never set. This is an issue when adding a timer

[PATCH 3.2 02/79] rtc: interface: ignore expired timers when enqueuing new timers

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Colin Ian King commit 2b2f5ff00f63847d95adad6289bd8b05f5983dd5 upstream. This patch fixes a RTC wakealarm issue, namely, the event fires during hibernate and is not cleared from the list,

[PATCH 3.2 17/79] l2tp: ensure sessions are freed after their PPPOL2TP socket

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault commit cdd10c9627496ad25c87ce6394e29752253c69d3 upstream. If l2tp_tunnel_delete() or l2tp_tunnel_closeall() deletes a session right after

[PATCH 3.2 17/79] l2tp: ensure sessions are freed after their PPPOL2TP socket

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault commit cdd10c9627496ad25c87ce6394e29752253c69d3 upstream. If l2tp_tunnel_delete() or l2tp_tunnel_closeall() deletes a session right after pppol2tp_release() orphaned its

[PATCH 3.2 16/79] l2tp: push all ppp pseudowire shutdown through .release handler

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Tom Parkin commit cf2f5c886a209377daefd5d2ba0bcd49c3887813 upstream. If userspace deletes a ppp pseudowire using the netlink API, either by directly deleting the session

[PATCH 3.2 16/79] l2tp: push all ppp pseudowire shutdown through .release handler

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Tom Parkin commit cf2f5c886a209377daefd5d2ba0bcd49c3887813 upstream. If userspace deletes a ppp pseudowire using the netlink API, either by directly deleting the session or by deleting the

[PATCH 3.2 68/79] RDS: null pointer dereference in rds_atomic_free_op

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Mohamed Ghannam commit 7d11f77f84b27cef452cee332f4e469503084737 upstream. set rm->atomic.op_active to 0 when rds_pin_pages() fails or the user supplied address is

[PATCH 3.2 78/79] kaiser: Set _PAGE_NX only if supported

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck This resolves a crash if loaded under qemu + haxm under windows. See https://www.spinics.net/lists/kernel/msg2689835.html for details. Here is a boot log (the

[PATCH 3.2 10/79] IB/srp: Avoid that a cable pull can trigger a kernel crash

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 8a0d18c62121d3c554a83eb96e2752861d84d937 upstream. This patch fixes the following kernel crash: general protection fault: [#1] PREEMPT SMP

[PATCH 3.2 68/79] RDS: null pointer dereference in rds_atomic_free_op

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Mohamed Ghannam commit 7d11f77f84b27cef452cee332f4e469503084737 upstream. set rm->atomic.op_active to 0 when rds_pin_pages() fails or the user supplied address is invalid, this prevents a NULL

[PATCH 3.2 78/79] kaiser: Set _PAGE_NX only if supported

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck This resolves a crash if loaded under qemu + haxm under windows. See https://www.spinics.net/lists/kernel/msg2689835.html for details. Here is a boot log (the log is from

[PATCH 3.2 10/79] IB/srp: Avoid that a cable pull can trigger a kernel crash

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 8a0d18c62121d3c554a83eb96e2752861d84d937 upstream. This patch fixes the following kernel crash: general protection fault: [#1] PREEMPT SMP Workqueue: ib_mad2

[PATCH 3.2 14/79] l2tp: add session reorder queue purge function to core

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Tom Parkin commit 48f72f92b31431c40279b0fba6c5588e07e67d95 upstream. If an l2tp session is deleted, it is necessary to delete skbs in-flight on the session's reorder queue

[PATCH 3.2 14/79] l2tp: add session reorder queue purge function to core

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Tom Parkin commit 48f72f92b31431c40279b0fba6c5588e07e67d95 upstream. If an l2tp session is deleted, it is necessary to delete skbs in-flight on the session's reorder queue before taking it

[PATCH 3.16 020/136] elf_fdpic: fix unused variable warning

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 11e3e8d6d9274bf630859b4c47bc4e4d76f289db upstream. The elf_fdpic code shows a harmless warning when built with MMU disabled, I ran into this now that fdpic

[PATCH 3.16 060/136] ACPI / APEI: Replace ioremap_page_range() with fixmap

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: James Morse commit 4f89fa286f6729312e227e7c2d764e8e7b9d340e upstream. Replace ghes_io{re,un}map_pfn_{nmi,irq}()s use of ioremap_page_range() with __set_fixmap() as

[PATCH 3.16 067/136] ima: fix hash algorithm initialization

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Boshi Wang commit ebe7c0a7be92bbd34c6ff5b55810546a0ee05bee upstream. The hash_setup function always sets the hash_setup_done flag, even when the hash algorithm is

[PATCH 3.16 020/136] elf_fdpic: fix unused variable warning

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 11e3e8d6d9274bf630859b4c47bc4e4d76f289db upstream. The elf_fdpic code shows a harmless warning when built with MMU disabled, I ran into this now that fdpic is available

[PATCH 3.16 060/136] ACPI / APEI: Replace ioremap_page_range() with fixmap

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: James Morse commit 4f89fa286f6729312e227e7c2d764e8e7b9d340e upstream. Replace ghes_io{re,un}map_pfn_{nmi,irq}()s use of ioremap_page_range() with __set_fixmap() as ioremap_page_range() may

[PATCH 3.16 067/136] ima: fix hash algorithm initialization

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Boshi Wang commit ebe7c0a7be92bbd34c6ff5b55810546a0ee05bee upstream. The hash_setup function always sets the hash_setup_done flag, even when the hash algorithm is invalid. This prevents the

[PATCH 3.16 028/136] net/9p: Switch to wait_event_killable()

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Tuomas Tynkkynen commit 9523feac272ccad2ad8186ba4fcc89103754de52 upstream. Because userspace gets Very Unhappy when calls like stat() and execve() return -EINTR on 9p

[PATCH 3.16 028/136] net/9p: Switch to wait_event_killable()

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Tuomas Tynkkynen commit 9523feac272ccad2ad8186ba4fcc89103754de52 upstream. Because userspace gets Very Unhappy when calls like stat() and execve() return -EINTR on 9p filesystem mounts. For

[PATCH 3.16 034/136] l2tp: initialise l2tp_eth sessions before registering them

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault commit ee28de6bbd78c2e18111a0aef43ea746f28d2073 upstream. Sessions must be initialised before being made externally visible by l2tp_session_register().

[PATCH 3.16 062/136] kprobes, x86/alternatives: Use text_mutex to protect smp_alt_modules

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Zhou Chengming commit e846d13958066828a9483d862cc8370a72fadbb6 upstream. We use alternatives_text_reserved() to check if the address is in the fixed pieces of

[PATCH 3.16 062/136] kprobes, x86/alternatives: Use text_mutex to protect smp_alt_modules

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Zhou Chengming commit e846d13958066828a9483d862cc8370a72fadbb6 upstream. We use alternatives_text_reserved() to check if the address is in the fixed pieces of alternative reserved, but the

[PATCH 3.16 034/136] l2tp: initialise l2tp_eth sessions before registering them

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault commit ee28de6bbd78c2e18111a0aef43ea746f28d2073 upstream. Sessions must be initialised before being made externally visible by l2tp_session_register(). Otherwise the session

[PATCH 3.16 025/136] IB/srp: Avoid that a cable pull can trigger a kernel crash

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 8a0d18c62121d3c554a83eb96e2752861d84d937 upstream. This patch fixes the following kernel crash: general protection fault: [#1] PREEMPT SMP

[PATCH 3.16 025/136] IB/srp: Avoid that a cable pull can trigger a kernel crash

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 8a0d18c62121d3c554a83eb96e2752861d84d937 upstream. This patch fixes the following kernel crash: general protection fault: [#1] PREEMPT SMP Workqueue: ib_mad2

[PATCH 3.16 030/136] f2fs: expose some sectors to user in inline data or dentry case

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 5b4267d195dd887c4412e34b5a7365baa741b679 upstream. If there's some data written through inline data or dentry, we need to shouw st_blocks. This fixes

[PATCH 3.16 030/136] f2fs: expose some sectors to user in inline data or dentry case

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 5b4267d195dd887c4412e34b5a7365baa741b679 upstream. If there's some data written through inline data or dentry, we need to shouw st_blocks. This fixes reporting zero blocks

[PATCH 3.16 024/136] IB/srpt: Do not accept invalid initiator port names

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit c70ca38960399a63d5c048b7b700612ea321d17e upstream. Make srpt_parse_i_port_id() return a negative value if hex2bin() fails. Fixes: commit

[PATCH 3.16 024/136] IB/srpt: Do not accept invalid initiator port names

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit c70ca38960399a63d5c048b7b700612ea321d17e upstream. Make srpt_parse_i_port_id() return a negative value if hex2bin() fails. Fixes: commit a42d985bd5b2 ("ib_srpt:

[PATCH 3.16 036/136] l2tp: initialise PPP sessions before registering them

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault commit f98be6c6359e7e4a61aaefb9964c1db31cb9ec0c upstream. pppol2tp_connect() initialises L2TP sessions after they've been exposed to the rest of the

[PATCH 3.16 036/136] l2tp: initialise PPP sessions before registering them

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault commit f98be6c6359e7e4a61aaefb9964c1db31cb9ec0c upstream. pppol2tp_connect() initialises L2TP sessions after they've been exposed to the rest of the system by

[PATCH 3.16 021/136] USB: serial: metro-usb: stop I/O after failed open

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 2339536d229df25c71c0900fc619289229bfecf6 upstream. Make sure to kill the interrupt-in URB after a failed open request. Apart from saving power (and

[PATCH 3.16 021/136] USB: serial: metro-usb: stop I/O after failed open

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 2339536d229df25c71c0900fc619289229bfecf6 upstream. Make sure to kill the interrupt-in URB after a failed open request. Apart from saving power (and avoiding stale input

[PATCH 3.16 059/136] powerpc/powernv/cpufreq: Fix the frequency read by /proc/cpuinfo

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Shriya commit cd77b5ce208c153260ed7882d8910f2395bfaabd upstream. The call to /proc/cpuinfo in turn calls cpufreq_quick_get() which returns the last frequency

[PATCH 3.16 027/136] fs/9p: Compare qid.path in v9fs_test_inode

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Tuomas Tynkkynen commit 8ee031631546cf2f7859cc69593bd60bbdd70b46 upstream. Commit fd2421f54423 ("fs/9p: When doing inode lookup compare qid details and inode mode bits.")

[PATCH 3.16 059/136] powerpc/powernv/cpufreq: Fix the frequency read by /proc/cpuinfo

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Shriya commit cd77b5ce208c153260ed7882d8910f2395bfaabd upstream. The call to /proc/cpuinfo in turn calls cpufreq_quick_get() which returns the last frequency requested by the kernel, but may

[PATCH 3.16 027/136] fs/9p: Compare qid.path in v9fs_test_inode

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Tuomas Tynkkynen commit 8ee031631546cf2f7859cc69593bd60bbdd70b46 upstream. Commit fd2421f54423 ("fs/9p: When doing inode lookup compare qid details and inode mode bits.") transformed

[PATCH 3.16 056/136] powerpc/pseries/vio: Dispose of virq mapping on vdevice unregister

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Tyrel Datwyler commit b8f89fea599d91e674497aad572613eb63181f31 upstream. When a vdevice is DLPAR removed from the system the vio subsystem doesn't bother unmapping

[PATCH 3.16 056/136] powerpc/pseries/vio: Dispose of virq mapping on vdevice unregister

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Tyrel Datwyler commit b8f89fea599d91e674497aad572613eb63181f31 upstream. When a vdevice is DLPAR removed from the system the vio subsystem doesn't bother unmapping the virq from the

[PATCH 3.16 038/136] bcache: only permit to recovery read error when cache device is clean

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Coly Li commit d59b23795933678c9638fd20c942d2b4f3cd6185 upstream. When bcache does read I/Os, for example in writeback or writethrough mode, if a read request on cache device

[PATCH 3.16 038/136] bcache: only permit to recovery read error when cache device is clean

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Coly Li commit d59b23795933678c9638fd20c942d2b4f3cd6185 upstream. When bcache does read I/Os, for example in writeback or writethrough mode, if a read request on cache device is failed,

[PATCH 3.16 026/136] tpm-dev-common: Reject too short writes

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Alexander Steffen commit ee70bc1e7b63ac8023c9ff9475d8741e397316e7 upstream. tpm_transmit() does not offer an explicit interface to indicate the number of valid

[PATCH 3.16 026/136] tpm-dev-common: Reject too short writes

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Alexander Steffen commit ee70bc1e7b63ac8023c9ff9475d8741e397316e7 upstream. tpm_transmit() does not offer an explicit interface to indicate the number of valid bytes in the communication

[PATCH 3.16 022/136] bcache: check ca->alloc_thread initialized before wake up it

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Coly Li commit 91af8300d9c1d7c6b6a2fd754109e08d4798b8d8 upstream. In bcache code, sysfs entries are created before all resources get allocated, e.g. allocation thread of a

[PATCH 3.16 022/136] bcache: check ca->alloc_thread initialized before wake up it

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Coly Li commit 91af8300d9c1d7c6b6a2fd754109e08d4798b8d8 upstream. In bcache code, sysfs entries are created before all resources get allocated, e.g. allocation thread of a cache set. There

[PATCH 3.16 052/136] coda: fix 'kernel memory exposure attempt' in fsync

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Jan Harkes commit d337b66a4c52c7b04eec661d86c2ef6e168965a2 upstream. When an application called fsync on a file in Coda a small request with just the file identifier was

[PATCH 3.16 070/136] MIPS: Fix an n32 core file generation regset support regression

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: "Maciej W. Rozycki" commit 547da673173de51f73887377eb275304775064ad upstream. Fix a commit 7aeb753b5353 ("MIPS: Implement task_user_regset_view.") regression, then activated

[PATCH 3.16 052/136] coda: fix 'kernel memory exposure attempt' in fsync

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: Jan Harkes commit d337b66a4c52c7b04eec661d86c2ef6e168965a2 upstream. When an application called fsync on a file in Coda a small request with just the file identifier was allocated, but the

[PATCH 3.16 070/136] MIPS: Fix an n32 core file generation regset support regression

3.16.54-rc1 review patch. If anyone has any objections, please let me know. -- From: "Maciej W. Rozycki" commit 547da673173de51f73887377eb275304775064ad upstream. Fix a commit 7aeb753b5353 ("MIPS: Implement task_user_regset_view.") regression, then activated by commit

[PATCH 3.2 67/79] RDS: Heap OOB write in rds_message_alloc_sgs()

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Mohamed Ghannam commit c095508770aebf1b9218e77026e48345d719b17c upstream. When args->nr_local is 0, nr_pages gets also 0 due some size calculation via rds_rm_size(),

[PATCH 3.2 67/79] RDS: Heap OOB write in rds_message_alloc_sgs()

3.2.99-rc1 review patch. If anyone has any objections, please let me know. -- From: Mohamed Ghannam commit c095508770aebf1b9218e77026e48345d719b17c upstream. When args->nr_local is 0, nr_pages gets also 0 due some size calculation via rds_rm_size(), which is later used to

  1   2   3   4   5   6   7   8   9   >