[PATCH v2 01/29] staging/lustre/llite: allocate and free client cache asynchronously

From: Emoly Liu Since the inflight request holds import refcount as well as export, sometimes obd_disconnect() in client_common_put_super() can't put the last refcount of OSC import (e.g. due to network disconnection), this will cause cl_cache being accessed after free. To fix this issue,

Re: [RFC PATCH] x86: Move away from /dev/cpu/*/msr

Borislav Petkov writes: > Comments are, as always, appreciated. Seems like a waste of kernel code to me. The MSR interface works perfectly fine. There are potentially hundreds of useful MSRs, are you going to add new sysfs for each of them? Even the more obscure ones can be very useful for

[PATCH v2 18/29] staging/lustre/ldlm: const qualify struct lustre_handle * params

From: "John L. Hammond" Add a const qualifier to several struct lustre_handle * parameters in the LDLM interface. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17071 Intel-bug-id:

[PATCH v2 18/29] staging/lustre/ldlm: const qualify struct lustre_handle * params

From: "John L. Hammond" Add a const qualifier to several struct lustre_handle * parameters in the LDLM interface. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17071 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7403 Reviewed-by: Andreas Dilger Reviewed-by:

[PATCH v2 08/29] staging/lustre/ptlrpc: missing wakeup for ptlrpc_check_set

From: Liang Zhen This patch changes a few things: - There is no guarantee that request_out_callback will happen before reply_in_callback, if a request got reply and unlinked reply buffer before request_out_callback is called, then the thread waiting on

[PATCH v2 27/29] staging/lustre/osc: glimpse lock should match only with granted locks

From: Andriy Skulysh A deadlock is possible during ccc_prep_size()->ldlm_lock_match() vs cl_io_lock() which is waiting for a matched lock and conflicts with already taken lock before ccc_prep_size(). It is better to send an additional lock request to avoid deadlock.

[PATCH v2 17/29] staging/lustre/llite: change it_data to it_request

From: "John L. Hammond" Change the void *it_data member of struct lookup_intent to struct ptlrpc_request *it_request. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17070 Intel-bug-id:

[PATCH v2 08/29] staging/lustre/ptlrpc: missing wakeup for ptlrpc_check_set

From: Liang Zhen This patch changes a few things: - There is no guarantee that request_out_callback will happen before reply_in_callback, if a request got reply and unlinked reply buffer before request_out_callback is called, then the thread waiting on ptlrpc_request_set will miss wakeup

[PATCH v2 27/29] staging/lustre/osc: glimpse lock should match only with granted locks

From: Andriy Skulysh A deadlock is possible during ccc_prep_size()->ldlm_lock_match() vs cl_io_lock() which is waiting for a matched lock and conflicts with already taken lock before ccc_prep_size(). It is better to send an additional lock request to avoid deadlock. Seagate-bug-id: MRP-3312

[PATCH v2 17/29] staging/lustre/llite: change it_data to it_request

From: "John L. Hammond" Change the void *it_data member of struct lookup_intent to struct ptlrpc_request *it_request. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17070 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7403 Reviewed-by: Andreas Dilger Reviewed-by:

[PATCH v2 04/29] staging/lustre/llite: lock i_lock before __d_drop()

From: Bruno Faccini There has been several Lustre Client crashes reported by sites running with Lustre versions 2.1/2.5, all showing the same dentry->d_hash->next corrupted pointer cause. This patch fixes a regression that has been introduced since a long time by commit

[PATCH v2 29/29] staging: lustre: quiet lockdep recursive lock warning

From: Andreas Dilger Lockdep complains about potential recursive locking during mount because the client configuration log is holding a lock on the MGC obd_device to prevent it from being torn down, while also getting mutexes on the MDC and OSC devices as they are

[PATCH v2 3/3] drm/i915: Enable polling when we don't have hpd

Unfortunately, there's two situations where we lose hpd right now: - Runtime suspend - When we've shut off all of the power wells on Valleyview/Cherryview While it would be nice if this didn't cause issues, this has the ability to get us in some awkward states where a user won't be able to get

[PATCH v2 04/29] staging/lustre/llite: lock i_lock before __d_drop()

From: Bruno Faccini There has been several Lustre Client crashes reported by sites running with Lustre versions 2.1/2.5, all showing the same dentry->d_hash->next corrupted pointer cause. This patch fixes a regression that has been introduced since a long time by commit : (LU-506 kernel: FC15 -

[PATCH v2 29/29] staging: lustre: quiet lockdep recursive lock warning

From: Andreas Dilger Lockdep complains about potential recursive locking during mount because the client configuration log is holding a lock on the MGC obd_device to prevent it from being torn down, while also getting mutexes on the MDC and OSC devices as they are instantiated: Lustre: Mounted

[PATCH v2 3/3] drm/i915: Enable polling when we don't have hpd

Unfortunately, there's two situations where we lose hpd right now: - Runtime suspend - When we've shut off all of the power wells on Valleyview/Cherryview While it would be nice if this didn't cause issues, this has the ability to get us in some awkward states where a user won't be able to get

[PATCH 3/4] MAINTAINERS: Update BCM63XX entry

There are more files being supported by the BCM63XX than simply "arch/arm/mach-bcm/bcm63xx.c" and "arch/arm/include/debug/bcm63xx.S". Add a regex of "bcm63xx" to catch all the other files that are out there. Signed-off-by: Jon Mason --- MAINTAINERS | 3 +-- 1 file

[PATCH 3/4] MAINTAINERS: Update BCM63XX entry

There are more files being supported by the BCM63XX than simply "arch/arm/mach-bcm/bcm63xx.c" and "arch/arm/include/debug/bcm63xx.S". Add a regex of "bcm63xx" to catch all the other files that are out there. Signed-off-by: Jon Mason --- MAINTAINERS | 3 +-- 1 file changed, 1 insertion(+), 2

[PATCH v2 21/29] staging/lustre/llite: don't panic when fid is insane

From: Sergey Cheremencev LASSERT should never be done on data that is received to over the network. Return EINVAL when server returns invalid fid despite of it_status == 0. Signed-off-by: Sergey Cheremencev Seagate-bug-id:

[PATCH v2 21/29] staging/lustre/llite: don't panic when fid is insane

From: Sergey Cheremencev LASSERT should never be done on data that is received to over the network. Return EINVAL when server returns invalid fid despite of it_status == 0. Signed-off-by: Sergey Cheremencev Seagate-bug-id: MRP-3073 Reviewed-on: http://review.whamcloud.com/17985 Intel-bug-id:

[PATCH v2 25/29] staging/lustre/osc: fix signed one bit field

From: Dmitry Eremin Bit field 'oi_lockless' and 'oi_is_active' has one bit and is signed which is confusing. Signed-off-by: Dmitry Eremin Reviewed-on: http://review.whamcloud.com/19196 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7258

[PATCH v2 00/29] Lustre fixes

Changes from v1: This is rebased and retested on top of latest staging tree, one patch dropped because it made it to the tree by other means, two more fixes added. These patches represent another round of Lustre fixes and also a few cleanups that some of the fixes were building up upon. Alex

[PATCH v2 03/29] staging/lustre/llite: Get rid of ll_lock_dcache/ll_unlock_dcache

These are just doing spin_lock/unlock on inode's i_lock, so just do the spinlock directly to make the code more clear Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/llite/dcache.c | 4 ++-- drivers/staging/lustre/lustre/llite/llite_internal.h | 10

Re: [PATCH 0/6] Support DAX for device-mapper dm-linear devices

On Mon, 2016-06-20 at 14:00 -0400, Mike Snitzer wrote: > On Mon, Jun 13 2016 at  6:57pm -0400, > Mike Snitzer wrote: > > > > > On Mon, Jun 13 2016 at  6:21pm -0400, > > Toshi Kani wrote: > > > > > > > > This patch-set adds DAX support to device-mapper

[PATCH v2 03/29] staging/lustre/llite: Get rid of ll_lock_dcache/ll_unlock_dcache

These are just doing spin_lock/unlock on inode's i_lock, so just do the spinlock directly to make the code more clear Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/llite/dcache.c | 4 ++-- drivers/staging/lustre/lustre/llite/llite_internal.h | 10 --

Re: [PATCH 0/6] Support DAX for device-mapper dm-linear devices

On Mon, 2016-06-20 at 14:00 -0400, Mike Snitzer wrote: > On Mon, Jun 13 2016 at  6:57pm -0400, > Mike Snitzer wrote: > > > > > On Mon, Jun 13 2016 at  6:21pm -0400, > > Toshi Kani wrote: > > > > > > > > This patch-set adds DAX support to device-mapper dm-linear devices > > > used by LVM.  It

[PATCH v2 25/29] staging/lustre/osc: fix signed one bit field

From: Dmitry Eremin Bit field 'oi_lockless' and 'oi_is_active' has one bit and is signed which is confusing. Signed-off-by: Dmitry Eremin Reviewed-on: http://review.whamcloud.com/19196 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7258 Reviewed-by: Andreas Dilger Reviewed-by: James

[PATCH v2 00/29] Lustre fixes

Changes from v1: This is rebased and retested on top of latest staging tree, one patch dropped because it made it to the tree by other means, two more fixes added. These patches represent another round of Lustre fixes and also a few cleanups that some of the fixes were building up upon. Alex

[PATCH v2 23/29] staging/lustre/llite: ll_revalidate_dentry update

From: Oleg Drokin There are a couple of cases in ll_revalidate_dentry() where we are pretty sure the dentry is valid, so check for them early and save more expensive checks for later. Signed-off-by: Oleg Drokin ---

[PATCH v2 23/29] staging/lustre/llite: ll_revalidate_dentry update

From: Oleg Drokin There are a couple of cases in ll_revalidate_dentry() where we are pretty sure the dentry is valid, so check for them early and save more expensive checks for later. Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/llite/dcache.c | 11 +++ 1 file changed,

[PATCH v2 02/29] staging/lustre/llite: correct request handling after ll_lookup_it()

From: "John L. Hammond" In the FIFO cases of ll_atomic_open() and ll_lookup_nd() remove spurious calls to ptlrpc_req_finished(). Explain that these cases are unreachable in practice anyway. Signed-off-by: John L. Hammond Reviewed-on:

[PATCH v2 02/29] staging/lustre/llite: correct request handling after ll_lookup_it()

From: "John L. Hammond" In the FIFO cases of ll_atomic_open() and ll_lookup_nd() remove spurious calls to ptlrpc_req_finished(). Explain that these cases are unreachable in practice anyway. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17068 Intel-bug-id:

[PATCH 0/4] MAINTAINERS: update BCM SoC entries

An overall clean-up to the MAINTAINER entries for a few Broadcom SoCs. Jon Mason (4): MAINTAINERS: Fix nsp false-positives MAINTAINERS: Add NS2 entry MAINTAINERS: Update BCM63XX entry MAINTAINERS: Update BCM281XX/BCM11XXX/BCM216XX entry MAINTAINERS | 19 +-- 1 file

[PATCH 2/4] MAINTAINERS: Add NS2 entry

Add NS2 to the Broadcom iProc Subsystem maintainers entry. Since most of the NS2 entries are already covered via the ns* already present there, all that is currently needed is to reference the device tree files. Signed-off-by: Jon Mason --- MAINTAINERS | 1 + 1 file

[PATCH 0/4] MAINTAINERS: update BCM SoC entries

An overall clean-up to the MAINTAINER entries for a few Broadcom SoCs. Jon Mason (4): MAINTAINERS: Fix nsp false-positives MAINTAINERS: Add NS2 entry MAINTAINERS: Update BCM63XX entry MAINTAINERS: Update BCM281XX/BCM11XXX/BCM216XX entry MAINTAINERS | 19 +-- 1 file

[PATCH 2/4] MAINTAINERS: Add NS2 entry

Add NS2 to the Broadcom iProc Subsystem maintainers entry. Since most of the NS2 entries are already covered via the ns* already present there, all that is currently needed is to reference the device tree files. Signed-off-by: Jon Mason --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+)

[PATCH 1/4] MAINTAINERS: Fix nsp false-positives

The 'nsp' regex pattern in the "BROADCOM IPROC ARM ARCHITECTURE" section is getting unintended hits due to the common frequence of these letters appearing in sequence. To change the regex expression to be more specific to the files we care about, add a "bcm" prefix to the regex and add file

[PATCH v2 26/29] staging/lustre: Add documentation for unstable_stats in sysfs

commit ac5b14810952 ("staging: lustre: osc: Track and limit "unstable" pages") added a new sysfs variable, but corresponding bit of documentation was not forgotten. Signed-off-by: Oleg Drokin --- drivers/staging/lustre/sysfs-fs-lustre | 8 1 file changed, 8

[PATCH 1/4] MAINTAINERS: Fix nsp false-positives

The 'nsp' regex pattern in the "BROADCOM IPROC ARM ARCHITECTURE" section is getting unintended hits due to the common frequence of these letters appearing in sequence. To change the regex expression to be more specific to the files we care about, add a "bcm" prefix to the regex and add file

[PATCH v2 26/29] staging/lustre: Add documentation for unstable_stats in sysfs

commit ac5b14810952 ("staging: lustre: osc: Track and limit "unstable" pages") added a new sysfs variable, but corresponding bit of documentation was not forgotten. Signed-off-by: Oleg Drokin --- drivers/staging/lustre/sysfs-fs-lustre | 8 1 file changed, 8 insertions(+) diff --git

[PATCH v2 16/29] staging/lustre: Inline Lustre intent disposition functions

They are just one-liners, so no point in having them exported and called through a different module. Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/include/lustre_intent.h | 15 +++ drivers/staging/lustre/lustre/include/lustre_mdc.h| 3 ---

[PATCH v2 16/29] staging/lustre: Inline Lustre intent disposition functions

They are just one-liners, so no point in having them exported and called through a different module. Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/include/lustre_intent.h | 15 +++ drivers/staging/lustre/lustre/include/lustre_mdc.h| 3 ---

[PATCH v2 11/29] staging/lustre/ptlrpc: lost bulk leads to a hang

From: Vitaly Fertman The reverse order of request_out_callback() and reply_in_callback() puts the RPC into UNREGISTERING state, which is waiting for RPC & bulk md unlink, whereas only RPC md unlink has been called so far. If bulk is lost, even expired_set does not

[PATCH v2 11/29] staging/lustre/ptlrpc: lost bulk leads to a hang

From: Vitaly Fertman The reverse order of request_out_callback() and reply_in_callback() puts the RPC into UNREGISTERING state, which is waiting for RPC & bulk md unlink, whereas only RPC md unlink has been called so far. If bulk is lost, even expired_set does not check for UNREGISTERING state.

[PATCH v2 13/29] staging/lustre: LDLM_DEBUG() shouldn't be passed \n

From: Alex Zhuravlev as it adds own \n, so any extra \n break log format. Signed-off-by: Alex Zhuravlev Reviewed-on: http://review.whamcloud.com/17494 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7521 Reviewed-by: James Simmons

[PATCH v2 13/29] staging/lustre: LDLM_DEBUG() shouldn't be passed \n

From: Alex Zhuravlev as it adds own \n, so any extra \n break log format. Signed-off-by: Alex Zhuravlev Reviewed-on: http://review.whamcloud.com/17494 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7521 Reviewed-by: James Simmons Reviewed-by: John L. Hammond Reviewed-by: Andreas Dilger

[PATCH v2 15/29] staging/lustre/llite: flatten struct lookup_intent

From: "John L. Hammond" Replace the union in struct lookup_intent with the members of struct lustre_indent_data. Remove the then unused struct lustre_intent_data. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17069

[PATCH v2 15/29] staging/lustre/llite: flatten struct lookup_intent

From: "John L. Hammond" Replace the union in struct lookup_intent with the members of struct lustre_indent_data. Remove the then unused struct lustre_intent_data. Signed-off-by: John L. Hammond Reviewed-on: http://review.whamcloud.com/17069 Intel-bug-id:

[PATCH v2 10/29] staging/lustre/ptlrpc: Remove __ptlrpc_request_bufs_pack

From: Ben Evans Combine __ptlrpc_request_bufs_pack into ptlrpc_request_bufs_pack because it was an unnecessary wrapper otherwise. Signed-off-by: Ben Evans Reviewed-on: http://review.whamcloud.com/16765 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7269

[PATCH v2 10/29] staging/lustre/ptlrpc: Remove __ptlrpc_request_bufs_pack

From: Ben Evans Combine __ptlrpc_request_bufs_pack into ptlrpc_request_bufs_pack because it was an unnecessary wrapper otherwise. Signed-off-by: Ben Evans Reviewed-on: http://review.whamcloud.com/16765 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7269 Reviewed-by: Frank Zago

[PATCH v2 14/29] staging/lustre: Add newline to LU_OBJECT_DEBUG() message

From: Bob Glossman LU_OBJECT_DEBUG expects non \n terminated message from the caller, so it should add it's own to keep debug logger happy. Signed-off-by: Bob Glossman Reviewed-on: http://review.whamcloud.com/19960 Intel-bug-id:

[PATCH v2 12/29] staging/lustre/llite: take trunc_sem only at vvp layer

From: Patrick Farrell The lli_trunc_sem is taken in 'read' mode in both ll_page_mkwrite and vvp_io_fault_start. This can lead to a deadlock with another thread which asks for the semaphore in write mode between thse two read calls. Since all users of lli_trunc_sem are in the vvp

[PATCH v2 09/29] staging/lustre/ptlrpc: Early Reply vs Reply MDunlink

From: Vitaly Fertman A race between unregister_reply & early reply. When buffers are busy for the early transfer, they cannon be unlinked by unregister_reply, so the RPC gets into UNREGISTERING state. The coming reply_in_callback for the early RPC already has unlinked

[PATCH v2 14/29] staging/lustre: Add newline to LU_OBJECT_DEBUG() message

From: Bob Glossman LU_OBJECT_DEBUG expects non \n terminated message from the caller, so it should add it's own to keep debug logger happy. Signed-off-by: Bob Glossman Reviewed-on: http://review.whamcloud.com/19960 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8094 Reviewed-by: Andreas

[PATCH v2 12/29] staging/lustre/llite: take trunc_sem only at vvp layer

From: Patrick Farrell The lli_trunc_sem is taken in 'read' mode in both ll_page_mkwrite and vvp_io_fault_start. This can lead to a deadlock with another thread which asks for the semaphore in write mode between thse two read calls. Since all users of lli_trunc_sem are in the vvp layer, we can

[PATCH v2 09/29] staging/lustre/ptlrpc: Early Reply vs Reply MDunlink

From: Vitaly Fertman A race between unregister_reply & early reply. When buffers are busy for the early transfer, they cannon be unlinked by unregister_reply, so the RPC gets into UNREGISTERING state. The coming reply_in_callback for the early RPC already has unlinked flag set due to previous

Re: [PATCH] blktrace: reword comment about time overflow

Arnd Bergmann writes: > Jeff Moyer looked up the blktrace source to see if an overflow might > happen. The situation is as follows: > > - The time stamp is not used by the program itself, only for > printing human-readable output. > - We normally don't print the timestamp at

Re: [PATCH] blktrace: reword comment about time overflow

Arnd Bergmann writes: > Jeff Moyer looked up the blktrace source to see if an overflow might > happen. The situation is as follows: > > - The time stamp is not used by the program itself, only for > printing human-readable output. > - We normally don't print the timestamp at all, except when

Re: [PATCH v9 10/12] kthread: Allow to cancel kthread work

On Thu, Jun 16, 2016 at 01:17:29PM +0200, Petr Mladek wrote: > +/* > + * Returns true when the work could not be queued at the moment. > + * It happens when it is already pending in a worker list > + * or when it is being cancelled. > + * > + * This function must be called under

Re: [PATCH v9 10/12] kthread: Allow to cancel kthread work

On Thu, Jun 16, 2016 at 01:17:29PM +0200, Petr Mladek wrote: > +/* > + * Returns true when the work could not be queued at the moment. > + * It happens when it is already pending in a worker list > + * or when it is being cancelled. > + * > + * This function must be called under

Re: [PATCH 5/5] vmlinux.lds.h: replace config_enabled() with IS_ENABLED()

Dne 14.6.2016 v 07:58 Masahiro Yamada napsal(a): > The use of config_enabled() against config options is ambiguous. > > Now, IS_ENABLED() is implemented purely with macro expansion, so > let's replace config_enabled() with IS_ENABLED(). > > Signed-off-by: Masahiro Yamada

Re: [PATCH 5/5] vmlinux.lds.h: replace config_enabled() with IS_ENABLED()

Dne 14.6.2016 v 07:58 Masahiro Yamada napsal(a): > The use of config_enabled() against config options is ambiguous. > > Now, IS_ENABLED() is implemented purely with macro expansion, so > let's replace config_enabled() with IS_ENABLED(). > > Signed-off-by: Masahiro Yamada I applied the whole

Re: [PATCH v8 2/8] perf evlist: Introduce aux evlist

Em Mon, Jun 20, 2016 at 10:47:19AM +, Wang Nan escreveu: > An auxiliary evlist is created by perf_evlist__new_aux() using an > existing evlist as its parent. An auxiliary evlist can have its own > 'struct perf_mmap', but can't have any other data. User should use its > parent instead when

Re: [PATCH v8 2/8] perf evlist: Introduce aux evlist

Em Mon, Jun 20, 2016 at 10:47:19AM +, Wang Nan escreveu: > An auxiliary evlist is created by perf_evlist__new_aux() using an > existing evlist as its parent. An auxiliary evlist can have its own > 'struct perf_mmap', but can't have any other data. User should use its > parent instead when

Re: [PATCH 1/2] x86/entry: Avoid interrupt flag save and restore

On Mon, Jun 20, 2016 at 7:58 AM, Paolo Bonzini wrote: > Thanks to all the work that was done by Andy Lutomirski and others, > enter_from_user_mode and prepare_exit_to_usermode are now called only with > interrupts disabled. Let's provide them a version of

Re: [PATCH 1/2] x86/entry: Avoid interrupt flag save and restore

On Mon, Jun 20, 2016 at 7:58 AM, Paolo Bonzini wrote: > Thanks to all the work that was done by Andy Lutomirski and others, > enter_from_user_mode and prepare_exit_to_usermode are now called only with > interrupts disabled. Let's provide them a version of user_enter/user_exit > that skips saving

Re: [PATCH] coccicheck: Allow for overriding spatch flags

On Sun, Jun 12, 2016 at 11:45:57PM +0200, Julia Lawall wrote: > > > On Sun, 12 Jun 2016, Nicolas Palix (LIG) wrote: > > > Le 12/06/16 à 21:04, Deepa Dinamani a écrit : > > > Documentation/coccinelle.txt suggests using the SPFLAGS > > > make variable to pass additional options to spatch. > > >

Re: [PATCH] coccicheck: Allow for overriding spatch flags

On Sun, Jun 12, 2016 at 11:45:57PM +0200, Julia Lawall wrote: > > > On Sun, 12 Jun 2016, Nicolas Palix (LIG) wrote: > > > Le 12/06/16 à 21:04, Deepa Dinamani a écrit : > > > Documentation/coccinelle.txt suggests using the SPFLAGS > > > make variable to pass additional options to spatch. > > >

Re: [PATCH] memcg: mem_cgroup_migrate() may be called with irq disabled

On 06/20/2016 08:41 PM, Tejun Heo wrote: > Hello, > > Christian, I *think* this should fix it. Can you please verify? I cannot reliably reproduce the bug :-/,but at least I have not seen it with this patch and the patch makes sense and matches the traces. > > Thanks! > -- 8< -- >

Re: [PATCH] memcg: mem_cgroup_migrate() may be called with irq disabled

On 06/20/2016 08:41 PM, Tejun Heo wrote: > Hello, > > Christian, I *think* this should fix it. Can you please verify? I cannot reliably reproduce the bug :-/,but at least I have not seen it with this patch and the patch makes sense and matches the traces. > > Thanks! > -- 8< -- >

Re: [PATCH 5/7] random: replace non-blocking pool with a Chacha20-based CRNG

On 06/20/16 08:49, Stephan Mueller wrote: > Am Montag, 20. Juni 2016, 11:01:47 schrieb Theodore Ts'o: > > Hi Theodore, > >> >> So simply doing chacha20 encryption in a tight loop in the kernel >> might not be a good proxy for what would actually happen in real life >> when someone calls

Re: [PATCH v9 12/12] kthread: Better support freezable kthread workers

On Thu, Jun 16, 2016 at 01:17:31PM +0200, Petr Mladek wrote: > This patch allows to make kthread worker freezable via a new @flags > parameter. It will allow to avoid an init work in some kthreads. > > It currently does not affect the function of kthread_worker_fn() > but it might help to do some

Re: [PATCH 5/7] random: replace non-blocking pool with a Chacha20-based CRNG

On 06/20/16 08:49, Stephan Mueller wrote: > Am Montag, 20. Juni 2016, 11:01:47 schrieb Theodore Ts'o: > > Hi Theodore, > >> >> So simply doing chacha20 encryption in a tight loop in the kernel >> might not be a good proxy for what would actually happen in real life >> when someone calls

Re: [PATCH v9 12/12] kthread: Better support freezable kthread workers

On Thu, Jun 16, 2016 at 01:17:31PM +0200, Petr Mladek wrote: > This patch allows to make kthread worker freezable via a new @flags > parameter. It will allow to avoid an init work in some kthreads. > > It currently does not affect the function of kthread_worker_fn() > but it might help to do some

Re: [PATCH v9 11/12] kthread: Allow to modify delayed kthread work

On Thu, Jun 16, 2016 at 01:17:30PM +0200, Petr Mladek wrote: > There are situations when we need to modify the delay of a delayed kthread > work. For example, when the work depends on an event and the initial delay > means a timeout. Then we want to queue the work immediately when the event >

Re: [PATCH v9 11/12] kthread: Allow to modify delayed kthread work

On Thu, Jun 16, 2016 at 01:17:30PM +0200, Petr Mladek wrote: > There are situations when we need to modify the delay of a delayed kthread > work. For example, when the work depends on an event and the initial delay > means a timeout. Then we want to queue the work immediately when the event >

Re: [PATCH] clk: renesas: build clk-rcar-gen2.o for R8A7792

Hi Arnd, On Mon, Jun 20, 2016 at 5:43 PM, Arnd Bergmann wrote: > The newly added support for R8A7792 causes build failures > because we try to call rcar_gen2_clocks_init but that is not > built into the kernel: > > arch/arm/mach-shmobile/built-in.o: In function

Re: [PATCH] clk: renesas: build clk-rcar-gen2.o for R8A7792

Hi Arnd, On Mon, Jun 20, 2016 at 5:43 PM, Arnd Bergmann wrote: > The newly added support for R8A7792 causes build failures > because we try to call rcar_gen2_clocks_init but that is not > built into the kernel: > > arch/arm/mach-shmobile/built-in.o: In function `rcar_gen2_timer_init': >

Re: [PATCH v2 1/3] coccinelle: also catch kzfree() issues

On Mon, 20 Jun 2016, Michal Marek wrote: > On 2016-05-23 17:18, Julia Lawall wrote: > > > > > > On Mon, 23 May 2016, Yann Droneaud wrote: > > > >> Since commit 3ef0e5ba4673 ('slab: introduce kzfree()'), > >> kfree() is no more the only function to be considered: > >> kzfree() should be

Re: [PATCH v2 1/3] coccinelle: also catch kzfree() issues

On Mon, 20 Jun 2016, Michal Marek wrote: > On 2016-05-23 17:18, Julia Lawall wrote: > > > > > > On Mon, 23 May 2016, Yann Droneaud wrote: > > > >> Since commit 3ef0e5ba4673 ('slab: introduce kzfree()'), > >> kfree() is no more the only function to be considered: > >> kzfree() should be

[PATCH] crypto : async implementation for sha1-mb

From: Megha Dey Herbert wants the sha1-mb algorithm to have an async implementation: https://lkml.org/lkml/2016/4/5/286. Currently, sha1-mb uses an async interface for the outer algorithm and a sync interface for the inner algorithm. This patch introduces a async

Re: [PATCH 2/2] x86/entry: Inline enter_from_user_mode

On Mon, 2016-06-20 at 16:58 +0200, Paolo Bonzini wrote: > This matches what is already done for prepare_exit_to_usermode, > and saves about 60 clock cycles (4% speedup) with the benchmark > in the previous commit message. > > Cc: Andy Lutomirski > Cc: Peter Zijlstra

Re: [PATCH 2/2] x86/entry: Inline enter_from_user_mode

On Mon, 2016-06-20 at 16:58 +0200, Paolo Bonzini wrote: > This matches what is already done for prepare_exit_to_usermode, > and saves about 60 clock cycles (4% speedup) with the benchmark > in the previous commit message. > > Cc: Andy Lutomirski > Cc: Peter Zijlstra > Cc: Rik van Riel > Cc: H.

[PATCH] crypto : async implementation for sha1-mb

From: Megha Dey Herbert wants the sha1-mb algorithm to have an async implementation: https://lkml.org/lkml/2016/4/5/286. Currently, sha1-mb uses an async interface for the outer algorithm and a sync interface for the inner algorithm. This patch introduces a async interface for even the inner

Re: [PATCH 3/2] context_tracking: move rcu_virt_note_context_switch out of kvm_host.h

On Mon, 2016-06-20 at 16:58 +0200, Paolo Bonzini wrote: > Make kvm_guest_{enter,exit} and __kvm_guest_{enter,exit} trivial > wrappers > around the code in context_tracking.h.  Name the context_tracking.h > functions > consistently with what those for kernel<->user switch. > > Cc: Andy Lutomirski

Re: [PATCH 4/2] KVM: remove kvm_guest_enter/exit wrappers

On Mon, 2016-06-20 at 16:58 +0200, Paolo Bonzini wrote: > Use the functions from context_tracking.h directly. > > Cc: Andy Lutomirski > Cc: Peter Zijlstra > Cc: Rik van Riel > Cc: H. Peter Anvin > Cc: Ingo Molnar

Re: [PATCH 4/2] KVM: remove kvm_guest_enter/exit wrappers

On Mon, 2016-06-20 at 16:58 +0200, Paolo Bonzini wrote: > Use the functions from context_tracking.h directly. > > Cc: Andy Lutomirski > Cc: Peter Zijlstra > Cc: Rik van Riel > Cc: H. Peter Anvin > Cc: Ingo Molnar > Cc: Thomas Gleixner > Signed-off-by: Paolo Bonzini > Reviewed-by: Rik van

Re: [PATCH 3/2] context_tracking: move rcu_virt_note_context_switch out of kvm_host.h

On Mon, 2016-06-20 at 16:58 +0200, Paolo Bonzini wrote: > Make kvm_guest_{enter,exit} and __kvm_guest_{enter,exit} trivial > wrappers > around the code in context_tracking.h.  Name the context_tracking.h > functions > consistently with what those for kernel<->user switch. > > Cc: Andy Lutomirski

Re: [PATCH 1/2] x86/entry: Avoid interrupt flag save and restore

On Mon, 2016-06-20 at 16:58 +0200, Paolo Bonzini wrote: > Thanks to all the work that was done by Andy Lutomirski and others, > enter_from_user_mode and prepare_exit_to_usermode are now called only > with > interrupts disabled.  Let's provide them a version of > user_enter/user_exit > that skips

Re: [PATCH 1/2] x86/entry: Avoid interrupt flag save and restore

On Mon, 2016-06-20 at 16:58 +0200, Paolo Bonzini wrote: > Thanks to all the work that was done by Andy Lutomirski and others, > enter_from_user_mode and prepare_exit_to_usermode are now called only > with > interrupts disabled.  Let's provide them a version of > user_enter/user_exit > that skips

Re: [PATCH v9 09/12] kthread: Initial support for delayed kthread work

Hello, On Thu, Jun 16, 2016 at 01:17:28PM +0200, Petr Mladek wrote: > +/** > + * kthread_delayed_work_timer_fn - callback that queues the associated > kthread > + * delayed work when the timer expires. > + * @__data: pointer to the data associated with the timer > + * > + * The format of the

Re: [PATCH v9 09/12] kthread: Initial support for delayed kthread work

Hello, On Thu, Jun 16, 2016 at 01:17:28PM +0200, Petr Mladek wrote: > +/** > + * kthread_delayed_work_timer_fn - callback that queues the associated > kthread > + * delayed work when the timer expires. > + * @__data: pointer to the data associated with the timer > + * > + * The format of the

Re: [PATCH v2 4/5] ASoC: tpa6130a2: Add DAPM support

On 20-06-2016 16:44, Lars-Peter Clausen wrote: + /* before widget power up */ + if (SND_SOC_DAPM_EVENT_ON(event)) { + /* Turn on the chip */ + tpa6130a2_power(data, true); + /* Sync the registers */ + ret =

Re: [PATCH v2 4/5] ASoC: tpa6130a2: Add DAPM support

On 20-06-2016 16:44, Lars-Peter Clausen wrote: + /* before widget power up */ + if (SND_SOC_DAPM_EVENT_ON(event)) { + /* Turn on the chip */ + tpa6130a2_power(data, true); + /* Sync the registers */ + ret =

Re: [PATCH v9 08/12] kthread: Detect when a kthread work is used by more workers

Hello, On Thu, Jun 16, 2016 at 01:17:27PM +0200, Petr Mladek wrote: > diff --git a/kernel/kthread.c b/kernel/kthread.c > index 567ec49b4872..8e9548649c86 100644 > --- a/kernel/kthread.c > +++ b/kernel/kthread.c > @@ -574,6 +574,9 @@ EXPORT_SYMBOL_GPL(__kthread_init_worker); > * The works are

Re: [PATCH v9 08/12] kthread: Detect when a kthread work is used by more workers

Hello, On Thu, Jun 16, 2016 at 01:17:27PM +0200, Petr Mladek wrote: > diff --git a/kernel/kthread.c b/kernel/kthread.c > index 567ec49b4872..8e9548649c86 100644 > --- a/kernel/kthread.c > +++ b/kernel/kthread.c > @@ -574,6 +574,9 @@ EXPORT_SYMBOL_GPL(__kthread_init_worker); > * The works are

Re: [PATCH V3] clocksource/drivers/bcm_kona: Convert init function to return error

On 06/20/2016 07:50 PM, Ray Jui wrote: [ ... ] -CLOCKSOURCE_OF_DECLARE(bcm_kona, "bcm,kona-timer", kona_timer_init); +CLOCKSOURCE_OF_DECLARE_RET(bcm_kona, "bcm,kona-timer", kona_timer_init); Looks good to me! Acked-by: Ray Jui Can you have a quick look at the patch

Re: [PATCH V3] clocksource/drivers/bcm_kona: Convert init function to return error

On 06/20/2016 07:50 PM, Ray Jui wrote: [ ... ] -CLOCKSOURCE_OF_DECLARE(bcm_kona, "bcm,kona-timer", kona_timer_init); +CLOCKSOURCE_OF_DECLARE_RET(bcm_kona, "bcm,kona-timer", kona_timer_init); Looks good to me! Acked-by: Ray Jui Can you have a quick look at the patch [63/63] for the kona

[PATCH 8/8] arm64: dts: db820c: add support to external sd card.

This patch adds support to external sd card. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c-pins.dtsi | 39 +++ arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 10 ++ 2 files changed, 49 insertions(+)

[PATCH 8/8] arm64: dts: db820c: add support to external sd card.

This patch adds support to external sd card. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c-pins.dtsi | 39 +++ arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 10 ++ 2 files changed, 49 insertions(+) create mode 100644

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