Re: [PATCH 2/4] x86/fpu: introduce restore_init_xstate()

On Fri, Mar 13, 2015 at 03:39:28PM +0100, Oleg Nesterov wrote: > This too needs cleanups. But later ;) > > Note that xstate_enable_boot_cpu is not called if !cpu_has_xsave, see the > check in xsave_init(). Howver, eagerfpu=on will force eager_fpu_init() which > calls eager_fpu_init_bp(). Yahaa.

[PATCH RT 14/27] futex: Split out the waiter check from lookup_pi_state()

3.4.106-rt132-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: e60cbc5ceaa518d630ab8f35a7d05cee1c752648 We want to be a bit more clever in futex_lock_pi_atomic() and separate the possible states. Split out the

[PATCH RT 00/27] Linux 3.4.106-rt132-rc1

Dear RT Folks, This is the RT stable review cycle of patch 3.4.106-rt132-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

Re: [PATCH v2 2/2] of: Drop superfluous dependance for OF_OVERLAY

On Mon, Feb 16, 2015 at 12:27 AM, Matwey V. Kornilov wrote: > The whole menu already depends on OF, so there is no need to additionaly > specify it. > > Suggested-by: Paul Bolle > Signed-off-by: Matwey V. Kornilov Applied for 4.0. Thanks. Rob > --- > drivers/of/Kconfig | 1 - > 1 file chang

[PATCH RT 25/31] sunrpc: make svc_xprt_do_enqueue() use get_cpu_light()

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:915 |in_atomic(): 1, irqs_disabled(): 0, pid: 3194, name: rpc.nfsd |Preemption disable

[PATCH RT 27/31] timers: Track total number of timers in list

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: "Paul E. McKenney" upstream commit: fff421580f512fc044cc7421fdff31a7a6997350 Currently, the tvec_base structure's ->active_timers field tracks only the non-deferrable timers, which

Re: [PATCH v4 0/9] ARM: at91 cleanups for 4.1 #1

Le 12/03/2015 15:54, Alexandre Belloni a écrit : > This series removes more mach/headers. > > Then it introduces a more scalable SoC detection infrastructure which allows > to > remove the at91_map_io/at91_alt_map_io and iotable_init ugliness. > > Changes in v4: > - Changes soc family and name

[PATCH RT 24/31] work-simple: Simple work queue implemenation

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Daniel Wagner Provides a framework for enqueuing callbacks from irq context PREEMPT_RT_FULL safe. The callbacks are executed in kthread context. Bases on wait-simple. Signed-off-by

Re: Linux XIA - merge proposal

On 03/10/2015 01:01 PM, Bjorn Helgaas wrote: From my point of view (far outside the networking world and completely incompetent to judge the merits of XIA), this email seems like a reasonable starting point for a discussion, and I'm disappointed that it got shut down so fast. It might not be in

[PATCH RT 21/31] ARM: cmpxchg: define __HAVE_ARCH_CMPXCHG for armv6 and later

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- Both pi_stress and sigwaittest in rt-test show performance gain with __HAVE_ARCH_CMPXCHG. Testing result on coretile_express_a9x4: pi_stress -p 99 --duration=300 (on linux-3.4-rc5; bigger i

[PATCH RT 10/31] rtmutex: Cleanup deadlock detector debug logic

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 8930ed80f970a90a795239e7415c9b0e6f964649 The conditions under which deadlock detection is conducted are unclear and undocumented. Add constants ins

[PATCH RT 16/31] futex: Simplify futex_lock_pi_atomic() and make it more robust

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: af54d6a1c3ad474bbc9893c9905022646be6092c futex_lock_pi_atomic() is a maze of retry hoops and loops. Reduce it to simple and understandable states:

Re: [PATCH] of/unittest: Fix the wrong expected value in of_selftest_property_string

On Mon, Mar 2, 2015 at 9:50 PM, Wang Long wrote: > This patch fix the wrong expected value of of_property_match_string > in of_selftest_property_string. > > Signed-off-by: Wang Long Applied for 4.0. Thanks. Rob > --- > drivers/of/unittest.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 delet

[PATCH RT 20/31] arm/futex: disable preemption during futex_atomic_cmpxchg_inatomic()

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior The ARM UP implementation of futex_atomic_cmpxchg_inatomic() assumes that pagefault_disable() inherits a preempt disabled section. This assumtion is true fo

Re: [PATCH] of/selftest: remove the duplicate of_changeset_init

On Mon, Mar 2, 2015 at 12:49 AM, Wang Long wrote: > Remove the duplicate of_changeset_init. In of_selftest_changeset > testcase, the "struct of_changeset chgset" is initialized twice, > but only once is enough. so, drop the first initializtion code. > > Signed-off-by: Wang Long Applied for 4.0.

[PATCH RT 11/31] rtmutex: Avoid pointless requeueing in the deadlock detection chain walk

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 67792e2cabadbadd1a93f6790fa7bcbd47eca7c3 In case the dead lock detector is enabled we follow the lock chain to the end in rt_mutex_adjust_prio_chain

[PATCH RT 17/31] rt-mutex: avoid a NULL pointer dereference on deadlock

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior With task_blocks_on_rt_mutex() returning early -EDEADLK we never add the waiter to the waitqueue. Later, we try to remove it via remove_waiter() and go boom

[PATCH RT 13/31] futex: Use futex_top_waiter() in lookup_pi_state()

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: bd1dbcc67cd2c1181e2c01daac51eabf1b964dd8 No point in open coding the same function again. Signed-off-by: Thomas Gleixner Reviewed-by: Darren Hart

[PATCH RT 01/31] gpio: omap: use raw locks for locking

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior This patch converts gpio_bank.lock from a spin_lock into a raw_spin_lock. The call path is to access this lock is always under a raw_spin_lock, for instance

[PATCH RT 07/31] rtmutex: Document pi chain walk

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 3eb65aeadf701976b084e9171e16bb7d1e83fbb0 Add commentry to document the chain walk and the protection mechanisms and their scope. Signed-off-by: Tho

[PATCH RT 05/31] rtmutex: No need to keep task ref for lock owner check

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 2ffa5a5cd2fe792b6399c903d5172adf088d8ff7 There is no point to keep the task ref across the check for lock owner. Drop the ref before that, so the pr

[PATCH RT 15/31] futex: Split out the first waiter attachment from lookup_pi_state()

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 04e1b2e52b17195c9a1daa5935c55a4c8716095c We want to be a bit more clever in futex_lock_pi_atomic() and separate the possible states. Split out the c

Re: [PATCH V2 linux-next] UBIFS: simplify returns

On Thu, Mar 12, 2015 at 9:34 PM, Fabian Frederick wrote: > directly return recover_head() and ubifs_leb_unmap() > instead of storing value in err and testing it. > > Signed-off-by: Fabian Frederick Acked-by: Geert Uytterhoeven Gr{oetje,eeting}s, Geert -- Geert Uytterh

[PATCH RT 25/27] sunrpc: make svc_xprt_do_enqueue() use get_cpu_light()

3.4.106-rt132-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:915 |in_atomic(): 1, irqs_disabled(): 0, pid: 3194, name: rpc.nfsd |Preemption disabl

[PATCH RT 06/31] rtmutex: Clarify the boost/deboost part

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: a57594a13a446d1a6ab1dcd48339f799ce586843 Add a separate local variable for the boost/deboost logic to make the code more readable. Add comments wher

[PATCH RT 02/31] create-rt-enqueue

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt To ease backporting patches, replace the plist functions with rt_mutex_enqueue{_pi}() and rt_mutex_dequeue{_pi}() like upstream -rt does. This will lower the conflicts

[PATCH RT 15/25] futex: Split out the first waiter attachment from lookup_pi_state()

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 04e1b2e52b17195c9a1daa5935c55a4c8716095c We want to be a bit more clever in futex_lock_pi_atomic() and separate the possible states. Split out the co

[PATCH RT 23/25] sunrpc: make svc_xprt_do_enqueue() use get_cpu_light()

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith |BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:915 |in_atomic(): 1, irqs_disabled(): 0, pid: 3194, name: rpc.nfsd |Preemption disabled

[PATCH RT 12/31] futex: Make unlock_pi more robust

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: ccf9e6a80d9e1b9df69c98e6b9745cf49869ee15 The kernel tries to atomically unlock the futex without checking whether there is kernel state associated t

[PATCH RT 18/31] x86: UV: raw_spinlock conversion

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith Shrug. Lots of hobbyists have a beast in their basement, right? Cc: stable...@vger.kernel.org Signed-off-by: Mike Galbraith Signed-off-by: Sebastian Andrzej Siewior

[PATCH RT 21/27] ARM: cmpxchg: define __HAVE_ARCH_CMPXCHG for armv6 and later

3.4.106-rt132-rc1 stable review patch. If anyone has any objections, please let me know. -- Both pi_stress and sigwaittest in rt-test show performance gain with __HAVE_ARCH_CMPXCHG. Testing result on coretile_express_a9x4: pi_stress -p 99 --duration=300 (on linux-3.4-rc5; bigger

[PATCH RT 26/27] lockdep: selftest: fix warnings due to missing PREEMPT_RT conditionals

3.4.106-rt132-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Josh Cartwright "lockdep: Selftest: Only do hardirq context test for raw spinlock" disabled the execution of certain tests with PREEMPT_RT_FULL, but did not prevent the tests from s

Re: [PATCH 1/2] ARM: dts: am4372: Add "ti,am437x-ocp2scp" as compatible string for OCP2SCP

Hi, On Friday 13 March 2015 08:45 PM, Nishanth Menon wrote: On 03/13/2015 10:12 AM, Kishon Vijay Abraham I wrote: Added a new compatible string "ti,am437x-ocp2scp" for OCP2SCP module. This is needed since except for the OCP2SCP used in AM437x, SYNC2 value in OCP2SCP TIMING should be changed whe

Re: [RFC] With 8250 Designware UART, if writes to the LCR failed the kernel will hung up

On Tue, Mar 10, 2015 at 4:47 AM, Tim Kryger wrote: > On Mon, Mar 9, 2015 at 8:05 AM, Alan Cox wrote: > >> Ah no - I meant what is their official software workaround for existing >> parts with the bug ? Presumably they have an errata document that >> discusses this and the correct methods they rec

Re: [PATCH] PNP / ACPI: Use ACPI_COMPANION_SET() during initialization

On Fri, Mar 13, 2015 at 01:45:49AM +0100, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > pnpacpi_add_device() calls acpi_bind_one() on an already registered > device, which is a mistake, but it can initialize the ACPI companion > field of the struct device to be registered using ACPI_COMP

[PATCH RT 25/25] Linux 3.2.68-rt99-rc1

3.2.68-rt99-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 8de253240c16..29791c9d77a3

[PATCH RT 01/25] gpio: omap: use raw locks for locking

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior This patch converts gpio_bank.lock from a spin_lock into a raw_spin_lock. The call path is to access this lock is always under a raw_spin_lock, for instance

[PATCH RT 18/27] x86: UV: raw_spinlock conversion

3.4.106-rt132-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith Shrug. Lots of hobbyists have a beast in their basement, right? Cc: stable...@vger.kernel.org Signed-off-by: Mike Galbraith Signed-off-by: Sebastian Andrzej Siewio

[PATCH RT 04/25] rtmutex: Simplify and document try_to_take_rtmutex()

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 358c331f391f3e0432f4f96f25017d12ac8d10b1 The current implementation of try_to_take_rtmutex() is correct, but requires more than a single brain twist

Re: [PATCH v3 0/2] x86_64: Sigcontext improvements

On 03/12, Andy Lutomirski wrote: > > Patch 1 is IMO a bug fix. And personally I agree. I am still not sure about renames in include/uapi, perhaps someone can ack comment this change... Perhaps we could could even do - __u16 __pad0; + // comment to explain that ->ss i

[PATCH RT 08/31] rtmutex: Simplify remove_waiter()

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 1ca7b86062ec8473d03c5cdfd336abc8b1c8098c Exit right away, when the removed waiter was not the top priority waiter on the lock. Get rid of the extra

[PATCH RT 16/25] futex: Simplify futex_lock_pi_atomic() and make it more robust

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: af54d6a1c3ad474bbc9893c9905022646be6092c futex_lock_pi_atomic() is a maze of retry hoops and loops. Reduce it to simple and understandable states:

[PATCH RT 27/27] Linux 3.4.106-rt132-rc1

3.4.106-rt132-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 a328b97369c2..50cab880b71

[PATCH RT 24/25] lockdep: selftest: fix warnings due to missing PREEMPT_RT conditionals

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Josh Cartwright "lockdep: Selftest: Only do hardirq context test for raw spinlock" disabled the execution of certain tests with PREEMPT_RT_FULL, but did not prevent the tests from sti

[PATCH RT 00/25] Linux 3.2.68-rt99-rc1

Dear RT Folks, This is the RT stable review cycle of patch 3.2.68-rt99-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 cand

[PATCH RT 09/25] rtmutex: Confine deadlock logic to futex

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: c051b21f71d1ffdfd7ad406a1ef5ede5e5f974c5 The deadlock logic is only required for futexes. Remove the extra arguments for the public functions and al

[PATCH RT 09/31] rtmutex: Confine deadlock logic to futex

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: c051b21f71d1ffdfd7ad406a1ef5ede5e5f974c5 The deadlock logic is only required for futexes. Remove the extra arguments for the public functions and a

[PATCH RT 11/25] rtmutex: Avoid pointless requeueing in the deadlock detection chain walk

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 67792e2cabadbadd1a93f6790fa7bcbd47eca7c3 In case the dead lock detector is enabled we follow the lock chain to the end in rt_mutex_adjust_prio_chain,

[PATCH RT 03/25] rtmutex: Simplify rtmutex_slowtrylock()

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream-commit: 88f2b4c15e561bb5c28709d666364f273bf54b98 Oleg noticed that rtmutex_slowtrylock() has a pointless check for rt_mutex_owner(lock) != current. To avoid

[PATCH RT 16/27] futex: Simplify futex_lock_pi_atomic() and make it more robust

3.4.106-rt132-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: af54d6a1c3ad474bbc9893c9905022646be6092c futex_lock_pi_atomic() is a maze of retry hoops and loops. Reduce it to simple and understandable states:

[PATCH RT 17/25] rt-mutex: avoid a NULL pointer dereference on deadlock

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior With task_blocks_on_rt_mutex() returning early -EDEADLK we never add the waiter to the waitqueue. Later, we try to remove it via remove_waiter() and go boom

[PATCH RT 21/25] scheduling while atomic in cgroup code

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith mm, memcg: make refill_stock() use get_cpu_light() Nikita reported the following memcg scheduling while atomic bug: Call Trace: [e22d5a90] [c0007ea8] show_stack+0x4c/

[PATCH RT 07/25] rtmutex: Document pi chain walk

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 3eb65aeadf701976b084e9171e16bb7d1e83fbb0 Add commentry to document the chain walk and the protection mechanisms and their scope. Signed-off-by: Thom

[PATCH RT 23/27] scheduling while atomic in cgroup code

3.4.106-rt132-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith mm, memcg: make refill_stock() use get_cpu_light() Nikita reported the following memcg scheduling while atomic bug: Call Trace: [e22d5a90] [c0007ea8] show_stack+0x4

[PATCH RT 04/31] rtmutex: Simplify and document try_to_take_rtmutex()

3.10.70-rt75-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 358c331f391f3e0432f4f96f25017d12ac8d10b1 The current implementation of try_to_take_rtmutex() is correct, but requires more than a single brain twist

[PATCH RT 14/25] futex: Split out the waiter check from lookup_pi_state()

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: e60cbc5ceaa518d630ab8f35a7d05cee1c752648 We want to be a bit more clever in futex_lock_pi_atomic() and separate the possible states. Split out the wa

[PATCH] HID: uclogic: make input_mapping independent of usb

No need to retrieve the USB handle in input_mapping() when we already do that in probe. It also allows to use the quirk without having to add the product ID matching. Signed-off-by: Benjamin Tissoires --- Nick, no need to cc DIGImend-devel when replying on this one, I'll send the same to DIGIme

[PATCH RT 20/25] arm/futex: disable preemption during futex_atomic_cmpxchg_inatomic()

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior The ARM UP implementation of futex_atomic_cmpxchg_inatomic() assumes that pagefault_disable() inherits a preempt disabled section. This assumtion is true for

[PATCH RT 22/27] sas-ata/isci: dontt disable interrupts in qc_issue handler

3.4.106-rt132-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Paul Gortmaker On 3.14-rt we see the following trace on Canoe Pass for SCSI_ISCI "Intel(R) C600 Series Chipset SAS Controller" when the sas qc_issue handler is run: BUG: sleeping

[PATCH RT 24/27] work-simple: Simple work queue implemenation

3.4.106-rt132-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Daniel Wagner Provides a framework for enqueuing callbacks from irq context PREEMPT_RT_FULL safe. The callbacks are executed in kthread context. Bases on wait-simple. Signed-off-b

[PATCH RT 02/25] create-rt-enqueue

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt To ease backporting patches, replace the plist functions with rt_mutex_enqueue{_pi}() and rt_mutex_dequeue{_pi}() like upstream -rt does. This will lower the conflicts

[PATCH RT 10/25] rtmutex: Cleanup deadlock detector debug logic

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 8930ed80f970a90a795239e7415c9b0e6f964649 The conditions under which deadlock detection is conducted are unclear and undocumented. Add constants inst

[PATCH RT 13/25] futex: Use futex_top_waiter() in lookup_pi_state()

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: bd1dbcc67cd2c1181e2c01daac51eabf1b964dd8 No point in open coding the same function again. Signed-off-by: Thomas Gleixner Reviewed-by: Darren Hart

[PATCH RT 12/25] futex: Make unlock_pi more robust

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: ccf9e6a80d9e1b9df69c98e6b9745cf49869ee15 The kernel tries to atomically unlock the futex without checking whether there is kernel state associated to

[PATCH RT 08/25] rtmutex: Simplify remove_waiter()

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 1ca7b86062ec8473d03c5cdfd336abc8b1c8098c Exit right away, when the removed waiter was not the top priority waiter on the lock. Get rid of the extra i

Re: [PATCH v3 3/5] i2c: recovery: change input parameter to i2c_adapter for prepare/unprepare_recovery

Hi, On Fri, Mar 13, 2015 at 12:15:54PM +0200, grygorii.stras...@linaro.org wrote: > Hi Wolfram, > > On 03/12/2015 01:32 PM, Alexander Sverdlin wrote: > > On 01/12/14 16:34, Grygorii Strashko wrote: > >> This patch changes type of input parameter for > >> .prepare/unprepare_recovery() > >> callba

[PATCH] mm/slub: fix lockups on PREEMPT && !SMP kernels

Commit 9aabf810a67cd97e ("mm/slub: optimize alloc/free fastpath by removing preemption on/off") introduced an occasional hang for kernels built with CONFIG_PREEMPT && !CONFIG_SMP. The problem is the following loop the patch introduced to slab_alloc_node and slab_free: do { tid = this_cpu_

[PATCH RT 06/25] rtmutex: Clarify the boost/deboost part

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: a57594a13a446d1a6ab1dcd48339f799ce586843 Add a separate local variable for the boost/deboost logic to make the code more readable. Add comments where

Re: [PATCH 3/4] x86/fpu: use restore_init_xstate() instead of math_state_restore() on kthread exec

On Fri, Mar 13, 2015 at 03:45:14PM +0100, Oleg Nesterov wrote: > Because in math_state_restore() case kernel_fpu_begin()->__save_init_fpu() > will overwrite (corrupt) the same fpu->state buffer we need to restore. > Without kernel_fpu_disable(). Yes. > restore_init_xstate() obviously differs beca

[PATCH RT 05/25] rtmutex: No need to keep task ref for lock owner check

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner upstream commit: 2ffa5a5cd2fe792b6399c903d5172adf088d8ff7 There is no point to keep the task ref across the check for lock owner. Drop the ref before that, so the pro

Re: [PATCH v4 2/4] arm64: dts: Add Qualcomm MSM8916 SoC and evaluation board dts

On Mar 13, 2015, at 5:52 AM, Mark Rutland wrote: >> +/ { >> +chosen { >> +stdout-path = &blsp1_uart2; >> +}; > > It would be good if we had the configuration too (see > Documentation/devicetree/bindings/chosen.txt), as that avoids any > reliance on kernel defaults. > > You

Re: [PATCH 14/16] staging: rtl8723au: Improve readability of two very long lines

On 03/12/2015 10:15 PM, M. Vefa Bicakci wrote: Improve the readability of an if statement and its very long trace output line in rtl8723au's rtw_security.c. Signed-off-by: M. Vefa Bicakci --- drivers/staging/rtl8723au/core/rtw_security.c | 18 +++--- 1 file changed, 15 insertions

[PATCH RT 18/25] x86: UV: raw_spinlock conversion

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith Shrug. Lots of hobbyists have a beast in their basement, right? Cc: stable...@vger.kernel.org Signed-off-by: Mike Galbraith Signed-off-by: Sebastian Andrzej Siewior

[PATCH RT 22/25] work-simple: Simple work queue implemenation

3.2.68-rt99-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Daniel Wagner Provides a framework for enqueuing callbacks from irq context PREEMPT_RT_FULL safe. The callbacks are executed in kthread context. Bases on wait-simple. Signed-off-by:

[PATCH] selftests/kcmp: exit with non-zero code in a fail case (v2)

Currently this test always returs zero code and a child process returns non-zero code only if the last testcase failed. v2: don't forget to return smth from ksft_exit() Cc: Michael Ellerman Cc: Shuah Khan Cc: Cyrill Gorcunov Signed-off-by: Andrey Vagin --- tools/testing/selftests/kcmp/kcmp_t

Re: [RFC][PATCH 1/2] fs proc: make pagemap a privileged interface

On 03/12/2015 03:35 PM, Andrew Morton wrote: > On Mon, 09 Mar 2015 13:43:21 -0700 Dave Hansen wrote: >> From: Dave Hansen >> >> Physical addresses are sensitive information. There are >> existing, known exploits that are made easier if physical >> information is available. Here is one example:

[PATCH] selftests/exec: take into account that zero is a success code

Cc: Shuah Khan Signed-off-by: Andrey Vagin --- tools/testing/selftests/exec/execveat.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftests/exec/execveat.c b/tools/testing/selftests/exec/execveat.c index e238c95..6747a3f 100644 --- a/tools/testing/selftest

Re: [PATCH 01/15] perf build: Disable default check for libbabeltrace

Em Wed, Mar 11, 2015 at 09:58:50AM +0100, Jiri Olsa escreveu: > Remove libbabeltrace check from default features set, because the > requested version is not released yet in most distributions. We'll > enable later. > > Calling libbabeltrace check manually via feature_check > before $(feature-libba

Re: committed memory, mmaps and shms

On Fri, Mar 13, 2015 at 03:09:58PM +0100, Michal Hocko wrote: > Well, the memory management subsystem is rather complex and it is not > really trivial to match all the possible combinations into simple > counters. Yes, I imagine. > I would be interested in the particular usecase where you wan

Re: [PATCH v4 02/10] mtd: st_spi_fsm: Fetch boot device locations from DT match tables

On Tue, Feb 24, 2015 at 09:41:10AM +, Lee Jones wrote: > On Mon, 23 Feb 2015, Brian Norris wrote: > > On Tue, Feb 10, 2015 at 03:46:34PM +0800, Lee Jones wrote: > > > On Thu, 05 Feb 2015, Brian Norris wrote: [snip other discussion] > > Now, unless you were able to provide an additional enligh

Re: [PATCH 0/6] CLONE_FD: Task exit notification via file descriptor

On Fri, Mar 13, 2015 at 1:40 AM, Josh Triplett wrote: > This patch series introduces a new clone flag, CLONE_FD, which lets the caller > handle child process exit notification via a file descriptor rather than > SIGCHLD. CLONE_FD makes it possible for libraries to safely launch and manage > child

[PATCH v5 2/4] arm64: dts: Add Qualcomm MSM8916 SoC and evaluation board dts

Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916 evaluation board. At the current time we only boot up a single processor. Signed-off-by: Kumar Gala --- v5: * killed use of skeleton, moved to addr/size cells both being 2 * Added serial alias in prep of being able to spec uart

Re: [RFC] capabilities: Ambient capabilities

On Fri, 13 Mar 2015, Andrew G. Morgan wrote: > > prctl(PR_CAP_AMBIENT, PR_CAP_AMBIENT_RAISE, CAP_SYS_ADMIN); > > system("/bin/bash"); > > Let's call the above two lines [a] and [b]. With this patch, you are > encouraging folk to write programs that contain a line like [a] > already. So, yes, I am

Re: mmotm 2015-03-12-15-17 uploaded (rocker.c)

On 03/12/15 15:18, a...@linux-foundation.org wrote: > The mm-of-the-moment snapshot 2015-03-12-15-17 has been uploaded to > >http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of my -mm

[GIT PULL] DeviceTree fixes for 4.0-rc

Hi Linus, Please pull DT fixes for 4.0. Details below. Rob The following changes since commit 9eccca0843205f87c00404b663188b88eb248051: Linux 4.0-rc3 (2015-03-08 16:09:09 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git tags/devic

Re: [PATCH] selftests/exec: take into account that zero is a success code

On 03/13/2015 09:57 AM, Andrey Vagin wrote: > Cc: Shuah Khan > Signed-off-by: Andrey Vagin Andrey, Please add a meaningful commit log for this patch and resend. -- Shuah > --- > tools/testing/selftests/exec/execveat.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/t

Re: [PATCH] selftests/kcmp: exit with non-zero code in a fail case (v2)

On 03/13/2015 09:55 AM, Andrey Vagin wrote: > Currently this test always returs zero code and a child process returns > non-zero code only if the last testcase failed. > > v2: don't forget to return smth from ksft_exit() Please check patch subject. It is phrased: [PATCH v2] selftests/kcmp: exit w

[PATCH] vxlan: fix wrong usage of VXLAN_VID_MASK

commit dfd8645ea1bd9127 wrongly assumes that VXLAN_VDI_MASK includes eight lower order reserved bits of VNI field that are using for remote checksum offload. Right now, when VNI number greater then 0x, vxlan_udp_encap_recv() will always return with 'bad_flag' error, reducing the usable vni ran

Re: [PATCH 1/2] CAPABILITIES: add cap_isequal helper

On Fri, Mar 13, 2015 at 10:02:46AM -0400, Paul Moore wrote: > On Monday, March 09, 2015 09:35:46 PM Mateusz Guzik wrote: > > Can be used to determine whether two given sets have the same > > capabilities. > > > > Signed-off-by: Mateusz Guzik > > --- > > include/linux/capability.h | 10 ++

Re: [PATCH v3 1/2] x86_64,signal: Fix SS handling for signals delivered to 64-bit programs

On Thu, Mar 12, 2015 at 01:57:51PM -0700, Andy Lutomirski wrote: > From: Andy Lutomirski > > The comment in the signal code says that apps can save/restore other > segments on their own. It's true that apps can *save* SS on their > own, but there's no way for apps to restore it: SYSCALL effectiv

[PATCH v2] mce: use safe MSR accesses

From: Jesse Larrew Certain MSRs are only relevant to a kernel in host mode, and kvm had chosen not to implement these MSRs at all for guests. If a guest kernel ever tried to access these MSRs, the result was a general protection fault. KVM will be separately patched to return 0 when these MSRs a

Re: [PATCH v6 4/4] ARM: dts: enable PCIe support for Cygnus

On 11/03/15 11:06, Ray Jui wrote: > Add PCIe device nodes in bcm-cygnus.dtsi but keep them disabled there. > Only enable them for bcm958300k where PCIe interfaces are populated > > Signed-off-by: Ray Jui > Reviewed-by: Scott Branden Applied to devicetree/next with Arnd's acked-by, thanks! -- F

Re: [PATCH 4/4] x86/fpu: don't abuse drop_init_fpu() in flush_thread()

On Fri, Mar 13, 2015 at 03:55:42PM +0100, Oleg Nesterov wrote: > But please look at drop_init_fpu(). If eagerfpu == F it calls drop_fpu() and > this is what we need. flush_thread() already has the "if (!use_eager_fpu())", > we can shift drop_fpu() there. > > Otherwise, if eagerfpu == T, drop_init_

Re: [PATCH net-next 1/2] bpf: allow extended BPF programs access skb fields

On 3/13/15 2:57 AM, Daniel Borkmann wrote: On 03/13/2015 03:21 AM, Alexei Starovoitov wrote: introduce user accessible mirror of in-kernel 'struct sk_buff': For each member, I'd also add BUILD_BUG_ON()s similarly as we have in convert_bpf_extensions(). That way, people won't forget to adjust t

Re: [PATCH 6/6] clone4: Introduce new CLONE_FD flag to get task exit notification via fd

Josh, I'll certainly try to read this series, but not before next week. but a couple of nits right now. On 03/12, Josh Triplett wrote: > > When passed CLONE_FD, clone4 will return a file descriptor rather than a > PID. When the child process exits, it gets automatically reaped, And even I have

Re: [PATCH 01/15] perf build: Disable default check for libbabeltrace

On Fri, Mar 13, 2015 at 12:36:21PM -0300, Arnaldo Carvalho de Melo wrote: SNIP > > Auto-detecting system features: > ... dwarf: [ on ] > ... glibc: [ on ] > ... gtk2: [ on ] > ... libaudit: [ on ] >

Re: [PATCH 2/3 RFC] ath10k: wmi: match wait_for_completion_timeout return type

Nicholas Mc Guire writes: > Return type of wait_for_completion_timeout is unsigned long not int. > An appropriately named unsigned long is added and the assignments fixed up. > Rather than returning 0 (timeout) or a more or less random remaining time > (completion success) this return 0 or 1 whic

Re: [PATCH v4 2/4] arm64: dts: Add Qualcomm MSM8916 SoC and evaluation board dts

On Fri, Mar 13, 2015 at 03:50:42PM +, Kumar Gala wrote: > > On Mar 13, 2015, at 5:52 AM, Mark Rutland wrote: > > >> +/ { > >> + chosen { > >> + stdout-path = &blsp1_uart2; > >> + }; > > > > It would be good if we had the configuration too (see > > Documentation/devicetree/binding

Re: [PATCH 2/3 RFC] ath10k: wmi: match wait_for_completion_timeout return type

On Fri, 13 Mar 2015, Kalle Valo wrote: > Nicholas Mc Guire writes: > > > Return type of wait_for_completion_timeout is unsigned long not int. > > An appropriately named unsigned long is added and the assignments fixed up. > > Rather than returning 0 (timeout) or a more or less random remaining t

Re: [PATCH 14/16] staging: rtl8723au: Improve readability of two very long lines

On Fri, 2015-03-13 at 10:44 -0500, Larry Finger wrote: > On 03/12/2015 10:15 PM, M. Vefa Bicakci wrote: > > Improve the readability of an if statement and its very long trace > > output line in rtl8723au's rtw_security.c. [] > > diff --git a/drivers/staging/rtl8723au/core/rtw_security.c > > b/driv

<    1   2   3   4   5   6   7   8   9   >