Re: 4.11.0-rc1 boot resulted in WARNING: CPU: 14 PID: 1722 at fs/sysfs/dir.c:31 .sysfs_warn_dup+0x78/0xb0

On Tue, Mar 07, 2017 at 10:01:04PM +0530, Abdul Haleem wrote: > > Hi, > > Today's mainline (4.11.0-rc1) booted with warnings on Power7 LPAR. > > Issue is not reproducible all the time. > > traces: > > Found device VDASD 5. > Mounting /home... > Reached target Swap. > Found device

Re: 4.11.0-rc1 boot resulted in WARNING: CPU: 14 PID: 1722 at fs/sysfs/dir.c:31 .sysfs_warn_dup+0x78/0xb0

On Tue, Mar 07, 2017 at 10:01:04PM +0530, Abdul Haleem wrote: > > Hi, > > Today's mainline (4.11.0-rc1) booted with warnings on Power7 LPAR. > > Issue is not reproducible all the time. > > traces: > > Found device VDASD 5. > Mounting /home... > Reached target Swap. > Found device

[PATCH 19/26] IB/ocrdma: Improve another size determination in ocrdma_alloc_mr()

From: Markus Elfring Date: Wed, 8 Mar 2017 09:54:42 +0100 Replace the specification of a data type by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 19/26] IB/ocrdma: Improve another size determination in ocrdma_alloc_mr()

From: Markus Elfring Date: Wed, 8 Mar 2017 09:54:42 +0100 Replace the specification of a data type by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. Signed-off-by: Markus

Re: [PATCH -mm -v6 1/9] mm, swap: Make swap cluster size same of THP size on x86_64

On Wed, Mar 08, 2017 at 03:26:05PM +0800, Huang, Ying wrote: > In this patch, the size of the swap cluster is changed to that of the > THP (Transparent Huge Page) on x86_64 architecture (512). This is for > the THP swap support on x86_64. Where one swap cluster will be used to > hold the

Re: [PATCH -mm -v6 1/9] mm, swap: Make swap cluster size same of THP size on x86_64

On Wed, Mar 08, 2017 at 03:26:05PM +0800, Huang, Ying wrote: > In this patch, the size of the swap cluster is changed to that of the > THP (Transparent Huge Page) on x86_64 architecture (512). This is for > the THP swap support on x86_64. Where one swap cluster will be used to > hold the

Re: [PATCH 2/2] perf probe: Remove stale func add_perf_probe_events

Thanks Masami for the review, On Wednesday 08 March 2017 03:13 PM, Masami Hiramatsu wrote: > On Wed, 8 Mar 2017 12:29:08 +0530 > Ravi Bangoria wrote: > >> I don't see any user of this function. This function was being copied >> to tools/perf/builtin-probe.c by

Re: [PATCH 2/2] perf probe: Remove stale func add_perf_probe_events

Thanks Masami for the review, On Wednesday 08 March 2017 03:13 PM, Masami Hiramatsu wrote: > On Wed, 8 Mar 2017 12:29:08 +0530 > Ravi Bangoria wrote: > >> I don't see any user of this function. This function was being copied >> to tools/perf/builtin-probe.c by commit b02137cc6550 ("perf probe:

[PATCH 12/26] IB/ocrdma: Adjust ten checks for null pointers

From: Markus Elfring Date: Tue, 7 Mar 2017 21:32:22 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl“ pointed information out like the following. Comparison to NULL could be written !… Thus

[PATCH 12/26] IB/ocrdma: Adjust ten checks for null pointers

From: Markus Elfring Date: Tue, 7 Mar 2017 21:32:22 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl“ pointed information out like the following. Comparison to NULL could be written !… Thus fix the affected source code

Re: Applied "spi: davinci: enable DMA when channels are defined in DT" to the spi tree

On Wed, Mar 08, 2017 at 11:35:02AM +0100, Frode Isaksen wrote: > To avoid data corruption issues with UBIFS volume over SPI NOR, DMA should > not be used for vmalloc'ed buffers. The 5'th patch in my series fixes that: It's best to always try to ensure that your patch serieses are bisectable...

Re: Applied "spi: davinci: enable DMA when channels are defined in DT" to the spi tree

On Wed, Mar 08, 2017 at 11:35:02AM +0100, Frode Isaksen wrote: > To avoid data corruption issues with UBIFS volume over SPI NOR, DMA should > not be used for vmalloc'ed buffers. The 5'th patch in my series fixes that: It's best to always try to ensure that your patch serieses are bisectable...

Re: [PATCH] mm: move pcp and lru-pcp drainging into single wq

On Wed 08-03-17 20:50:45, Tetsuo Handa wrote: > Michal Hocko wrote: > > On Tue 07-03-17 22:50:48, Tetsuo Handa wrote: > > > Michal Hocko wrote: > > > > From: Michal Hocko > > > > > > > > We currently have 2 specific WQ_RECLAIM workqueues in the mm code. > > > > vmstat_wq for

Re: [PATCH] mm: move pcp and lru-pcp drainging into single wq

On Wed 08-03-17 20:50:45, Tetsuo Handa wrote: > Michal Hocko wrote: > > On Tue 07-03-17 22:50:48, Tetsuo Handa wrote: > > > Michal Hocko wrote: > > > > From: Michal Hocko > > > > > > > > We currently have 2 specific WQ_RECLAIM workqueues in the mm code. > > > > vmstat_wq for updating pcp stats

Re: [RFC PATCH 3/4] xfs: map KM_MAYFAIL to __GFP_RETRY_MAYFAIL

On Wed 08-03-17 20:23:37, Tetsuo Handa wrote: > On 2017/03/08 0:48, Michal Hocko wrote: > > From: Michal Hocko > > > > KM_MAYFAIL didn't have any suitable GFP_FOO counterpart until recently > > so it relied on the default page allocator behavior for the given set > > of flags.

Re: [RFC PATCH 3/4] xfs: map KM_MAYFAIL to __GFP_RETRY_MAYFAIL

On Wed 08-03-17 20:23:37, Tetsuo Handa wrote: > On 2017/03/08 0:48, Michal Hocko wrote: > > From: Michal Hocko > > > > KM_MAYFAIL didn't have any suitable GFP_FOO counterpart until recently > > so it relied on the default page allocator behavior for the given set > > of flags. This means that

[PATCH 13/26] IB/ocrdma: Use kcalloc() in ocrdma_alloc_resources()

From: Markus Elfring Date: Tue, 7 Mar 2017 21:55:42 +0100 * Multiplications for the size determination of memory allocations indicated that array data structures should be processed. Thus reuse the corresponding function "kcalloc". This issue was detected by

[PATCH 09/26] IB/ocrdma: Improve another size determination in ocrdma_mq_cq_handler()

From: Markus Elfring Date: Tue, 7 Mar 2017 20:20:45 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 13/26] IB/ocrdma: Use kcalloc() in ocrdma_alloc_resources()

From: Markus Elfring Date: Tue, 7 Mar 2017 21:55:42 +0100 * Multiplications for the size determination of memory allocations indicated that array data structures should be processed. Thus reuse the corresponding function "kcalloc". This issue was detected by using the Coccinelle software.

[PATCH 09/26] IB/ocrdma: Improve another size determination in ocrdma_mq_cq_handler()

From: Markus Elfring Date: Tue, 7 Mar 2017 20:20:45 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. Signed-off-by:

[PATCH 08/26] IB/ocrdma: Improve size determinations in ocrdma_mbx_rdma_stats()

From: Markus Elfring Date: Tue, 7 Mar 2017 20:16:16 +0100 Replace the specification of two data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determinations a bit safer according to the Linux coding

Re: [PATCH] livepatch: make klp_mutex proper part of API

On Wed, 8 Mar 2017, Josh Poimboeuf wrote: > On Wed, Mar 08, 2017 at 10:16:00AM +0100, Jiri Kosina wrote: > > From: Jiri Kosina > > > > klp_mutex is shared between core.c and transition.c, and as such would > > rather be properly located in livepatch.h so that we don't have to

Re: [PATCH] livepatch: make klp_mutex proper part of API

On Wed, 8 Mar 2017, Josh Poimboeuf wrote: > On Wed, Mar 08, 2017 at 10:16:00AM +0100, Jiri Kosina wrote: > > From: Jiri Kosina > > > > klp_mutex is shared between core.c and transition.c, and as such would > > rather be properly located in livepatch.h so that we don't have to play > >

[PATCH 08/26] IB/ocrdma: Improve size determinations in ocrdma_mbx_rdma_stats()

From: Markus Elfring Date: Tue, 7 Mar 2017 20:16:16 +0100 Replace the specification of two data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determinations a bit safer according to the Linux coding style convention. Signed-off-by:

[PATCH 11/26] IB/ocrdma: Delete unnecessary braces

From: Markus Elfring Date: Tue, 7 Mar 2017 21:12:56 +0100 Do not use curly brackets at some source code places where a single statement should be sufficient. Signed-off-by: Markus Elfring ---

[PATCH 11/26] IB/ocrdma: Delete unnecessary braces

From: Markus Elfring Date: Tue, 7 Mar 2017 21:12:56 +0100 Do not use curly brackets at some source code places where a single statement should be sufficient. Signed-off-by: Markus Elfring --- drivers/infiniband/hw/ocrdma/ocrdma_hw.c | 17 - 1 file changed, 8 insertions(+), 9

Re: [RFC PATCH] sched/wait: Introduce new, more compact wait_event*() primitives

* Ingo Molnar wrote: > You can find the latest (WIP, frequently rebased) version in: > > git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.sched/core > > The first 10 patches reshape the waitqueue code to be more hackable (to me!), > because I kept bumping

Re: [RFC PATCH] sched/wait: Introduce new, more compact wait_event*() primitives

* Ingo Molnar wrote: > You can find the latest (WIP, frequently rebased) version in: > > git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.sched/core > > The first 10 patches reshape the waitqueue code to be more hackable (to me!), > because I kept bumping into confusing

[PATCH 10/26] IB/ocrdma: Improve another size determination in ocrdma_init_emb_mqe()

From: Markus Elfring Date: Tue, 7 Mar 2017 20:33:29 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

Re: [PATCH v3 03/09] iommu/ipmmu-vmsa: Enable multi context support

On 08/03/17 11:01, Magnus Damm wrote: > From: Magnus Damm > > Add support for up to 8 contexts. Each context is mapped to one > domain. One domain is assigned one or more slave devices. Contexts > are allocated dynamically and slave devices are grouped together >

[PATCH 10/26] IB/ocrdma: Improve another size determination in ocrdma_init_emb_mqe()

From: Markus Elfring Date: Tue, 7 Mar 2017 20:33:29 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. Signed-off-by:

Re: [PATCH v3 03/09] iommu/ipmmu-vmsa: Enable multi context support

On 08/03/17 11:01, Magnus Damm wrote: > From: Magnus Damm > > Add support for up to 8 contexts. Each context is mapped to one > domain. One domain is assigned one or more slave devices. Contexts > are allocated dynamically and slave devices are grouped together > based on which IPMMU device they

Re: [PATCH v7 01/07] iommu/ipmmu-vmsa: Remove platform data handling

On Tue, Mar 7, 2017 at 4:16 AM, Magnus Damm wrote: > From: Magnus Damm > > The IPMMU driver is using DT these days, and platform data is no longer > used by the driver. Remove unused code. > > Signed-off-by: Magnus Damm

Re: [PATCH v7 01/07] iommu/ipmmu-vmsa: Remove platform data handling

On Tue, Mar 7, 2017 at 4:16 AM, Magnus Damm wrote: > From: Magnus Damm > > The IPMMU driver is using DT these days, and platform data is no longer > used by the driver. Remove unused code. > > Signed-off-by: Magnus Damm > Reviewed-by: Laurent Pinchart > Reviewed-by: Joerg Roedel Reviewed-by:

Re: [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment

On Wed, Mar 08, 2017 at 04:45:13PM +0800, Baoquan He wrote: > -4G and -68G just a trick which makes people understand easily, still we > think kernel text mapping region is in higher addr area then vmalloc. I > personnally think. Just remove the direction: bottom-up or top-down, it will confuse

Re: [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment

On Wed, Mar 08, 2017 at 04:45:13PM +0800, Baoquan He wrote: > -4G and -68G just a trick which makes people understand easily, still we > think kernel text mapping region is in higher addr area then vmalloc. I > personnally think. Just remove the direction: bottom-up or top-down, it will confuse

Re: [PATCH] mm, vmalloc: use __GFP_HIGHMEM implicitly

On Tue 07-03-17 10:57:48, Matthew Wilcox wrote: > On Tue, Mar 07, 2017 at 10:28:41AM -0800, Matthew Wilcox wrote: > > On Tue, Mar 07, 2017 at 03:10:20PM +0100, Michal Hocko wrote: > > > This patch simply uses __GFP_HIGHMEM implicitly when allocating pages to > > > be mapped to the vmalloc space.

Re: [PATCH] mm, vmalloc: use __GFP_HIGHMEM implicitly

On Tue 07-03-17 10:57:48, Matthew Wilcox wrote: > On Tue, Mar 07, 2017 at 10:28:41AM -0800, Matthew Wilcox wrote: > > On Tue, Mar 07, 2017 at 03:10:20PM +0100, Michal Hocko wrote: > > > This patch simply uses __GFP_HIGHMEM implicitly when allocating pages to > > > be mapped to the vmalloc space.

Re: [PATCH 3/3] cpufreq: schedutil: remove redundant code from sugov_next_freq_shared()

On Wed, Mar 8, 2017 at 12:15 PM, Viresh Kumar wrote: > On 08-03-17, 11:50, Rafael J. Wysocki wrote: >> So overall, maybe you can move the flags check to >> sugov_update_shared(), so that you don't need to pass flags to >> sugov_next_freq_shared(), and then do what you did

Re: [PATCH 3/3] cpufreq: schedutil: remove redundant code from sugov_next_freq_shared()

On Wed, Mar 8, 2017 at 12:15 PM, Viresh Kumar wrote: > On 08-03-17, 11:50, Rafael J. Wysocki wrote: >> So overall, maybe you can move the flags check to >> sugov_update_shared(), so that you don't need to pass flags to >> sugov_next_freq_shared(), and then do what you did to util and max. > >

Re: [PATCH] staging: nvec: Remove unnecessary cast on void pointer

On Fri, Mar 03, 2017 at 01:45:11AM +0530, simran singhal wrote: > The following Coccinelle script was used to detect this: > > @r@ > expression x; > void* e; > type T; > identifier f; > @@ > ( > *((T *)e) > | > ((T *)x)[...] > | > ((T*)x)->f > | > - (T*) > e > ) > > Signed-off-by: simran

[PATCH 07/26] IB/ocrdma: Improve another size determination in ocrdma_mbx_get_ctrl_attribs()

From: Markus Elfring Date: Tue, 7 Mar 2017 20:07:25 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

Re: [PATCH] staging: nvec: Remove unnecessary cast on void pointer

On Fri, Mar 03, 2017 at 01:45:11AM +0530, simran singhal wrote: > The following Coccinelle script was used to detect this: > > @r@ > expression x; > void* e; > type T; > identifier f; > @@ > ( > *((T *)e) > | > ((T *)x)[...] > | > ((T*)x)->f > | > - (T*) > e > ) > > Signed-off-by: simran

[PATCH 07/26] IB/ocrdma: Improve another size determination in ocrdma_mbx_get_ctrl_attribs()

From: Markus Elfring Date: Tue, 7 Mar 2017 20:07:25 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. Signed-off-by:

Re: [PATCH 6/6] staging: comedi: Using macro DIV_ROUND_UP

On 21/02/17 18:28, simran singhal wrote: The macro DIV_ROUND_UP performs the computation (((n) + (d) - 1) /(d)). It clarifies the divisor calculations. This occurence was detected using the coccinelle script: @@ expression e1; expression e2; @@ ( - ((e1) + e2 - 1) / (e2) + DIV_ROUND_UP(e1,e2) |

Re: [PATCH 6/6] staging: comedi: Using macro DIV_ROUND_UP

On 21/02/17 18:28, simran singhal wrote: The macro DIV_ROUND_UP performs the computation (((n) + (d) - 1) /(d)). It clarifies the divisor calculations. This occurence was detected using the coccinelle script: @@ expression e1; expression e2; @@ ( - ((e1) + e2 - 1) / (e2) + DIV_ROUND_UP(e1,e2) |

Re: [Outreachy kernel] [PATCH] staging: nvec: cleanup USLEEP_RANGEcheckpatch checks

On Thu, Mar 02, 2017 at 03:57:01PM +0100, Marc Dietrich wrote: > Hi Simran, > > Am Donnerstag, 2. März 2017, 15:48:13 CET schrieb SIMRAN SINGHAL: > > On Thursday, March 2, 2017 at 8:06:40 PM UTC+5:30, Julia Lawall wrote: > > > On Thu, 2 Mar 2017, simran singhal wrote: > > > > Resolve strict

Re: [Outreachy kernel] [PATCH] staging: nvec: cleanup USLEEP_RANGEcheckpatch checks

On Thu, Mar 02, 2017 at 03:57:01PM +0100, Marc Dietrich wrote: > Hi Simran, > > Am Donnerstag, 2. März 2017, 15:48:13 CET schrieb SIMRAN SINGHAL: > > On Thursday, March 2, 2017 at 8:06:40 PM UTC+5:30, Julia Lawall wrote: > > > On Thu, 2 Mar 2017, simran singhal wrote: > > > > Resolve strict

[PATCH 06/26] IB/ocrdma: Improve another size determination in ocrdma_alloc_pd_pool()

From: Markus Elfring Date: Tue, 7 Mar 2017 19:54:38 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 06/26] IB/ocrdma: Improve another size determination in ocrdma_alloc_pd_pool()

From: Markus Elfring Date: Tue, 7 Mar 2017 19:54:38 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. Signed-off-by:

[PATCH 01/26] IB/ocrdma: Use kcalloc() in ocrdma_create_eqs()

From: Markus Elfring Date: Tue, 7 Mar 2017 17:56:45 +0100 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus reuse the corresponding function "kcalloc". This issue was

[PATCH 01/26] IB/ocrdma: Use kcalloc() in ocrdma_create_eqs()

From: Markus Elfring Date: Tue, 7 Mar 2017 17:56:45 +0100 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus reuse the corresponding function "kcalloc". This issue was detected by using the Coccinelle

[PATCH 05/26] IB/ocrdma: Improve another size determination in ocrdma_mbx_query_qp()

From: Markus Elfring Date: Tue, 7 Mar 2017 19:40:31 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 05/26] IB/ocrdma: Improve another size determination in ocrdma_mbx_query_qp()

From: Markus Elfring Date: Tue, 7 Mar 2017 19:40:31 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. Signed-off-by:

Re: blk: improve order of bio handling in generic_make_request()

On 7 March 2017 at 17:52, Mike Snitzer wrote: > > On 06.03.2017 21:18, Jens Axboe wrote: > > > I like the change, and thanks for tackling this. It's been a pending > > > issue for way too long. I do think we should squash Jack's patch > > > into the original, as it does clean

[PATCH v2 1/2] x86/efi/64: Clean up code comment about efi region

EFI allocates runtime services regions starting from EFI_VA_START, -4G, decrement to EFI_VA_END. So remove the bottom-up term to avoid confusion. Signed-off-by: Baoquan He --- arch/x86/platform/efi/efi_64.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

Re: mm: use-after-free in zap_page_range

On Fri, Mar 3, 2017 at 5:23 PM, Andrea Arcangeli wrote: > Hello Dmitry, > > On Fri, Mar 03, 2017 at 02:54:26PM +0100, Dmitry Vyukov wrote: >> The following program triggers use-after-free in zap_page_range: >>

Re: blk: improve order of bio handling in generic_make_request()

On 7 March 2017 at 17:52, Mike Snitzer wrote: > > On 06.03.2017 21:18, Jens Axboe wrote: > > > I like the change, and thanks for tackling this. It's been a pending > > > issue for way too long. I do think we should squash Jack's patch > > > into the original, as it does clean up the code nicely.

[PATCH v2 1/2] x86/efi/64: Clean up code comment about efi region

EFI allocates runtime services regions starting from EFI_VA_START, -4G, decrement to EFI_VA_END. So remove the bottom-up term to avoid confusion. Signed-off-by: Baoquan He --- arch/x86/platform/efi/efi_64.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

Re: mm: use-after-free in zap_page_range

On Fri, Mar 3, 2017 at 5:23 PM, Andrea Arcangeli wrote: > Hello Dmitry, > > On Fri, Mar 03, 2017 at 02:54:26PM +0100, Dmitry Vyukov wrote: >> The following program triggers use-after-free in zap_page_range: >>

Re: [PATCH 1/2] reset: add reset-simple to unify socfpga, stm32, and sunxi

Hi Philipp, On 03/08/2017 11:19 AM, Andre Przywara wrote: Hi, On 08/03/17 09:54, Philipp Zabel wrote: Reset operations for simple reset controllers with reset lines that can be controlled by toggling bits in (mostly) contiguous register ranges using read-modify-write cycles under a spinlock.

Re: [PATCH 1/2] reset: add reset-simple to unify socfpga, stm32, and sunxi

Hi Philipp, On 03/08/2017 11:19 AM, Andre Przywara wrote: Hi, On 08/03/17 09:54, Philipp Zabel wrote: Reset operations for simple reset controllers with reset lines that can be controlled by toggling bits in (mostly) contiguous register ranges using read-modify-write cycles under a spinlock.

Re: [PATCH stable-4.9 0/2] mm: follow up oom fixes for 32b

On Tue, Feb 28, 2017 at 04:11:06PM +0100, Michal Hocko wrote: > Hi, > later in the 4.10 release cycle it turned out that b4536f0c829c ("mm, > memcg: fix the active list aging for lowmem requests when memcg is > enabled") was not sufficient to fully close the regression introduced by > f8d1a31163fc

Re: [PATCH stable-4.9 0/2] mm: follow up oom fixes for 32b

On Tue, Feb 28, 2017 at 04:11:06PM +0100, Michal Hocko wrote: > Hi, > later in the 4.10 release cycle it turned out that b4536f0c829c ("mm, > memcg: fix the active list aging for lowmem requests when memcg is > enabled") was not sufficient to fully close the regression introduced by > f8d1a31163fc

Re: [PATCH] mm: move pcp and lru-pcp drainging into single wq

Michal Hocko wrote: > On Tue 07-03-17 22:50:48, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > From: Michal Hocko > > > > > > We currently have 2 specific WQ_RECLAIM workqueues in the mm code. > > > vmstat_wq for updating pcp stats and lru_add_drain_wq dedicated to drain > >

Re: [PATCH] mm: move pcp and lru-pcp drainging into single wq

Michal Hocko wrote: > On Tue 07-03-17 22:50:48, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > From: Michal Hocko > > > > > > We currently have 2 specific WQ_RECLAIM workqueues in the mm code. > > > vmstat_wq for updating pcp stats and lru_add_drain_wq dedicated to drain > > > per cpu lru

[PATCH 03/26] IB/ocrdma: Improve size determinations in ocrdma_mbx_get_dcbx_config()

From: Markus Elfring Date: Tue, 7 Mar 2017 19:09:20 +0100 Replace the specification of data structures by references for variables as the parameter for the operator "sizeof" to make the corresponding size determinations a bit safer according to the Linux coding

[PATCH 03/26] IB/ocrdma: Improve size determinations in ocrdma_mbx_get_dcbx_config()

From: Markus Elfring Date: Tue, 7 Mar 2017 19:09:20 +0100 Replace the specification of data structures by references for variables as the parameter for the operator "sizeof" to make the corresponding size determinations a bit safer according to the Linux coding style convention. Signed-off-by:

Re: [PATCH v7 06/07] iommu/ipmmu-vmsa: ARM and ARM64 archdata access

On 07/03/17 03:17, Magnus Damm wrote: > From: Magnus Damm > > Not all architectures have an iommu member in their archdata, so > use #ifdefs support build with COMPILE_TEST on any architecture. I have a feeling I might be repeating myself, but ipmmu_vmsa_archdata

Re: [PATCH v7 06/07] iommu/ipmmu-vmsa: ARM and ARM64 archdata access

On 07/03/17 03:17, Magnus Damm wrote: > From: Magnus Damm > > Not all architectures have an iommu member in their archdata, so > use #ifdefs support build with COMPILE_TEST on any architecture. I have a feeling I might be repeating myself, but ipmmu_vmsa_archdata looks to be trivially

Re: [PATCH] media: vpif: use a configurable i2c_adapter_id for vpif display

2017-03-07 18:12 GMT+01:00 Lad, Prabhakar : > Hi Bartosz, > > Thanks for the patch. > > On Thu, Feb 16, 2017 at 6:08 PM, Bartosz Golaszewski > wrote: >> >> The vpif display driver uses a static i2c adapter ID of 1 but on the >> da850-evm

Re: [PATCH] media: vpif: use a configurable i2c_adapter_id for vpif display

2017-03-07 18:12 GMT+01:00 Lad, Prabhakar : > Hi Bartosz, > > Thanks for the patch. > > On Thu, Feb 16, 2017 at 6:08 PM, Bartosz Golaszewski > wrote: >> >> The vpif display driver uses a static i2c adapter ID of 1 but on the >> da850-evm board in DT boot mode the i2c adapter ID is actually 0. >>

[PATCH 02/26] IB/ocrdma: Use kcalloc() in ocrdma_mbx_alloc_pd_range()

From: Markus Elfring Date: Tue, 7 Mar 2017 18:23:54 +0100 * Multiplications for the size determination of memory allocations indicated that array data structures should be processed. Thus reuse the corresponding function "kcalloc". This issue was detected by

[PATCH 02/26] IB/ocrdma: Use kcalloc() in ocrdma_mbx_alloc_pd_range()

From: Markus Elfring Date: Tue, 7 Mar 2017 18:23:54 +0100 * Multiplications for the size determination of memory allocations indicated that array data structures should be processed. Thus reuse the corresponding function "kcalloc". This issue was detected by using the Coccinelle software.

Re: [PATCH] MAINTAINERS: Remove self from Tegra maintainers

On Mon, Mar 06, 2017 at 03:11:34PM +0900, Alexandre Courbot wrote: > I have not been doing any Tegra maintainance work for a while, and this > is unlikely to change in the foreseeable future. Better reflect the > actual state of things by removing myself from the list. > > Signed-off-by:

Re: [PATCH] MAINTAINERS: Remove self from Tegra maintainers

On Mon, Mar 06, 2017 at 03:11:34PM +0900, Alexandre Courbot wrote: > I have not been doing any Tegra maintainance work for a while, and this > is unlikely to change in the foreseeable future. Better reflect the > actual state of things by removing myself from the list. > > Signed-off-by:

[PATCH] phy: phy-exynos-pcie: fix the wrong error return

When it doesn't get the blk_base's resource, it was returned the error about phy_base, not blk_base. This patch is for fixing the wrong error return about blk_base. Fixes: cf0adb8e281b ("phy: phy-exynos-pcie: Add support for Exynos PCIe PHY") Signed-off-by: Jaehoon Chung

[PATCH] phy: phy-exynos-pcie: fix the wrong error return

When it doesn't get the blk_base's resource, it was returned the error about phy_base, not blk_base. This patch is for fixing the wrong error return about blk_base. Fixes: cf0adb8e281b ("phy: phy-exynos-pcie: Add support for Exynos PCIe PHY") Signed-off-by: Jaehoon Chung ---

Re: [PATCH 1/2] reset: add reset-simple to unify socfpga, stm32, and sunxi

On Wed, 2017-03-08 at 12:05 +0100, Alexandre Torgue wrote: > Hi Philipp, > > On 03/08/2017 11:19 AM, Andre Przywara wrote: > > Hi, > > > > On 08/03/17 09:54, Philipp Zabel wrote: > >> Reset operations for simple reset controllers with reset lines that can > >> be controlled by toggling bits in

Re: [PATCH 1/2] reset: add reset-simple to unify socfpga, stm32, and sunxi

On Wed, 2017-03-08 at 12:05 +0100, Alexandre Torgue wrote: > Hi Philipp, > > On 03/08/2017 11:19 AM, Andre Przywara wrote: > > Hi, > > > > On 08/03/17 09:54, Philipp Zabel wrote: > >> Reset operations for simple reset controllers with reset lines that can > >> be controlled by toggling bits in

Re: [PATCH v3 4/6] drm: bridge: dw-hdmi: Switch to V4L bus format and encodings

On 03/07/2017 06:35 PM, Jose Abreu wrote: > Hi Neil, > > > On 07-03-2017 16:42, Neil Armstrong wrote: >> Some display pipelines can only provide non-RBG input pixels to the HDMI TX >> Controller, this patch takes the pixel format from the plat_data if provided. >> >> Signed-off-by: Neil

Re: [PATCH -next] soc: zte: pm_domains: Remove redundant dev_err call in zx2967_pd_probe()

On Mon, Feb 06, 2017 at 04:23:02PM +, Wei Yongjun wrote: > From: Wei Yongjun > > There is a error message within devm_ioremap_resource > already, so remove the dev_err call to avoid redundant > error message. > > Signed-off-by: Wei Yongjun

Re: [PATCH v3 4/6] drm: bridge: dw-hdmi: Switch to V4L bus format and encodings

On 03/07/2017 06:35 PM, Jose Abreu wrote: > Hi Neil, > > > On 07-03-2017 16:42, Neil Armstrong wrote: >> Some display pipelines can only provide non-RBG input pixels to the HDMI TX >> Controller, this patch takes the pixel format from the plat_data if provided. >> >> Signed-off-by: Neil

Re: [PATCH -next] soc: zte: pm_domains: Remove redundant dev_err call in zx2967_pd_probe()

On Mon, Feb 06, 2017 at 04:23:02PM +, Wei Yongjun wrote: > From: Wei Yongjun > > There is a error message within devm_ioremap_resource > already, so remove the dev_err call to avoid redundant > error message. > > Signed-off-by: Wei Yongjun Applied, thanks.

Re: [PATCH -next] soc: zte: pm_domains: Remove .owner field for driver

On Mon, Feb 06, 2017 at 04:23:18PM +, Wei Yongjun wrote: > From: Wei Yongjun > > Remove .owner field if calls are used which set it automatically. > > Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci > > Signed-off-by: Wei Yongjun

Re: [PATCH -next] soc: zte: pm_domains: Remove .owner field for driver

On Mon, Feb 06, 2017 at 04:23:18PM +, Wei Yongjun wrote: > From: Wei Yongjun > > Remove .owner field if calls are used which set it automatically. > > Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci > > Signed-off-by: Wei Yongjun Applied, thanks.

Re: [PATCH v4 2/7] perf/sdt: Directly record SDT events with 'perf record'

Hi Ravi, On Mon, 6 Mar 2017 18:42:59 +0530 Ravi Bangoria wrote: > diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c > index bc84a37..e87b19b 100644 > --- a/tools/perf/builtin-record.c > +++ b/tools/perf/builtin-record.c > @@ -39,6 +39,7 @@

Re: [PATCH v4 2/7] perf/sdt: Directly record SDT events with 'perf record'

Hi Ravi, On Mon, 6 Mar 2017 18:42:59 +0530 Ravi Bangoria wrote: > diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c > index bc84a37..e87b19b 100644 > --- a/tools/perf/builtin-record.c > +++ b/tools/perf/builtin-record.c > @@ -39,6 +39,7 @@ > #include "util/trigger.h" >

Re: [Xen-devel] [PATCH 4/7] xen/9pfs: connect to the backend

Hi Stefano, On 08/03/17 00:49, Stefano Stabellini wrote: On Tue, 7 Mar 2017, Julien Grall wrote: On 03/06/2017 08:01 PM, Stefano Stabellini wrote: + if (ring->bytes == NULL) + goto error; + for (i = 0; i < (1 << XEN_9PFS_RING_ORDER); i++) +

Re: [Xen-devel] [PATCH 4/7] xen/9pfs: connect to the backend

Hi Stefano, On 08/03/17 00:49, Stefano Stabellini wrote: On Tue, 7 Mar 2017, Julien Grall wrote: On 03/06/2017 08:01 PM, Stefano Stabellini wrote: + if (ring->bytes == NULL) + goto error; + for (i = 0; i < (1 << XEN_9PFS_RING_ORDER); i++) +

Re: kasan behavior when built with unsupported compiler

On Wed, Mar 8, 2017 at 9:10 AM, Nikolay Borisov wrote: > > > On 7.03.2017 17:54, Dmitry Vyukov wrote: >> On Tue, Mar 7, 2017 at 4:35 PM, Nikolay Borisov >> wrote: >>> Hello, >>> >>> I've been chasing a particular UAF as reported by kasan >>>

Re: kasan behavior when built with unsupported compiler

On Wed, Mar 8, 2017 at 9:10 AM, Nikolay Borisov wrote: > > > On 7.03.2017 17:54, Dmitry Vyukov wrote: >> On Tue, Mar 7, 2017 at 4:35 PM, Nikolay Borisov >> wrote: >>> Hello, >>> >>> I've been chasing a particular UAF as reported by kasan >>>

Re: [PATCH v3 06/09] iommu/ipmmu-vmsa: Write IMCTR twice

On 08/03/17 11:02, Magnus Damm wrote: > From: Magnus Damm > > Write IMCTR both in the root device and the leaf node. > > Signed-off-by: Magnus Damm > --- > > Changes since V2: > - None > > Changes since V1: > - None > >

Re: [PATCH] serial: 8250: 8250_core: Use dev_name() during request_irq()

On Wed, Mar 08, 2017 at 05:49:43PM +0530, Vignesh R wrote: > Passing "serial" as name during request_irq() results in all serial port > irqs have same name. This does not help much to easily identify which > irq belongs to which serial port instance. Therefore pass dev_name() > during

Re: [PATCH v3 06/09] iommu/ipmmu-vmsa: Write IMCTR twice

On 08/03/17 11:02, Magnus Damm wrote: > From: Magnus Damm > > Write IMCTR both in the root device and the leaf node. > > Signed-off-by: Magnus Damm > --- > > Changes since V2: > - None > > Changes since V1: > - None > > drivers/iommu/ipmmu-vmsa.c | 17 ++--- > 1 file

Re: [PATCH] serial: 8250: 8250_core: Use dev_name() during request_irq()

On Wed, Mar 08, 2017 at 05:49:43PM +0530, Vignesh R wrote: > Passing "serial" as name during request_irq() results in all serial port > irqs have same name. This does not help much to easily identify which > irq belongs to which serial port instance. Therefore pass dev_name() > during

Re: [PATCH] pciehp: Fix race condition handling surprise link-down

On Mon, Mar 06, 2017 at 06:24:17PM -0600, Bjorn Helgaas wrote: > On Fri, Feb 03, 2017 at 10:51:04AM -0600, Bjorn Helgaas wrote: > > Hi Ashok, > > Just a ping to make sure we're not deadlocked. I'm waiting for you, > so I hope you're not also waiting for me :) I'm not trying to rush you; > I

Re: [PATCH] pciehp: Fix race condition handling surprise link-down

On Mon, Mar 06, 2017 at 06:24:17PM -0600, Bjorn Helgaas wrote: > On Fri, Feb 03, 2017 at 10:51:04AM -0600, Bjorn Helgaas wrote: > > Hi Ashok, > > Just a ping to make sure we're not deadlocked. I'm waiting for you, > so I hope you're not also waiting for me :) I'm not trying to rush you; > I

Re: [f2fs-dev] [PATCH 2/2] f2fs: don't overwrite node block by SSR

On 2017/3/7 5:51, Jaegeuk Kim wrote: > This patch fixes that SSR can overwrite previous warm node block consisting of > a node chain since the last checkpoint. Good catch! Need to consider the impact to other accesser, e.g. is_checkpointed_data, add_discard_addrs? Thanks, > > Fixes:

[PATCH] platform/x86: dell-laptop: Handle return error form dell_get_intensity.

Here, dell_get_intensity can return an error. So we can assgine props.brightness as max_brightness. This change is done using Coccinelle. Signed-off-by: Arvind Yadav --- drivers/platform/x86/dell-laptop.c | 3 +++ 1 file changed, 3 insertions(+) diff --git

<    8   9   10   11   12   13   14   15   16   17   >