[tip:locking/core] kernel/locking: Compute 'current' directly

Commit-ID: d269a8b8c57523a2e328c1ff44fe791e13df3d37 Gitweb: http://git.kernel.org/tip/d269a8b8c57523a2e328c1ff44fe791e13df3d37 Author: Davidlohr Bueso AuthorDate: Tue, 3 Jan 2017 13:43:13 -0800 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:14:14 +0100 kernel/locking: Compute '

[tip:locking/core] drivers/tty: Compute 'current' directly

Commit-ID: 5376f2e722026e91cb46384bda8d8b3e9f88217c Gitweb: http://git.kernel.org/tip/5376f2e722026e91cb46384bda8d8b3e9f88217c Author: Davidlohr Bueso AuthorDate: Tue, 3 Jan 2017 13:43:12 -0800 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:14:13 +0100 drivers/tty: Compute 'cur

[tip:locking/core] sched/core: Remove set_task_state()

Commit-ID: 642fa448ae6b3a4e5e8737054a094173405b7643 Gitweb: http://git.kernel.org/tip/642fa448ae6b3a4e5e8737054a094173405b7643 Author: Davidlohr Bueso AuthorDate: Tue, 3 Jan 2017 13:43:14 -0800 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:14:16 +0100 sched/core: Remove set_ta

[tip:locking/core] sched/wait, RCU: Introduce rcuwait machinery

Commit-ID: 8f95c90ceb541a38ac16fec48c05142ef1450c25 Gitweb: http://git.kernel.org/tip/8f95c90ceb541a38ac16fec48c05142ef1450c25 Author: Davidlohr Bueso AuthorDate: Wed, 11 Jan 2017 07:22:25 -0800 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:14:33 +0100 sched/wait, RCU: Introdu

[PATCH] sparc32: mm: srmmu: add __ro_after_init to sparc32_cachetlb_ops structures

The objects viking_ops, viking_sun4d_smp_ops and smp_cachetlb_ops of type sparc32_cachetlb_ops are not modified anywhere after getting modified in the init functions. Inside init their reference is also stored in a pointer of type const struct sparc32_cachetlb_ops *. So these structures are never

[tip:locking/core] locking/percpu-rwsem: Replace waitqueue with rcuwait

Commit-ID: 52b94129f274937e4c25dd17b76697664a3c43c9 Gitweb: http://git.kernel.org/tip/52b94129f274937e4c25dd17b76697664a3c43c9 Author: Davidlohr Bueso AuthorDate: Wed, 11 Jan 2017 07:22:26 -0800 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:14:35 +0100 locking/percpu-rwsem: Re

[PATCH 0/4] Drop drivers for Exynos4415

Hi, Support for Exynos4415 is being removed because: 1. There are no upstream users, 2. There are no known downstream users, 3. Except compile testing, you cannot build working kernel for Exynos4415 anymore. Patches are rebased on current next and are independent. Please pick up as you wish.

[PATCH 1/4] ARM: EXYNOS: Remove Exynos4415 driver (SoC not supported anymore)

Support for Exynos4415 is going away because there are no internal nor external users. Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), the platform cannot be instantiated so remove also the mach code. Signed-off-by: Krzysztof Kozlowski --- arch/arm/mach-exynos/Kconfig

[PATCH 4/4] drm: exynos: Remove support for Exynos4415 (SoC not supported anymore)

Support for Exynos4415 is going away because there are no internal nor external users. Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), the platform cannot be instantiated so remove also the drivers. Signed-off-by: Krzysztof Kozlowski --- .../devicetree/bindings/display/e

[PATCH 2/4] clk: samsung: Remove Exynos4415 driver (SoC not supported anymore)

Support for Exynos4415 is going away because there are no internal nor external users. Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), the platform cannot be instantiated so remove also the drivers. Signed-off-by: Krzysztof Kozlowski --- .../devicetree/bindings/clock/exy

[PATCH 3/4] pinctrl: samsung: Remove support for Exynos4415 (SoC not supported anymore)

Support for Exynos4415 is going away because there are no internal nor external users. Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), the platform cannot be instantiated so remove also the drivers. Signed-off-by: Krzysztof Kozlowski --- drivers/pinctrl/samsung/pinctrl-e

[tip:sched/core] sched/fair: Push rq lock pin/unpin into idle_balance()

Commit-ID: 46f69fa33712ad12ccaa723e46ed5929ee93589b Gitweb: http://git.kernel.org/tip/46f69fa33712ad12ccaa723e46ed5929ee93589b Author: Matt Fleming AuthorDate: Wed, 21 Sep 2016 14:38:12 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:29:32 +0100 sched/fair: Push rq lock pi

[tip:sched/core] sched/core: Add wrappers for lockdep_(un)pin_lock()

Commit-ID: d8ac897137a230ec351269f6378017f2decca512 Gitweb: http://git.kernel.org/tip/d8ac897137a230ec351269f6378017f2decca512 Author: Matt Fleming AuthorDate: Wed, 21 Sep 2016 14:38:10 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:29:30 +0100 sched/core: Add wrappers fo

[tip:sched/core] sched/core: Reset RQCF_ACT_SKIP before unpinning rq->lock

Commit-ID: 92509b732baf14c59ca702307270cfaa3a585ae7 Gitweb: http://git.kernel.org/tip/92509b732baf14c59ca702307270cfaa3a585ae7 Author: Matt Fleming AuthorDate: Wed, 21 Sep 2016 14:38:11 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:29:31 +0100 sched/core: Reset RQCF_ACT_

[tip:sched/core] sched/core: Add debugging code to catch missing update_rq_clock() calls

Commit-ID: cb42c9a3e23448c3f9a25417fae6309b1a92 Gitweb: http://git.kernel.org/tip/cb42c9a3e23448c3f9a25417fae6309b1a92 Author: Matt Fleming AuthorDate: Wed, 21 Sep 2016 14:38:13 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:29:35 +0100 sched/core: Add debugging c

[tip:sched/core] sched/deadline: Show leftover runtime and abs deadline in /proc/*/sched

Commit-ID: 59f8c2989283bbd3df9fcfb22494d84f4852e536 Gitweb: http://git.kernel.org/tip/59f8c2989283bbd3df9fcfb22494d84f4852e536 Author: Tommaso Cucinotta AuthorDate: Wed, 26 Oct 2016 11:17:17 +0200 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:30:00 +0100 sched/deadline: Show l

[tip:sched/core] sched/core: Fix group_entity's share update

Commit-ID: 89ee048f3cc796db6f26906c6bef4edf0bee70fd Gitweb: http://git.kernel.org/tip/89ee048f3cc796db6f26906c6bef4edf0bee70fd Author: Vincent Guittot AuthorDate: Wed, 21 Dec 2016 16:50:26 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:30:02 +0100 sched/core: Fix group_en

[tip:sched/core] sched/fair: Explain why MIN_SHARES isn't scaled in calc_cfs_shares()

Commit-ID: b8fd8423697b9ec729c5bb91737faad84ae19985 Gitweb: http://git.kernel.org/tip/b8fd8423697b9ec729c5bb91737faad84ae19985 Author: Dietmar Eggemann AuthorDate: Wed, 11 Jan 2017 11:29:47 + Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:30:02 +0100 sched/fair: Explain why

[tip:sched/core] sched/core: move IO scheduling accounting from io_schedule_timeout() into scheduler

Commit-ID: e33a9bba85a869b85fd0a7f16e21a5ec8977e325 Gitweb: http://git.kernel.org/tip/e33a9bba85a869b85fd0a7f16e21a5ec8977e325 Author: Tejun Heo AuthorDate: Wed, 7 Dec 2016 15:48:41 -0500 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:30:03 +0100 sched/core: move IO scheduling

Re: [PATCH 2/3] iio: adc: ti-ads7950: Drop "ti-" prefix from module name

On 11/01/17 17:52, David Lechner wrote: > This drops the "ti-" prefix from the module name. It makes the module name > consistent with other iio ti-ads* drivers and it makes the driver work > with device tree (the spi subsystem drops the "ti," prefix when matching > compatible strings from device t

Re: [PATCH] rcu: Narrow early boot window of illegal synchronous grace periods

On Sat, Jan 14, 2017 at 01:27:40PM +0100, Rafael J. Wysocki wrote: > OK, so this fixes the problem with synchronize_rcu_expedited() in > acpi_os_map_cleanup(), right? Yeah. > I wonder if the ACPI-specific fix is still needed, then? It is not strictly necessary. If you still think it would be bet

[tip:sched/core] sched/core: Separate out io_schedule_prepare() and io_schedule_finish()

Commit-ID: 10ab56434f2f633a51e432ee8b7c29e12438e163 Gitweb: http://git.kernel.org/tip/10ab56434f2f633a51e432ee8b7c29e12438e163 Author: Tejun Heo AuthorDate: Fri, 28 Oct 2016 12:58:10 -0400 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:30:04 +0100 sched/core: Separate out io_sc

[tip:sched/core] locking/mutex, sched/wait: Add mutex_lock_io()

Commit-ID: 1460cb65a10f6c7a6e3a1c76513338861a0a43b6 Gitweb: http://git.kernel.org/tip/1460cb65a10f6c7a6e3a1c76513338861a0a43b6 Author: Tejun Heo AuthorDate: Fri, 28 Oct 2016 12:58:11 -0400 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:30:05 +0100 locking/mutex, sched/wait: Add

[tip:sched/core] fs/jbd2, locking/mutex, sched/wait: Use mutex_lock_io() for journal->j_checkpoint_mutex

Commit-ID: 6fa7aa50b2c48400bbd045daf3a2498882eb0596 Gitweb: http://git.kernel.org/tip/6fa7aa50b2c48400bbd045daf3a2498882eb0596 Author: Tejun Heo AuthorDate: Fri, 28 Oct 2016 12:58:12 -0400 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:30:06 +0100 fs/jbd2, locking/mutex, sched/

Re: [PATCH 3/3] iio: adc: ti-ads7950: Change regulator matching string to "vref"

On 11/01/17 17:52, David Lechner wrote: > This changes the reference voltage regulator matching string from "refin" > to "vref". This is to be consistent with other A/DC chips that also use > "vref-supply" in their device tree bindings. > > Signed-off-by: David Lechner > --- > drivers/iio/adc/ti

[tip:timers/core] math64, timers: Fix 32bit mul_u64_u32_shr() and friends

Commit-ID: 9e3d6223d2093a8903c8f570a06284453ee59944 Gitweb: http://git.kernel.org/tip/9e3d6223d2093a8903c8f570a06284453ee59944 Author: Peter Zijlstra AuthorDate: Fri, 9 Dec 2016 09:30:11 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:31:50 +0100 math64, timers: Fix 32bit

[tip:locking/core] locking/ww_mutex: Fix compilation of __WW_MUTEX_INITIALIZER

Commit-ID: af2e859edd477fa1ea3d1d106f41a595cff3d162 Gitweb: http://git.kernel.org/tip/af2e859edd477fa1ea3d1d106f41a595cff3d162 Author: Chris Wilson AuthorDate: Thu, 1 Dec 2016 11:47:04 + Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:37:13 +0100 locking/ww_mutex: Fix compil

Re: [PATCH 1/3] DT/bindings: Add bindings for TI ADS7950 A/DC chips

On 11/01/17 17:52, David Lechner wrote: > This adds device tree bindings for the TI ADS7950 family of A/DC chips. > > Signed-off-by: David Lechner This is in of itself good, but we may need to have some deprecated elements to continue supporting what was implicitly happening with the missnaming s

[tip:locking/core] locking/ww_mutex: Add ww_mutex to locktorture test

Commit-ID: 0186a6cbdc6287fde65858e5d9c714dc167b8ace Gitweb: http://git.kernel.org/tip/0186a6cbdc6287fde65858e5d9c714dc167b8ace Author: Chris Wilson AuthorDate: Thu, 1 Dec 2016 11:47:05 + Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:37:14 +0100 locking/ww_mutex: Add ww_mut

[tip:locking/core] locking/ww_mutex: Begin kselftests for ww_mutex

Commit-ID: f2a5fec17395f259d54daa8833d81b00cceb15c3 Gitweb: http://git.kernel.org/tip/f2a5fec17395f259d54daa8833d81b00cceb15c3 Author: Chris Wilson AuthorDate: Thu, 1 Dec 2016 11:47:06 + Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:37:14 +0100 locking/ww_mutex: Begin ksel

[tip:locking/core] locking/ww_mutex: Add kselftests for ww_mutex ABBA deadlock detection

Commit-ID: 70207686e492fb97c11d88ae7d8ebce7d2d080aa Gitweb: http://git.kernel.org/tip/70207686e492fb97c11d88ae7d8ebce7d2d080aa Author: Chris Wilson AuthorDate: Thu, 1 Dec 2016 11:47:08 + Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:37:16 +0100 locking/ww_mutex: Add kselft

[tip:locking/core] locking/ww_mutex: Add kselftests for ww_mutex AA deadlock detection

Commit-ID: c22fb3807fd0a3bdd98c13c4d2190ab064e6c09d Gitweb: http://git.kernel.org/tip/c22fb3807fd0a3bdd98c13c4d2190ab064e6c09d Author: Chris Wilson AuthorDate: Thu, 1 Dec 2016 11:47:07 + Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:37:15 +0100 locking/ww_mutex: Add kselft

[tip:locking/core] locking/ww_mutex: Add kselftests for ww_mutex stress

Commit-ID: 2a0c11282881875dc44f166a20eedf0d866dd0ef Gitweb: http://git.kernel.org/tip/2a0c11282881875dc44f166a20eedf0d866dd0ef Author: Chris Wilson AuthorDate: Thu, 1 Dec 2016 11:47:10 + Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:37:17 +0100 locking/ww_mutex: Add kselft

[tip:locking/core] locking/ww_mutex: Add kselftests for resolving ww_mutex cyclic deadlocks

Commit-ID: d1b42b800e5d09dcee52812b4396aca3a3696ba9 Gitweb: http://git.kernel.org/tip/d1b42b800e5d09dcee52812b4396aca3a3696ba9 Author: Chris Wilson AuthorDate: Thu, 1 Dec 2016 11:47:09 + Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:37:16 +0100 locking/ww_mutex: Add kselft

[tip:locking/core] locking/ww_mutex: Add ww_mutex to tools/testing/selftests

Commit-ID: 2b0b211134a65401ed874ce0d5d48844f4f6f341 Gitweb: http://git.kernel.org/tip/2b0b211134a65401ed874ce0d5d48844f4f6f341 Author: Chris Wilson AuthorDate: Thu, 1 Dec 2016 11:47:11 + Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:37:17 +0100 locking/ww_mutex: Add ww_mut

Re: [PATCHv2 1/2] iio: Documentation: Add proximity unit

On 11/01/17 15:51, Enric Balletbo i Serra wrote: > To follow iio guidelines Where possible we stick to the raw SI unit, so > specify meters for proximity. > > Signed-off-by: Enric Balletbo i Serra Please remember to add a change log to later versions of patch sets. Saves reviewers who typically h

Re: [PATCH] iio: magnetometer: ak8974: remove redundant zero timeout check

On 11/01/17 23:11, Linus Walleij wrote: > On Wed, Jan 11, 2017 at 6:49 PM, Colin King wrote: > >> From: Colin Ian King >> >> At the end of the delay loop timeout will always be zero >> and hence the check for !timeout will always be true. Remove >> the redundant check and the redundant return 0

Re: [PATCH] x86/platform/UV: Clean up the UV APIC code

On Sat, 2017-01-14 at 09:26 +0100, Ingo Molnar wrote: > * Ingo Molnar wrote: [] > In particular the random line breaks, apparently to pacify checkpatch, were > horribly widespread. I just made the lines longer - that's still more readable > than the multi-line horror that was there before. [] > ar

Re: [PATCHv2 2/2] iio: cros_ec_light_prox: add ChromeOS EC Light and Proximity Sensors

On 11/01/17 15:51, Enric Balletbo i Serra wrote: > From: Gwendal Grignou > > Handle Light and Proximity sensors presented by the ChromeOS EC Sensor hub. > Creates an IIO device for each functions. > > Signed-off-by: Gwendal Grignou > Signed-off-by: Guenter Roeck > Signed-off-by: Enric Balletbo

Re: sysfs deferred_probe attribute

On Thu, Jan 12, 2017 at 06:26:11PM +, Ben Hutchings wrote: > On Thu, 2017-01-12 at 18:41 +0100, Greg Kroah-Hartman wrote: > > On Thu, Jan 12, 2017 at 11:27:01AM -0600, Rob Herring wrote: > > > I just noticed that we have a new device attribute 'deferred_probe' > > > added in 4.10 with this comm

Re: [PATCH 2/9] slab: remove synchronous rcu_barrier() call in memcg cache release path

Hello Tejun, Thanks a lot for looking into this issue as it seems to affect a lot of users! On Sat, Jan 14, 2017 at 12:54:42AM -0500, Tejun Heo wrote: > This patch updates the cache release path so that it simply uses > call_rcu() instead of the synchronous rcu_barrier() + custom batching. > This

Re: 4.9.0 regression in pipe-backed iov_iter with systemd-nspawn

at 22:50 on Fri 13-Jan-2017 Al Viro (v...@zeniv.linux.org.uk) wrote: > Or, even better, we can get rid of all wraparound-related crap if we > calculate the final value of pipe->nrbufs and watch for _that_ as > loop condition: > > diff --git a/lib/iov_iter.c b/lib/iov_iter.c > index 25f572303801..

Re: [PATCH 3/9] slab: simplify shutdown_memcg_caches()

On Sat, Jan 14, 2017 at 12:54:43AM -0500, Tejun Heo wrote: > shutdown_memcg_caches() shuts down all memcg caches associated with a > root cache. It first walks the index table clearing and shutting down > each entry and then shuts down the ones on > root_cache->memcg_params.list. As active caches

Re: [PATCH 4/9] slab: reorganize memcg_cache_params

On Sat, Jan 14, 2017 at 12:54:44AM -0500, Tejun Heo wrote: > We're gonna change how memcg caches are iterated. In preparation, > clean up and reorganize memcg_cache_params. > > * The shared ->list is replaced by ->children in root and > ->children_node in children. > > * ->is_root_cache is rem

Re: [PATCH 5/9] slab: link memcg kmem_caches on their associated memory cgroup

On Sat, Jan 14, 2017 at 12:54:45AM -0500, Tejun Heo wrote: > With kmem cgroup support enabled, kmem_caches can be created and > destroyed frequently and a great number of near empty kmem_caches can > accumulate if there are a lot of transient cgroups and the system is > not under memory pressure.

Re: [PATCH 6/9] slab: don't put memcg caches on slab_caches list

On Sat, Jan 14, 2017 at 12:54:46AM -0500, Tejun Heo wrote: > With kmem cgroup support enabled, kmem_caches can be created and > destroyed frequently and a great number of near empty kmem_caches can > accumulate if there are a lot of transient cgroups and the system is > not under memory pressure.

Re: [PATCH 7/9] slab: introduce __kmemcg_cache_deactivate()

On Sat, Jan 14, 2017 at 12:54:47AM -0500, Tejun Heo wrote: > __kmem_cache_shrink() is called with %true @deactivate only for memcg > caches. Remove @deactivate from __kmem_cache_shrink() and introduce > __kmemcg_cache_deactivate() instead. Each memcg-supporting allocator > should implement it and

Re: [PATCH] can: Fix kernel panic at security_sock_rcv_skb

Hello Eric, On 01/14/2017 04:43 AM, Liu Shuo wrote: On Thu 12.Jan'17 at 17:33:38 +0100, Oliver Hartkopp wrote: On 01/12/2017 02:01 PM, Eric Dumazet wrote: The main problem seems that the sockets themselves are not RCU protected. If CAN uses RCU for delivery, then sockets should be freed onl

Re: [PATCH 8/9] slab: remove synchronous synchronize_sched() from memcg cache deactivation path

On Sat, Jan 14, 2017 at 12:54:48AM -0500, Tejun Heo wrote: > With kmem cgroup support enabled, kmem_caches can be created and > destroyed frequently and a great number of near empty kmem_caches can > accumulate if there are a lot of transient cgroups and the system is > not under memory pressure.

Re: [PATCH 9/9] slab: remove slub sysfs interface files early for empty memcg caches

On Sat, Jan 14, 2017 at 12:54:49AM -0500, Tejun Heo wrote: > With kmem cgroup support enabled, kmem_caches can be created and > destroyed frequently and a great number of near empty kmem_caches can > accumulate if there are a lot of transient cgroups and the system is > not under memory pressure.

[PATCH 1/2] ns: Allow ns_entries to have custom symlink content

Make possible to have link content prefix yyy different from the link name xxx: $ readlink /proc/[pid]/ns/xxx yyy:[4026531838] This will be used in next patch. Signed-off-by: Kirill Tkhai --- fs/nsfs.c |4 +++- include/linux/proc_ns.h |1 + 2 files changed, 4 insertions(+

Re: [tip:sched/core] locking/mutex, sched/wait: Add mutex_lock_io()

On Sat, 2017-01-14 at 04:50 -0800, tip-bot for Tejun Heo wrote: > diff --git a/include/linux/mutex.h b/include/linux/mutex.h > index b97870f..980ba16 100644 > --- a/include/linux/mutex.h > +++ b/include/linux/mutex.h > @@ -171,11 +173,13 @@ do {

[PATCH 2/2] pidns: Expose task pid_ns_for_children to userspace

For correct checkpointing/restoring of a task from userspace it's need to know the task's pid_ns_for_children. Currently, there is no a sane way to do that (the only possible trick is to force the task create a new child and to analize the child's /proc/[pid]/ns/pid link, that is performance-stupid

[BISECT] ARM build errors on GCC v6.2 (crypto: arm/aes - replace scalar AES cipher)

Hi, allyesconfig and multi_v7_defconfig fail to build on recent linux-next on GCC 6.2.0. Errors: ../arch/arm/crypto/aes-cipher-core.S: Assembler messages: ../arch/arm/crypto/aes-cipher-core.S:21: Error: selected processor does not support `tt .req ip' in ARM mode ../arch/arm/crypto/aes-cipher-co

Re: [PATCH 2/9] slab: remove synchronous rcu_barrier() call in memcg cache release path

Hello, Vladimir. On Sat, Jan 14, 2017 at 04:19:39PM +0300, Vladimir Davydov wrote: > On Sat, Jan 14, 2017 at 12:54:42AM -0500, Tejun Heo wrote: > > This patch updates the cache release path so that it simply uses > > call_rcu() instead of the synchronous rcu_barrier() + custom batching. > > This d

Re: [BISECT] ARM build errors on GCC v6.2 (crypto: arm/aes - replace scalar AES cipher)

On 14 January 2017 at 14:24, Krzysztof Kozlowski wrote: > Hi, > > allyesconfig and multi_v7_defconfig fail to build on recent linux-next > on GCC 6.2.0. > > Errors: > ../arch/arm/crypto/aes-cipher-core.S: Assembler messages: > ../arch/arm/crypto/aes-cipher-core.S:21: Error: selected processor does

Re: [patch 3/3] PTP: add kvm PTP driver

On Fri, Jan 13, 2017 at 04:56:58PM +0100, Radim Krcmar wrote: > > +static int __init ptp_kvm_init(void) > > +{ > > + if (!kvm_para_available()) > > + return -ENODEV; > > + > > + kvm_ptp_clock.caps = ptp_kvm_caps; > > + > > + kvm_ptp_clock.ptp_clock = ptp_clock_register(&kvm_ptp_cloc

Re: [PATCH 3/9] slab: simplify shutdown_memcg_caches()

On Sat, Jan 14, 2017 at 04:27:22PM +0300, Vladimir Davydov wrote: > > -* Second, shutdown all caches left from memory cgroups that are now > > -* offline. > > +* Shutdown all caches. > > */ > > list_for_each_entry_safe(c, c2, &s->memcg_params.list, > >

Re: [PATCH 6/9] slab: don't put memcg caches on slab_caches list

On Sat, Jan 14, 2017 at 04:39:18PM +0300, Vladimir Davydov wrote: > IIRC the slab_caches list is also used on cpu/mem online/offline, so you > have to patch those places to ensure that memcg caches get updated too. > Other than that the patch looks good to me. Right, will update. Thanks! -- tej

Re: [PATCH 7/9] slab: introduce __kmemcg_cache_deactivate()

On Sat, Jan 14, 2017 at 04:42:11PM +0300, Vladimir Davydov wrote: > > +#if defined(CONFIG_MEMCG) && !defined(CONFIG_SLOB) > > +void __kmemcg_cache_deactivate(struct kmem_cache *s); > > +#endif > > nit: ifdef is not necessary Will drop, thanks. -- tejun

Re: [PATCH 3/9] slab: simplify shutdown_memcg_caches()

On Sat, Jan 14, 2017 at 10:38:01AM -0500, Tejun Heo wrote: > On Sat, Jan 14, 2017 at 04:27:22PM +0300, Vladimir Davydov wrote: > > > - * Second, shutdown all caches left from memory cgroups that are now > > > - * offline. > > > + * Shutdown all caches. > > >*/ > > > list_for_each_entry_saf

Re: [PATCH] radix-tree: Fix private list warnings

On Thu, Jan 12, 2017 at 05:28:23PM -0800, Matthew Wilcox wrote: > From: Matthew Wilcox > > The newly introduced warning in radix_tree_free_nodes() was testing the > wrong variable; it should have been 'old' instead of 'node'. Rather > than replace that one instance, I noticed that we can simply

Re: [tip:sched/core] locking/mutex, sched/wait: Add mutex_lock_io()

* Mike Galbraith wrote: > On Sat, 2017-01-14 at 04:50 -0800, tip-bot for Tejun Heo wrote: > > > diff --git a/include/linux/mutex.h b/include/linux/mutex.h > > index b97870f..980ba16 100644 > > --- a/include/linux/mutex.h > > +++ b/include/linux/mutex.h > > > @@ -171,11 +173,13 @@ do {

Re: [PATCH v2 5/6] arm: dts: mt2701: Add ethernet device node.

Hi John, the watchdog driver should just be the driver that includes reset functions called from driver and then send reset signal to abnormal hw.. however luckily ETHDMA_RST provided from watchdog is not required and even actually the latest driver didn't refer to the property no longer. So i w

Re: [patch v2] mm, memcg: do not retry precharge charges

On Fri, Jan 13, 2017 at 02:09:53AM -0800, David Rientjes wrote: > When memory.move_charge_at_immigrate is enabled and precharges are > depleted during move, mem_cgroup_move_charge_pte_range() will attempt to > increase the size of the precharge. > > Prevent precharges from ever looping by setting

Re: Fixing tools using UAPI headers?

On 14/01/17 00:24, Laura Abbott wrote: > Hi, > > I submitted https://marc.info/?l=linux-kernel&m=147343473231192&w=2 > a while ago and it was suggested postponing any discussion until > after ksummit > (https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2016-September/003829.html) > Did

Re: 4.9.0 regression in pipe-backed iov_iter with systemd-nspawn

at 13:16 on Sat 14-Jan-2017 Alan J. Wylie (a...@wylie.me.uk) wrote: > I'll run this for a bit, then apply it to my workstation (which I'm > rather fond of) and make sure there are no new regressions. Looking good. -- Alan J. Wylie http://www.wylie.me.uk/

Re: [PATCH] mm, vmscan: do not count freed pages as PGDEACTIVATE

On Thu, Jan 12, 2017 at 10:12:21PM +0100, Michal Hocko wrote: > From: Michal Hocko > > PGDEACTIVATE represents the number of pages moved from the active list > to the inactive list. At least this sounds like the original motivation > of the counter. move_active_pages_to_lru, however, counts pages

Re: [PATCH][V2] pinctrl: ti-iodelay: remove redundant pin < 0 check on unsigned int

On 01/13/2017 03:06 PM, Colin King wrote: From: Colin Ian King pin is an unsigned int and therefore can never be < 0 so this check is redundant. Remove the check and the associated dev_err error message. Fixes CoverityScan CID#1396438 ("Unsigned compared against 0") Signed-off-by: Colin Ian K

Re: [PATCH v4 0/5] thermal: fixes the rockchip thermal

Folks, On Wed, Jan 04, 2017 at 12:30:40AM +0800, ayaka wrote: > > > On 01/03/2017 09:13 AM, Randy Li wrote: > > > > > >On 01/03/2017 09:02 AM, Caesar Wang wrote: > >> > >>在 2017年01月03日 07:57, Randy Li 写道: > >>> > >>>On 01/02/2017 09:16 PM, Caesar Wang wrote: > 在 2016年12月31日 00:11, ayaka 写道:

[PATCH] drivers: staging: rts5208: fix endianness handling

'cb' and 'sgb' were assigned __le values but were not marked as such, this fixes the following sparse warnings: drivers/staging/rts5208/rtsx_transport.c:220:34: warning: incorrect type in assignment (different base types) drivers/staging/rts5208/rtsx_transport.c:220:34:expected unsigned int

Re: [PATCH] cxgb4: Remove redundant memset before memcpy

From: Shyam Saini Date: Sat, 14 Jan 2017 06:47:40 +0530 > The region set by the call to memset, immediately overwritten by > the subsequent call to memcpy and thus makes the memset redundant. > > Also remove the memset((&info, 0, sizeof(info)) on line 398 because > info is memcpy()'ed to before

Re: [PATCH] can: Fix kernel panic at security_sock_rcv_skb

On Sat, 2017-01-14 at 14:53 +0100, Oliver Hartkopp wrote: > Hello Eric, > > On 01/14/2017 04:43 AM, Liu Shuo wrote: > > On Thu 12.Jan'17 at 17:33:38 +0100, Oliver Hartkopp wrote: > >> On 01/12/2017 02:01 PM, Eric Dumazet wrote: > > >>> The main problem seems that the sockets themselves are not RC

Re: [PATCH v2 2/2] iio: distance: srf08: add IIO driver for us ranger

Hi Jonathan, see comments below. Andreas Jonathan Cameron schrieb am Sat, 14. Jan 12:17: > On 10/01/17 18:48, Andreas Klinger wrote: > > This is the IIO driver for devantech srf08 ultrasonic ranger which can be > > used to measure the distances to an object. > > > > The sensor supports I2C wi

Re: [PATCH 1/3] DT/bindings: Add bindings for TI ADS7950 A/DC chips

On 01/14/2017 06:53 AM, Jonathan Cameron wrote: On 11/01/17 17:52, David Lechner wrote: This adds device tree bindings for the TI ADS7950 family of A/DC chips. Signed-off-by: David Lechner This is in of itself good, but we may need to have some deprecated elements to continue supporting what

Re: 4.9.0 regression in pipe-backed iov_iter with systemd-nspawn

On Sat, Jan 14, 2017 at 8:29 AM, Alan J. Wylie wrote: > at 13:16 on Sat 14-Jan-2017 Alan J. Wylie (a...@wylie.me.uk) wrote: > >> I'll run this for a bit, then apply it to my workstation (which I'm >> rather fond of) and make sure there are no new regressions. > > Looking good. Thanks for the pinp

Re: [PATCH 2/3] iio: adc: ti-ads7950: Drop "ti-" prefix from module name

On 01/14/2017 06:49 AM, Jonathan Cameron wrote: On 11/01/17 17:52, David Lechner wrote: This drops the "ti-" prefix from the module name. It makes the module name consistent with other iio ti-ads* drivers and it makes the driver work with device tree (the spi subsystem drops the "ti," prefix whe

Re: [PATCH 3/3] iio: adc: ti-ads7950: Change regulator matching string to "vref"

On 01/14/2017 06:52 AM, Jonathan Cameron wrote: On 11/01/17 17:52, David Lechner wrote: This changes the reference voltage regulator matching string from "refin" to "vref". This is to be consistent with other A/DC chips that also use "vref-supply" in their device tree bindings. Signed-off-by: D

[PATCH] drivers: staging: rtl8188eu: include: Fix semicolon after macro definition

fixed a trailing semicolon after macro definition Signed-off-by: Kartikey Singh --- drivers/staging/rtl8188eu/include/basic_types.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/rtl8188eu/include/basic_types.h b/drivers/staging/rtl8188eu/include/basic_types

Re: [BISECT] ARM build errors on GCC v6.2 (crypto: arm/aes - replace scalar AES cipher)

On Sat, Jan 14, 2017 at 04:24:35PM +0200, Krzysztof Kozlowski wrote: > Hi, > > allyesconfig and multi_v7_defconfig fail to build on recent linux-next > on GCC 6.2.0. > > Errors: > ../arch/arm/crypto/aes-cipher-core.S: Assembler messages: > ../arch/arm/crypto/aes-cipher-core.S:21: Error: selected

[PATCH] drivers: staging: rtl8188eu: include: wifi: Unnecessary do-while removed from macro

do while loop removed from single statement macro Signed-off-by: Kartikey Singh --- drivers/staging/rtl8188eu/include/wifi.h | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/staging/rtl8188eu/include/wifi.h b/drivers/staging/rtl8188eu/include/wifi.h index 9e08e68..

Re: [PATCH] net: korina: use new api ethtool_{get|set}_link_ksettings

On 01/14/2017 03:33 AM, Philippe Reynes wrote: > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > Signed-off-by: Philippe Reynes Reviewed-by: Florian Fainelli -- Florian

Re: [PATCH] drivers: staging: rtl8188eu: include: wifi: Unnecessary do-while removed from macro

On Sat, Jan 14, 2017 at 11:53:36PM +0530, Kartikey Singh wrote: > do while loop removed from single statement macro > > Signed-off-by: Kartikey Singh > --- > drivers/staging/rtl8188eu/include/wifi.h | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > > diff --git a/drivers/staging/rtl8

Re: [PATCH v3] tty: serial: 8250: add MOXA Smartio MUE boards support

Hi, I am currently reading misc stuff in serial/8250/. What is the reason why 8250_moxa ever exists? I mean, it seems that 8250_pci module does the same as 8250_moxa does. 2016-03-19 12:07 GMT+03:00 Mathieu OTHACEHE : > Hi, > > Sorry about late reply. > > No I haven't planned to do it soon. Your

Re: [PATCH] drivers: staging: rtl8188eu: include: Fix semicolon after macro definition

On Sat, Jan 14, 2017 at 11:47:56PM +0530, Kartikey Singh wrote: > fixed a trailing semicolon after macro definition > > Signed-off-by: Kartikey Singh > --- > drivers/staging/rtl8188eu/include/basic_types.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/staging/

[PATCH 3/8] slab: reorganize memcg_cache_params

We're gonna change how memcg caches are iterated. In preparation, clean up and reorganize memcg_cache_params. * The shared ->list is replaced by ->children in root and ->children_node in children. * ->is_root_cache is removed. Instead ->root_cache is moved out of the child union and now use

[PATCH 7/8] slab: remove synchronous synchronize_sched() from memcg cache deactivation path

With kmem cgroup support enabled, kmem_caches can be created and destroyed frequently and a great number of near empty kmem_caches can accumulate if there are a lot of transient cgroups and the system is not under memory pressure. When memory reclaim starts under such conditions, it can lead to co

[PATCH 8/8] slab: remove slub sysfs interface files early for empty memcg caches

With kmem cgroup support enabled, kmem_caches can be created and destroyed frequently and a great number of near empty kmem_caches can accumulate if there are a lot of transient cgroups and the system is not under memory pressure. When memory reclaim starts under such conditions, it can lead to co

[PATCH 5/8] slab: implement slab_root_caches list

With kmem cgroup support enabled, kmem_caches can be created and destroyed frequently and a great number of near empty kmem_caches can accumulate if there are a lot of transient cgroups and the system is not under memory pressure. When memory reclaim starts under such conditions, it can lead to co

[PATCH 4/8] slab: link memcg kmem_caches on their associated memory cgroup

With kmem cgroup support enabled, kmem_caches can be created and destroyed frequently and a great number of near empty kmem_caches can accumulate if there are a lot of transient cgroups and the system is not under memory pressure. When memory reclaim starts under such conditions, it can lead to co

[PATCH 6/8] slab: introduce __kmemcg_cache_deactivate()

__kmem_cache_shrink() is called with %true @deactivate only for memcg caches. Remove @deactivate from __kmem_cache_shrink() and introduce __kmemcg_cache_deactivate() instead. Each memcg-supporting allocator should implement it and it should deactivate and drain the cache. This is to allow memcg

[PATCH 2/8] slab: remove synchronous rcu_barrier() call in memcg cache release path

With kmem cgroup support enabled, kmem_caches can be created and destroyed frequently and a great number of near empty kmem_caches can accumulate if there are a lot of transient cgroups and the system is not under memory pressure. When memory reclaim starts under such conditions, it can lead to co

Re: [BISECT] ARM build errors on GCC v6.2 (crypto: arm/aes - replace scalar AES cipher)

On Sat, Jan 14, 2017 at 06:20:12PM +, Russell King - ARM Linux wrote: > On Sat, Jan 14, 2017 at 04:24:35PM +0200, Krzysztof Kozlowski wrote: > > Hi, > > > > allyesconfig and multi_v7_defconfig fail to build on recent linux-next > > on GCC 6.2.0. > > > > Errors: > > ../arch/arm/crypto/aes-ciph

[PATCH 1/8] Revert "slub: move synchronize_sched out of slab_mutex on shrink"

This reverts commit 89e364db71fb5e7fc8d93228152abfa67daf35fa. With kmem cgroup support enabled, kmem_caches can be created and destroyed frequently and a great number of near empty kmem_caches can accumulate if there are a lot of transient cgroups and the system is not under memory pressure. When

[PATCHSET v2] slab: make memcg slab destruction scalable

This is v2. Changes from the last version[L] are * 0002-slab-remove-synchronous-rcu_barrier-call-in-memcg-ca.patch was incorrect and dropped. * 0006-slab-don-t-put-memcg-caches-on-slab_caches-list.patch incorrectly converted places which needed to walk all caches. Replaced with 0005-slab-i

Re: [PATCH net-next v2 05/10] drivers: base: Add device_find_class()

On 01/13/2017 02:55 AM, David Laight wrote: > From: Florian Fainelli >> Sent: 12 January 2017 22:51 >> On 01/12/2017 01:21 PM, David Miller wrote: >>> From: Florian Fainelli >>> Date: Wed, 11 Jan 2017 19:41:16 -0800 >>> Add a helper function to lookup a device reference given a class name.

[PATCH] reset: uniphier: add compatible string for LD11 SD-reset block

The LD11 SoC is equipped with not only MIO-reset but also SD-reset for controlling RST_n pin of the eMMC device. Update the binding document and remove unneeded "." from each line in itemization. Signed-off-by: Masahiro Yamada --- .../devicetree/bindings/reset/uniphier-reset.txt | 47 +++

Re: [PATCH net-next v2 08/10] net: dsa: Add support for platform data

On 01/13/2017 02:37 PM, Florian Fainelli wrote: > On 01/13/2017 06:04 AM, Andrew Lunn wrote: >>> index cd91070b5467..d326fc4afad7 100644 >>> --- a/net/dsa/dsa2.c >>> +++ b/net/dsa/dsa2.c >>> @@ -81,17 +81,23 @@ static void dsa_dst_del_ds(struct dsa_switch_tree *dst, >>> >>> static bool dsa_port_

Re: [PATCH v2 1/3] Input: pwm-beeper: suppress error message on probe defer

On Wed, Jan 11, 2017 at 02:01:59PM -0600, David Lechner wrote: > This suppress printing an error message when pwm_get returns -EPROBE_DEFER. > Otherwise you get a bunch of noise in the kernel log. > > Signed-off-by: David Lechner > --- > drivers/input/misc/pwm-beeper.c | 7 --- > 1 file chan

Re: [PATCH v2 3/3] Input: pwm-beeper: add optional amplifier regulator

On Wed, Jan 11, 2017 at 02:02:01PM -0600, David Lechner wrote: > This adds an optional regulator to the pwm-beeper device. This regulator > acts as an amplifier. The amplifier is only enabled while beeping in order > to reduce power consumption. > > Tested on LEGO MINDSTORMS EV3, which has a speak

<    1   2   3   4   >