[PATCH RT 17/20] f2fs: Mutex cant be used by down_write_nest_lock()

3.18.27-rt27-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Yang Shi fsf2_lock_all() calls down_write_nest_lock() to acquire a rw_sem and check a mutex, but down_write_nest_lock() is designed for two rw_sem accoring to the comment in include/

[PATCH RT 13/20] sched,rt: __always_inline preemptible_lazy()

3.18.27-rt27-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith homer: # nm kernel/sched/core.o|grep preemptible_lazy 00b5 t preemptible_lazy echo wakeup_rt > current_tracer ==> Welcome to infinity. Signed-off-by: Mik

[PATCH RT 16/20] trace: Use rcuidle version for preemptoff_hist trace point

3.18.27-rt27-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Yang Shi When running -rt kernel with both PREEMPT_OFF_HIST and LOCKDEP enabled, the below error is reported: [ INFO: suspicious RCU usage. ] 4.4.1-rt6 #1 Not tainted include/tra

[PATCH RT 02/20] ptrace: dont open IRQs in ptrace_freeze_traced() too early

3.18.27-rt27-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior In the non-RT case the spin_lock_irq() here disables interrupts as well as raw_spin_lock_irq(). So in the unlock case the interrupts are enabled too early.

[PATCH RT 08/20] arm64: replace read_lock to rcu lock in call_step_hook

3.18.27-rt27-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Yang Shi BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:917 in_atomic(): 1, irqs_disabled(): 128, pid: 383, name: sh Preemption disabled at:[] kgdb_c

[PATCH RT 12/20] tick/broadcast: Make broadcast hrtimer irqsafe

3.18.27-rt27-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner Otherwise we end up with the following: |= |[ INFO: inconsistent lock state ] |4.4.2-rt7+ #5 Not tainted |---

[PATCH RT 18/20] rcu/torture: Comment out rcu_bh ops on PREEMPT_RT_FULL

3.18.27-rt27-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Clark Williams RT has dropped support of rcu_bh, comment out in rcutorture. Signed-off-by: Clark Williams Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Thomas Gleixner

[PATCH RT 14/20] drm,radeon,i915: Use preempt_disable/enable_rt() where recommended

3.18.27-rt27-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith DRM folks identified the spots, so use them. Signed-off-by: Mike Galbraith Cc: Sebastian Andrzej Siewior Cc: linux-rt-users Signed-off-by: Thomas Gleixner Signed-

[PATCH RT 11/20] kernel/stop_machine: partly revert "stop_machine: Use raw spinlocks"

3.18.27-rt27-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior With completion using swait and so rawlocks we don't need this anymore. Further, bisect thinks this patch is responsible for: |BUG: unable to handle kernel

[PATCH RT 04/20] preempt-lazy: Add the lazy-preemption check to preempt_schedule()

3.18.27-rt27-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior Probably in the rebase onto v4.1 this check got moved into less commonly used preempt_schedule_notrace(). This patch ensures that both functions use it. Re

Re: [PATCH v5 0/7] remoteproc: Add driver for STMicroelectronics platforms

On Wed, 27 Jan 2016, Bjorn Andersson wrote: > On Tue, Jan 26, 2016 at 11:31 PM, Lee Jones wrote: > > > > Apologies for ping (I hate doing that), but I haven't heard anything > > from you. Do you want me to re-submit this set, or are you willing to > > take this and apply the relevant Acks? > > >

Re: [PATCH] clk: ti: Fix some errors found by static checkers

On 03/02/2016 01:55 AM, Tony Lindgren wrote: * Stephen Boyd [160301 10:55]: drivers/clk/ti/clk-814x.c:34:12: warning: symbol 'dm814x_adpll_early_init' was not declared. Should it be static? drivers/clk/ti/clk-814x.c:58:12: warning: symbol 'dm814x_adpll_enable_init_clocks' was not declared. Sh

[PATCH RT 09/20] kernel: migrate_disable() do fastpath in atomic & irqs-off

3.18.27-rt27-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior With interrupts off it makes no sense to do the long path since we can't leave the CPU anyway. Also we might end up in a recursion with lockdep. Signed-off

[PATCH RT 03/20] net: move xmit_recursion to per-task variable on -RT

3.18.27-rt27-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior A softirq on -RT can be preempted. That means one task is in __dev_queue_xmit(), gets preempted and another task may enter __dev_queue_xmit() aw well. netpe

Re: [PATCH 2/2] kasan: unpoison stack of idle task on cpu online

On Wed, Mar 02, 2016 at 06:27:49PM +0300, Andrey Ryabinin wrote: > On 03/02/2016 05:50 PM, Mark Rutland wrote: > > On Wed, Mar 02, 2016 at 04:51:59PM +0300, Andrey Ryabinin wrote: [...] > > Is all the above necessary? > > > > Surely we can just include in mm/kasan/kasan.c? > > It is necessary.

[PATCH RT 01/20] sched: reset tasks lockless wake-queues on fork()

3.18.27-rt27-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior In 7675104990ed ("sched: Implement lockless wake-queues") we gained lockless wake-queues. -RT managed to lockup itself with those. There could be multiple a

[PATCH RT 00/20] Linux 3.18.27-rt27-rc1

Dear RT Folks, This is the RT stable review cycle of patch 3.18.27-rt27-rc1. Please scream at me if I messed something up. Please test the patches too. The -rc release will be uploaded to kernel.org and will be deleted when the final release is out. This is just a review release (or release can

[RESEND 05/11] pwm: sti: Supply PWM Capture register addresses and bit locations

Signed-off-by: Lee Jones --- drivers/pwm/pwm-sti.c | 25 + 1 file changed, 25 insertions(+) diff --git a/drivers/pwm/pwm-sti.c b/drivers/pwm/pwm-sti.c index aa217e2..2336bac 100644 --- a/drivers/pwm/pwm-sti.c +++ b/drivers/pwm/pwm-sti.c @@ -22,26 +22,48 @@ #include #

[PATCH RT 08/17] kernel: migrate_disable() do fastpath in atomic & irqs-off

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior With interrupts off it makes no sense to do the long path since we can't leave the CPU anyway. Also we might end up in a recursion with lockdep. Signed-off

[PATCH RT 14/17] f2fs: Mutex cant be used by down_write_nest_lock()

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Yang Shi fsf2_lock_all() calls down_write_nest_lock() to acquire a rw_sem and check a mutex, but down_write_nest_lock() is designed for two rw_sem accoring to the comment in include/

[PATCH RT 01/17] ptrace: dont open IRQs in ptrace_freeze_traced() too early

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior In the non-RT case the spin_lock_irq() here disables interrupts as well as raw_spin_lock_irq(). So in the unlock case the interrupts are enabled too early.

[PATCH RT 10/17] kernel/stop_machine: partly revert "stop_machine: Use raw spinlocks"

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior With completion using swait and so rawlocks we don't need this anymore. Further, bisect thinks this patch is responsible for: |BUG: unable to handle kernel

Re: [RFC 4/4] perf kvm: Fix output fields instead of 'trace' for perf kvm report on powerpc

Thanks Arnaldo, Please find my comments. On Wednesday 02 March 2016 07:55 PM, Arnaldo Carvalho de Melo wrote: Em Wed, Feb 24, 2016 at 02:37:45PM +0530, Ravi Bangoria escreveu: use_browser = 0; + if (!field_order && + is_perf_data_reorded_on_ppc(session->evlist) &&

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

Hello, Jiri. On Fri, Feb 19, 2016 at 01:10:00PM +0100, Jiri Slaby wrote: > > 1. didn't help, the problem persists. So I haven't applied the patch from 2. > > FWIW I dumped more info about the wq: > wq->name='hci0' pwq=8800390d7600 wq->dfl_pwq=8800390d5200 > pwq->refcnt=2 pwq->nr_active=0

[PATCH RT 00/17] Linux 3.14.61-rt64-rc1

Dear RT Folks, This is the RT stable review cycle of patch 3.14.61-rt64-rc1. Please scream at me if I messed something up. Please test the patches too. The -rc release will be uploaded to kernel.org and will be deleted when the final release is out. This is just a review release (or release can

Re: [PATCH] ARM: at91: avoid defining CONFIG_* symbols in source code

Le 23/02/2016 15:39, Arnd Bergmann a écrit : > In an invalid randconfig build (fixed by another patch), > I ran across this warning: > > arch/arm/include/debug/at91.S:18:0: error: "CONFIG_DEBUG_UART_VIRT" redefined > [-Werror] > #define CONFIG_DEBUG_UART_VIRT AT91_IO_P2V(CONFIG_DEBUG_UART_PHYS)

[PATCH RT 02/13] preempt-lazy: Add the lazy-preemption check to preempt_schedule()

3.12.54-rt74-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior Probably in the rebase onto v4.1 this check got moved into less commonly used preempt_schedule_notrace(). This patch ensures that both functions use it. Re

Re: [PATCH 5/7] perf, tools, stat: Implement --metric-only mode

On Wed, Mar 02, 2016 at 04:38:26PM +0100, Andi Kleen wrote: > On Wed, Mar 02, 2016 at 12:28:42PM +0100, Jiri Olsa wrote: > > On Tue, Mar 01, 2016 at 01:32:39PM +0100, Jiri Olsa wrote: > > > On Mon, Feb 29, 2016 at 02:36:24PM -0800, Andi Kleen wrote: > > > > From: Andi Kleen > > > > > > > > Add a

[PATCH RT 08/13] kernel/stop_machine: partly revert "stop_machine: Use raw spinlocks"

3.12.54-rt74-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior With completion using swait and so rawlocks we don't need this anymore. Further, bisect thinks this patch is responsible for: |BUG: unable to handle kernel

[PATCH RT 01/10] softirq: split timer softirqs out of ksoftirqd

3.10.97-rt107-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior The softirqd runs in -RT with SCHED_FIFO (prio 1) and deals mostly with timer wakeup which can not happen in hardirq context. The prio has been risen from

[PATCH RT 05/10] kernel: softirq: unlock with irqs on

3.10.97-rt107-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior We unlock the lock while the interrupts are off. This isn't a problem now but will get because the migrate_disable() + enable are not symmetrical in regard

Re: [PATCH 2/3] x86/mce/AMD, EDAC: Simplify SMCA decoding

On 3/2/2016 4:53 AM, Borislav Petkov wrote: Merge all IP blocks into a single enum. This allows for easier block name use later. Drop superfluous "_BLOCK" from the enum names. Signed-off-by: Borislav Petkov Cc: Aravind Gopalakrishnan enum amd_ip_types { - SMCA_F17H_CORE_BLOCK = 0,

[PATCH RT 09/13] sched,rt: __always_inline preemptible_lazy()

3.12.54-rt74-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith homer: # nm kernel/sched/core.o|grep preemptible_lazy 00b5 t preemptible_lazy echo wakeup_rt > current_tracer ==> Welcome to infinity. Signed-off-by: Mik

[PATCH RT 04/10] kernel: migrate_disable() do fastpath in atomic & irqs-off

3.10.97-rt107-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior With interrupts off it makes no sense to do the long path since we can't leave the CPU anyway. Also we might end up in a recursion with lockdep. Signed-of

[PATCH RT 06/10] kernel/stop_machine: partly revert "stop_machine: Use raw spinlocks"

3.10.97-rt107-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior With completion using swait and so rawlocks we don't need this anymore. Further, bisect thinks this patch is responsible for: |BUG: unable to handle kerne

[PATCH RT 13/13] Linux 3.12.54-rt74-rc1

3.12.54-rt74-rc1 stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (Red Hat)" --- localversion-rt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/localversion-rt b/localversion-rt index e8ada8cdb471..8dd12f3c29cb

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On 3/2/16, Peter Zijlstra wrote: > On Wed, Mar 02, 2016 at 04:00:49PM +0100, Sedat Dilek wrote: >> > >> > Right, most odd. Sedat, could you provide objdump -D of the relevant >> > sections of vmlinux ? >> > >> >> Can you give some clear instructions - for what shall I look for in >> special? > > o

[PATCH RT 09/10] kernel: sched: Fix preempt_disable_ip recodring for preempt_disable()

3.10.97-rt107-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior preempt_disable() invokes preempt_count_add() which saves the caller in current->preempt_disable_ip. It uses CALLER_ADDR1 which does not look for its calle

[PATCH RT 07/10] trace: Use rcuidle version for preemptoff_hist trace point

3.10.97-rt107-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Yang Shi When running -rt kernel with both PREEMPT_OFF_HIST and LOCKDEP enabled, the below error is reported: [ INFO: suspicious RCU usage. ] 4.4.1-rt6 #1 Not tainted include/tr

[PATCH RT 08/10] rcu/torture: Comment out rcu_bh ops on PREEMPT_RT_FULL

3.10.97-rt107-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Clark Williams RT has dropped support of rcu_bh, comment out in rcutorture. Signed-off-by: Clark Williams Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Thomas Gleixner

[PATCH RT 02/10] net: provide a way to delegate processing a softirq to ksoftirqd

3.10.97-rt107-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior If the NET_RX uses up all of his budget it moves the following NAPI invocations into the `ksoftirqd`. On -RT it does not do so. Instead it rises the NET_RX

[PATCH RT 10/10] Linux 3.10.97-rt107-rc1

3.10.97-rt107-rc1 stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (Red Hat)" --- localversion-rt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/localversion-rt b/localversion-rt index 8111d0b4d38d..c01084d72cc

Re: [RFC PATCH v3 3/3] PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers

On Tue, Mar 01, 2016 at 07:22:47PM +, Lorenzo Pieralisi wrote: > Hi Bjorn, > > On Thu, Feb 25, 2016 at 01:59:12PM -0600, Bjorn Helgaas wrote: > > On Thu, Feb 25, 2016 at 12:07:50PM +, Lorenzo Pieralisi wrote: > > > On Thu, Feb 25, 2016 at 03:01:19AM +, Gabriele Paoloni wrote: > > [...

[PATCH RT 00/10] Linux 3.10.97-rt107-rc1

Dear RT Folks, This is the RT stable review cycle of patch 3.10.97-rt107-rc1. Please scream at me if I messed something up. Please test the patches too. The -rc release will be uploaded to kernel.org and will be deleted when the final release is out. This is just a review release (or release ca

[PATCH RT 04/13] net: provide a way to delegate processing a softirq to ksoftirqd

3.12.54-rt74-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior If the NET_RX uses up all of his budget it moves the following NAPI invocations into the `ksoftirqd`. On -RT it does not do so. Instead it rises the NET_RX

[PATCH RT 03/10] latencyhist: disable jump-labels

3.10.97-rt107-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior Atleast on X86 we die a recursive death |CPU: 3 PID: 585 Comm: bash Not tainted 4.4.1-rt4+ #198 |Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS

Re: [PATCH 3.10 00/80] 3.10.99-stable review

On Wed, Mar 02, 2016 at 06:32:15AM -0800, Guenter Roeck wrote: > On 03/01/2016 03:44 PM, Greg Kroah-Hartman wrote: > >This is the start of the stable review cycle for the 3.10.99 release. > >There are 80 patches in this series, all will be posted as a response > >to this one. If anyone has any iss

[PATCH RT 01/13] ptrace: dont open IRQs in ptrace_freeze_traced() too early

3.12.54-rt74-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior In the non-RT case the spin_lock_irq() here disables interrupts as well as raw_spin_lock_irq(). So in the unlock case the interrupts are enabled too early.

[PATCH RT 06/17] latencyhist: disable jump-labels

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior Atleast on X86 we die a recursive death |CPU: 3 PID: 585 Comm: bash Not tainted 4.4.1-rt4+ #198 |Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS D

[PATCH RT 04/17] softirq: split timer softirqs out of ksoftirqd

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior The softirqd runs in -RT with SCHED_FIFO (prio 1) and deals mostly with timer wakeup which can not happen in hardirq context. The prio has been risen from t

[PATCH RT 15/17] rcu/torture: Comment out rcu_bh ops on PREEMPT_RT_FULL

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Clark Williams RT has dropped support of rcu_bh, comment out in rcutorture. Signed-off-by: Clark Williams Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Thomas Gleixner

[PATCH RT 09/17] kernel: softirq: unlock with irqs on

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior We unlock the lock while the interrupts are off. This isn't a problem now but will get because the migrate_disable() + enable are not symmetrical in regard

[RESEND 02/11] pwm: sysfs: Add PWM Capture support

Allow a user to read PWM Capture results from /sysfs. First, the user must tell PWM Capture which channel they wish to read from: $ echo 2 > $PWMCHIP/capture To start a capture and read the result, simply read the file: $ cat $PWMCHIP/capture The output format is left to the device. Signed

[PATCH RT 05/17] net: provide a way to delegate processing a softirq to ksoftirqd

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior If the NET_RX uses up all of his budget it moves the following NAPI invocations into the `ksoftirqd`. On -RT it does not do so. Instead it rises the NET_RX

[PATCH RT 03/17] preempt-lazy: Add the lazy-preemption check to preempt_schedule()

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior Probably in the rebase onto v4.1 this check got moved into less commonly used preempt_schedule_notrace(). This patch ensures that both functions use it. Re

[PATCH RT 06/13] kernel: migrate_disable() do fastpath in atomic & irqs-off

3.12.54-rt74-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior With interrupts off it makes no sense to do the long path since we can't leave the CPU anyway. Also we might end up in a recursion with lockdep. Signed-off

[PATCH RT 03/13] softirq: split timer softirqs out of ksoftirqd

3.12.54-rt74-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior The softirqd runs in -RT with SCHED_FIFO (prio 1) and deals mostly with timer wakeup which can not happen in hardirq context. The prio has been risen from t

[PATCH RT 12/13] kernel: sched: Fix preempt_disable_ip recodring for preempt_disable()

3.12.54-rt74-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior preempt_disable() invokes preempt_count_add() which saves the caller in current->preempt_disable_ip. It uses CALLER_ADDR1 which does not look for its caller

[PATCH RT 05/13] latencyhist: disable jump-labels

3.12.54-rt74-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior Atleast on X86 we die a recursive death |CPU: 3 PID: 585 Comm: bash Not tainted 4.4.1-rt4+ #198 |Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS D

[PATCH RT 13/17] trace: Use rcuidle version for preemptoff_hist trace point

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Yang Shi When running -rt kernel with both PREEMPT_OFF_HIST and LOCKDEP enabled, the below error is reported: [ INFO: suspicious RCU usage. ] 4.4.1-rt6 #1 Not tainted include/tra

Re: [PATCH V2 2/5] EDAC, MCE, AMD: Enable error decoding of Scalable MCA errors

On 3/2/2016 4:50 AM, Borislav Petkov wrote: Ok, applied with a bunch of changes ontop. Thanks! The second patch is relying on the assumption that a hwid of 0 is invalid. Is that so? Yes, HWID of 0 is invalid. Thanks, -Aravind.

[PATCH RT 10/13] trace: Use rcuidle version for preemptoff_hist trace point

3.12.54-rt74-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Yang Shi When running -rt kernel with both PREEMPT_OFF_HIST and LOCKDEP enabled, the below error is reported: [ INFO: suspicious RCU usage. ] 4.4.1-rt6 #1 Not tainted include/tra

[PATCH RT 00/13] Linux 3.12.54-rt74-rc1

Dear RT Folks, This is the RT stable review cycle of patch 3.12.54-rt74-rc1. Please scream at me if I messed something up. Please test the patches too. The -rc release will be uploaded to kernel.org and will be deleted when the final release is out. This is just a review release (or release can

[PATCH RT 07/17] arm64: replace read_lock to rcu lock in call_step_hook

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Yang Shi BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:917 in_atomic(): 1, irqs_disabled(): 128, pid: 383, name: sh Preemption disabled at:[] kgdb_c

[PATCH RT 07/13] kernel: softirq: unlock with irqs on

3.12.54-rt74-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior We unlock the lock while the interrupts are off. This isn't a problem now but will get because the migrate_disable() + enable are not symmetrical in regard

Re: [PATCH 3/3] EDAC, mce_amd: Correct error paths

On 3/2/2016 4:54 AM, Borislav Petkov wrote: From: Borislav Petkov Date: Wed, 2 Mar 2016 11:46:58 +0100 Subject: [PATCH 3/3] EDAC, mce_amd: Correct error paths We need to unwind properly when we fail to find the proper decoding functions. Streamline error messages to resemble the rest of this fi

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

[ Resend with reply all, instead of just "reply" ] On Wed, 2 Mar 2016 16:53:36 +0100 Sedat Dilek wrote: > 8110f3f0 : > 8110f3f0: 55 push %rbp > 8110f3f1: 48 89 e5mov%rsp,%rbp > 8110f3f4: 41 57

Re: [PATCH 1/6] usb: host: unhide suspend/resume declarations

On Wed, 2 Mar 2016, Arnd Bergmann wrote: > There is no need to hide function declarations, and making > these visible to the SoC specific host drivers lets us > use __maybe_unused and IS_ENABLED() checks to control > their use, rather than having to use #ifdef to hide all > callers. > > Signed-of

[PATCH RT 11/13] rcu/torture: Comment out rcu_bh ops on PREEMPT_RT_FULL

3.12.54-rt74-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Clark Williams RT has dropped support of rcu_bh, comment out in rcutorture. Signed-off-by: Clark Williams Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Thomas Gleixner

[PATCH 1/3] printk: Make printk() completely async

Currently, printk() sometimes waits for message to be printed to console and sometimes it does not (when console_sem is held by some other process). In case printk() grabs console_sem and starts printing to console, it prints messages from kernel printk buffer until the buffer is empty. When serial

Re: Freezable workqueue blocks non-freezable workqueue during the system resume process

Hello, (cc'ing Jan) On Fri, Feb 26, 2016 at 02:19:20PM +0800, Peter Chen wrote: > On Thu, Feb 25, 2016 at 05:01:12PM -0500, Tejun Heo wrote: > > Hello, Peter. > > > > On Wed, Feb 24, 2016 at 03:24:30PM +0800, Peter Chen wrote: > > > > You might want to complain to the block-layer people about th

[PATCH 11/14] input: spear-keyboard: use __maybe_unused to hide pm functions

The spear keyboard driver uses #ifdef CONFIG_PM to hide its power management functions, but then uses references from SIMPLE_DEV_PM_OPS that are only present if both CONFIG_PM and CONFIG_PM_SLEEP are set, resulting in a warning about unused functions: drivers/input/keyboard/spear-keyboard.c:292:12

[PATCH 06/14] dma: sirf: use __maybe_unused to hide pm functions

The sirf dma driver uses #ifdef to check for CONFIG_PM_SLEEP for its suspend/resume code but then has no #ifdef for the respective runtime PM code, so we get a warning if CONFIG_PM is disabled altogether: drivers/dma/sirf-dma.c:1000:12: error: 'sirfsoc_dma_runtime_resume' defined but not used [-W

[PATCH 14/14] ASoC: rockchip: use __maybe_unused to hide st_irq_syscfg_resume

The rockchip spdif driver uses SIMPLE_DEV_PM_OPS to conditionally set its power management functions, but we get a warning about rk_spdif_runtime_resume being unused when CONFIG_PM is not set: sound/soc/rockchip/rockchip_spdif.c:67:12: error: 'rk_spdif_runtime_resume' defined but not used [-Werro

[PATCH 10/14] wireless: cw1200: use __maybe_unused to hide pm functions_

The cw1200 uses #ifdef to check for CONFIG_PM, but then uses SIMPLE_DEV_PM_OPS, which leaves the references out when CONFIG_PM_SLEEP is not defined, so we get a warning with PM=y && PM_SLEEP=n: drivers/net/wireless/st/cw1200/cw1200_spi.c:450:12: error: 'cw1200_spi_suspend' defined but not used [-

Re: [PATCH] ASoC: intel: remove unused variable

On Wednesday 02 March 2016 06:50 PM, Mark Brown wrote: On Wed, Mar 02, 2016 at 12:27:09PM +, One Thousand Gnomes wrote: Sudip Mukherjee wrote: My From: is Sudip Mukherjee and my Signed-off-by: is Sudip Mukherjee My From name and Signed-off name matches. But my emails donot match.

[PATCH 08/14] scsi: mvumi: use __maybe_unused to hide pm functions

The mvumi scsi hides the references to its suspend/resume functions in an #ifdef but does not hide the implementation the same way: drivers/scsi/mvumi.c:2632:12: error: 'mvumi_suspend' defined but not used [-Werror=unused-function] drivers/scsi/mvumi.c:2651:12: error: 'mvumi_resume' defined but n

[PATCH 09/14] amd-xgbe: use __maybe_unused to hide pm functions

The amd-xgbe ethernet driver hides its suspend/resume functions in #ifdef CONFIG_PM, but uses SIMPLE_DEV_PM_OPS() to make the reference conditional on CONFIG_PM_SLEEP, which results in a warning when PM_SLEEP is not set but PM is: drivers/net/ethernet/amd/xgbe/xgbe-main.c:833:12: warning: 'xgbe_su

Re: [PATCH v2 13/13] ARM: sunxi: Introduce MACH_SUN8I_A83T option

Hello Maxime, On Tue, Mar 1, 2016 at 3:12 PM, Maxime Ripard wrote: > Hi, > > On Sun, Feb 28, 2016 at 11:18:58PM +0800, Vishnu Patekar wrote: >> A83T has CPUS clock similar to A80's. currently, a80 cpus clock only >> compiled for A80. So, Introduce MACH_SUN8I_A83T to compile it for >> A83T as well

[PATCH RT 16/17] kernel: sched: Fix preempt_disable_ip recodring for preempt_disable()

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior preempt_disable() invokes preempt_count_add() which saves the caller in current->preempt_disable_ip. It uses CALLER_ADDR1 which does not look for its caller

Re: [PATCH 1/3] Device tree binding documentation for gpio-switch

Reviving this thread... On Tue, Dec 15, 2015 at 3:09 AM, Markus Pargmann wrote: > Hi, > > On Monday 14 December 2015 09:45:48 Rob Herring wrote: >> On Mon, Dec 14, 2015 at 8:28 AM, Linus Walleij >> wrote: >> > On Fri, Dec 11, 2015 at 3:06 PM, Rob Herring wrote: >> >> On Fri, Dec 11, 2015 at 6:

[PATCH 07/14] hw_random: exynos: use __maybe_unused to hide pm functions

The exynos random driver uses #ifdef to check for CONFIG_PM, but then uses SIMPLE_DEV_PM_OPS, which leaves the references out when CONFIG_PM_SLEEP is not defined, so we get a warning with PM=y && PM_SLEEP=n: drivers/char/hw_random/exynos-rng.c:166:12: error: 'exynos_rng_suspend' defined but not u

[PATCH RT 11/17] sched,rt: __always_inline preemptible_lazy()

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith homer: # nm kernel/sched/core.o|grep preemptible_lazy 00b5 t preemptible_lazy echo wakeup_rt > current_tracer ==> Welcome to infinity. Signed-off-by: Mik

[PATCH RT 12/17] drm,radeon,i915: Use preempt_disable/enable_rt() where recommended

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith DRM folks identified the spots, so use them. Signed-off-by: Mike Galbraith Cc: Sebastian Andrzej Siewior Cc: linux-rt-users Signed-off-by: Thomas Gleixner Signed-

[PATCH RT 17/17] Linux 3.14.61-rt64-rc1

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (Red Hat)" --- localversion-rt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/localversion-rt b/localversion-rt index b0e8dd7bd707..c64934cc5dfa

[PATCH 00/14] drivers: use __maybe_unused to hide pm functions

I found many variations of the bug in these device drivers (and some USB drivers I already send patches for in a separate series). In each case, the power management operations structure conditionally references suspend/resume functions, but the functions are hidden in an incorrect #ifdef or not h

Re: [PATCH 01/14] pinctrl: at91: use __maybe_unused to hide pm functions

Le 02/03/2016 16:58, Arnd Bergmann a écrit : > The at91-pio4 pinctrl driver uses SET_SYSTEM_SLEEP_PM_OPS() to > conditionally set the correct suspend/resume options, but they > become unused when CONFIG_PM is disabled: > > drivers/pinctrl/pinctrl-at91-pio4.c:827:12: error: 'atmel_pctrl_suspend' >

[PATCH 2/3] printk: Skip messages on oops

When there are too many messages in the kernel printk buffer it can take very long to print them to console (especially when using slow serial console). This is undesirable during oops so when we encounter oops and there are more than 100 messages to print, print just the newest 100 messages and th

[PATCH 04/14] power: pm2301-charger: use __maybe_unused to hide pm functions

The pm2301 charger driver uses nested #ifdefs to check for both CONFIG_PM and CONFIG_PM_SLEEP in an attempt to hide its suspend and runtime-pm operations when they are unused, but it does not hide the clear_lpn_pin() function in the same way, so we get a build warning when everything is disabled:

[PATCH 05/14] mfd: ipaq-micro: use __maybe_unused to hide pm functions

The ipaq-micro driver uses SET_SYSTEM_SLEEP_PM_OPS() to remove the reference to its resume function, but does not use an #ifdef around the definition, so we get a build warning: drivers/mfd/ipaq-micro.c:379:12: error: 'micro_resume' defined but not used [-Werror=unused-function] This adds a __ma

[PATCH 3/3] printk: debug: Slow down printing to 9600 bauds

Signed-off-by: Jan Kara --- kernel/printk/printk.c | 35 ++- 1 file changed, 34 insertions(+), 1 deletion(-) diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c index 03f5278b47b4..8ac60219059a 100644 --- a/kernel/printk/printk.c +++ b/kernel/printk/print

[GIT PULL] at91: dt for 4.6 #2

Arnd, Olof, Kevin, A second batch of DT updates for 4.6. This time it is based on 4.5-rc3 as one of the patches fixes an node that was changed during 4.5-rc phase. As I saw that your "next/dt" branches are based on 4.5-rc3, I thought it wouldn't be a problem. Overall a pretty simple series with ma

Re: [PATCH v5 0/5] drm/dsi: DSI for devices with different control bus

On Fri, Feb 12, 2016 at 02:48:29PM +0530, Archit Taneja wrote: > We are currently restricted when it comes to supporting DSI on devices > that have a non-DSI control bus. For example, DSI encoder chips are > available in the market that are configured via i2c. Configuring their > registers via DSI

[PATCH 01/14] pinctrl: at91: use __maybe_unused to hide pm functions

The at91-pio4 pinctrl driver uses SET_SYSTEM_SLEEP_PM_OPS() to conditionally set the correct suspend/resume options, but they become unused when CONFIG_PM is disabled: drivers/pinctrl/pinctrl-at91-pio4.c:827:12: error: 'atmel_pctrl_suspend' defined but not used [-Werror=unused-function] drivers/p

[PATCH 13/14] [media] omap3isp: use IS_ENABLED() to hide pm functions

The omap3isp driver hides is power management functions using #ifdef but it fails to hide the isp_suspend_modules/isp_resume_modules functions in the same way, which leads to a build warning when CONFIG_PM is disabled: drivers/media/platform/omap3isp/isp.c:1183:12: error: 'isp_suspend_modules' de

Re: [PATCH] drm/panel: simple: fix g121x1_l03 hsync/vsync polarity

On Tue, Mar 01, 2016 at 06:06:54PM -0500, Akshay Bhat wrote: > Set hsync/vsync to active low for g121x1_l03 panel to match the > recommended setting in datasheet. > > Signed-off-by: Akshay Bhat > --- > drivers/gpu/drm/panel/panel-simple.c | 1 + > 1 file changed, 1 insertion(+) Applied, thanks.

[PATCH RT 02/17] net: move xmit_recursion to per-task variable on -RT

3.14.61-rt64-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior A softirq on -RT can be preempted. That means one task is in __dev_queue_xmit(), gets preempted and another task may enter __dev_queue_xmit() aw well. netpe

[PATCH 12/14] keyboard: snvs-pwrkey: use __maybe_unused to hide pm functions

The SNVS power key driver has suspend/resume functions that are accessed using SIMPLE_DEV_PM_OPS, which hide the reference when CONFIG_PM_SLEEP is not set, resulting in a warning about unused functions: drivers/input/keyboard/snvs_pwrkey.c:183:12: error: 'imx_snvs_pwrkey_suspend' defined but not

[PATCH 03/14] power: ipaq-micro-battery: use __maybe_unused to hide pm functions

The ipaq micro battery driver has suspend/resume functions that are accessed using SIMPLE_DEV_PM_OPS, which hide the reference when CONFIG_PM_SLEEP is not set, resulting in a warning about unused functions: drivers/power/ipaq_micro_battery.c:284:12: error: 'micro_batt_suspend' defined but not use

[PATCH 02/14] irqchip: st: use __maybe_unused to hide st_irq_syscfg_resume

the st irqchip driver uses SIMPLE_DEV_PM_OPS to conditionally set its power management functions, but we get a warning about st_irq_syscfg_resume being unused when CONFIG_PM is not set: drivers/irqchip/irq-st.c:183:12: error: 'st_irq_syscfg_resume' defined but not used [-Werror=unused-function]

<    2   3   4   5   6   7   8   9   10   11   >