Re: Linux-next parallel cp workload hang

On Wed, May 18, 2016 at 09:46:15AM +0800, Xiong Zhou wrote: > Hi, > > Parallel cp workload (xfstests generic/273) hangs like blow. > It's reproducible with a small chance, less the 1/100 i think. > > Have hit this in linux-next 20160504 0506 0510 trees, testing on > xfs with loop or block

Re: Linux-next parallel cp workload hang

On Wed, May 18, 2016 at 09:46:15AM +0800, Xiong Zhou wrote: > Hi, > > Parallel cp workload (xfstests generic/273) hangs like blow. > It's reproducible with a small chance, less the 1/100 i think. > > Have hit this in linux-next 20160504 0506 0510 trees, testing on > xfs with loop or block

Re: [PATCH 1/2] arm64: dts: NS2: Add all of the UARTs

On 2016/5/18 3:56, Florian Fainelli wrote: > On 05/15/2016 06:11 PM, Kefeng Wang wrote: >>> I can confirm that with your change and the change to the bootargs you >>> describe above, it works as desired. Was your change already accepted? >>> >> >> Great, thanks a lot. it is still being

Re: [PATCH 1/2] arm64: dts: NS2: Add all of the UARTs

On 2016/5/18 3:56, Florian Fainelli wrote: > On 05/15/2016 06:11 PM, Kefeng Wang wrote: >>> I can confirm that with your change and the change to the bootargs you >>> describe above, it works as desired. Was your change already accepted? >>> >> >> Great, thanks a lot. it is still being

[RFC][PATCH 8/7] sched/fair: Use utilization distance to filter affine sync wakeups

On Mon, 2016-05-09 at 12:48 +0200, Peter Zijlstra wrote: > Hai, (got some of the frozen variety handy?:) > here be a semi coherent patch series for the recent select_idle_siblings() > tinkering. Happy benchmarking.. And tinkering on top of your rewrite series... sched/fair: Use utilization

[RFC][PATCH 8/7] sched/fair: Use utilization distance to filter affine sync wakeups

On Mon, 2016-05-09 at 12:48 +0200, Peter Zijlstra wrote: > Hai, (got some of the frozen variety handy?:) > here be a semi coherent patch series for the recent select_idle_siblings() > tinkering. Happy benchmarking.. And tinkering on top of your rewrite series... sched/fair: Use utilization

Re: UBSAN: Undefined behaviour in block/blk-mq.c:1459:27 with pata_amd

> Does the patch below help? > > From: Bartlomiej Zolnierkiewicz > Subject: [PATCH] blk-mq: fix undefined behaviour in order_to_size() > > When this_order variable in blk_mq_init_rq_map() becomes zero > the code incorrectly decrements the variable and passes the result

Re: UBSAN: Undefined behaviour in block/blk-mq.c:1459:27 with pata_amd

> Does the patch below help? > > From: Bartlomiej Zolnierkiewicz > Subject: [PATCH] blk-mq: fix undefined behaviour in order_to_size() > > When this_order variable in blk_mq_init_rq_map() becomes zero > the code incorrectly decrements the variable and passes the result > to order_to_size()

Re: [PATCH] arc: axs103_smp: Fix CPU frequency to 100MHz for dual-core

On Monday 16 May 2016 03:27 PM, Alexey Brodkin wrote: > The most recent release of AXS103 [v1.1] is proven to work > at 100 MHz in dual-core mode so this change uses mentioned feature. > For that we: > * Update axc003_idu.dtsi with mention of really-used CPU clock freq > * Remove clock override

Re: [PATCH] arc: axs103_smp: Fix CPU frequency to 100MHz for dual-core

On Monday 16 May 2016 03:27 PM, Alexey Brodkin wrote: > The most recent release of AXS103 [v1.1] is proven to work > at 100 MHz in dual-core mode so this change uses mentioned feature. > For that we: > * Update axc003_idu.dtsi with mention of really-used CPU clock freq > * Remove clock override

Re: [PATCH] ARC: Troubleshoot execution of UP Linux on SMP HW and vice versa

On Wednesday 18 May 2016 02:36 AM, Alexey Brodkin wrote: > ARC SMP hardware heavily relies on Interrupt Distribution Unit (IDU) > for all interrupts serving. And UP ARC hardware lacks this block. > > That leads to incompatibility between UP and SMP Linux builds. > > Even though UP build of Linux

Re: [PATCH] ARC: Troubleshoot execution of UP Linux on SMP HW and vice versa

On Wednesday 18 May 2016 02:36 AM, Alexey Brodkin wrote: > ARC SMP hardware heavily relies on Interrupt Distribution Unit (IDU) > for all interrupts serving. And UP ARC hardware lacks this block. > > That leads to incompatibility between UP and SMP Linux builds. > > Even though UP build of Linux

Re: [PATCH] net: au1000 eth: simplify logical expression

Le 17/05/2016 16:58, Heinrich Schuchardt a écrit : > (a && a > 0) is equivalent to (a > 0). > > Signed-off-by: Heinrich Schuchardt Acked-by: Florian Fainelli -- Florian

Re: [PATCH] net: au1000 eth: simplify logical expression

Le 17/05/2016 16:58, Heinrich Schuchardt a écrit : > (a && a > 0) is equivalent to (a > 0). > > Signed-off-by: Heinrich Schuchardt Acked-by: Florian Fainelli -- Florian

Re: Crashes in -next due to 'phy: add support for a reset-gpio specification'

9.371540] Unable to handle kernel paging request at virtual address > 001c > [9.371540] pc = d0320926, ra = 903209d1 > [9.375358] Oops: sig: 11 [#1] > [9.376081] PREEMPT > [9.377080] CPU: 0 PID: 1 Comm: swapper Not tainted > 4.6.0-next-20160517 #1 >

Re: Crashes in -next due to 'phy: add support for a reset-gpio specification'

9.371540] Unable to handle kernel paging request at virtual address > 001c > [9.371540] pc = d0320926, ra = 903209d1 > [9.375358] Oops: sig: 11 [#1] > [9.376081] PREEMPT > [9.377080] CPU: 0 PID: 1 Comm: swapper Not tainted > 4.6.0-next-20160517 #1 >

[PATCH 1/1] Staging: comedi: fix CHECK: Prefer using the BIT macro issues in pcmmio.c

This patch Replace all occurences of (1< --- drivers/staging/comedi/drivers/pcmmio.c | 40

[PATCH 1/1] Staging: comedi: fix CHECK: Prefer using the BIT macro issues in pcmmio.c

This patch Replace all occurences of (1< --- drivers/staging/comedi/drivers/pcmmio.c | 40 - 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/drivers/staging/comedi/drivers/pcmmio.c b/drivers/staging/comedi/drivers/pcmmio.c index 10472e6..70ad497

Crashes in -next due to 'phy: add support for a reset-gpio specification'

[9.371540] pc = d0320926, ra = 903209d1 [9.375358] Oops: sig: 11 [#1] [9.376081] PREEMPT [9.377080] CPU: 0 PID: 1 Comm: swapper Not tainted 4.6.0-next-20160517 #1 [9.378397] task: d7c2c000 ti: d7c3 task.ti: d7c3 [9.379394] a00: 903209d1 d7c31bd0 d7fb5810 0001

Crashes in -next due to 'phy: add support for a reset-gpio specification'

[9.371540] pc = d0320926, ra = 903209d1 [9.375358] Oops: sig: 11 [#1] [9.376081] PREEMPT [9.377080] CPU: 0 PID: 1 Comm: swapper Not tainted 4.6.0-next-20160517 #1 [9.378397] task: d7c2c000 ti: d7c3 task.ti: d7c3 [9.379394] a00: 903209d1 d7c31bd0 d7fb5810 0001

Re: [PATCH v2 1/9] powerpc/powernv: Move CHECK_HMI_INTERRUPT to exception-64s header

On Tue, May 03, 2016 at 01:54:30PM +0530, Shreyas B. Prabhu wrote: > CHECK_HMI_INTERRUPT is used to check for HMI's in reset vector. Move > the macro to a common location (exception-64s.h) > This patch does not change any functionality. > I suppose this code movement is to facilitate the

Re: [PATCH v2 1/9] powerpc/powernv: Move CHECK_HMI_INTERRUPT to exception-64s header

On Tue, May 03, 2016 at 01:54:30PM +0530, Shreyas B. Prabhu wrote: > CHECK_HMI_INTERRUPT is used to check for HMI's in reset vector. Move > the macro to a common location (exception-64s.h) > This patch does not change any functionality. > I suppose this code movement is to facilitate the

linux-next: Tree for May 18

Hi all, Please do not add any v4.8 destined material to your linux-next included branches until after v4.7-rc1 has been released. Changes since 20160517: New tree: dax-misc The dax-misc tree gained a conflict against the nvdimm tree. The akpm-current tree gained a conflict against the dax

linux-next: Tree for May 18

Hi all, Please do not add any v4.8 destined material to your linux-next included branches until after v4.7-rc1 has been released. Changes since 20160517: New tree: dax-misc The dax-misc tree gained a conflict against the nvdimm tree. The akpm-current tree gained a conflict against the dax

Re: [PATCH] mmc: dw_mmc: Consider HLE errors to be data and command errors

Hi, On Tue, May 17, 2016 at 7:08 PM, Jaehoon Chung wrote: > On 05/18/2016 09:47 AM, Doug Anderson wrote: >> Jaehoon, >> >> On Mon, Mar 30, 2015 at 8:47 AM, Doug Anderson wrote: >>> Jaehoon, >>> >>> On Sun, Mar 29, 2015 at 5:55 PM, Jaehoon Chung

Re: [PATCH] mmc: dw_mmc: Consider HLE errors to be data and command errors

Hi, On Tue, May 17, 2016 at 7:08 PM, Jaehoon Chung wrote: > On 05/18/2016 09:47 AM, Doug Anderson wrote: >> Jaehoon, >> >> On Mon, Mar 30, 2015 at 8:47 AM, Doug Anderson wrote: >>> Jaehoon, >>> >>> On Sun, Mar 29, 2015 at 5:55 PM, Jaehoon Chung >>> wrote: Dear Doug, I'm

Re: [PATCH] mmc: dw_mmc: Consider HLE errors to be data and command errors

Hi, On Tue, May 17, 2016 at 6:59 PM, Shawn Lin wrote: > Could you try this patch to see if you can still find HLE? > > @@ -2356,12 +2356,22 @@ static void dw_mci_cmd_interrupt(struct dw_mci > *host, u32 status) > static void dw_mci_handle_cd(struct dw_mci *host) >

Re: [PATCH] mmc: dw_mmc: Consider HLE errors to be data and command errors

Hi, On Tue, May 17, 2016 at 6:59 PM, Shawn Lin wrote: > Could you try this patch to see if you can still find HLE? > > @@ -2356,12 +2356,22 @@ static void dw_mci_cmd_interrupt(struct dw_mci > *host, u32 status) > static void dw_mci_handle_cd(struct dw_mci *host) > { > int i; > +

Re: QRTR merge conflict resolution

On Tue 17 May 17:43 PDT 2016, Stephen Rothwell wrote: > Hi David, > > On Tue, 17 May 2016 14:11:54 -0400 (EDT) David Miller > wrote: > > > > From: Bjorn Andersson > > Date: Fri, 13 May 2016 15:19:09 -0700 > > > > > I have prepared the merge of

Re: QRTR merge conflict resolution

On Tue 17 May 17:43 PDT 2016, Stephen Rothwell wrote: > Hi David, > > On Tue, 17 May 2016 14:11:54 -0400 (EDT) David Miller > wrote: > > > > From: Bjorn Andersson > > Date: Fri, 13 May 2016 15:19:09 -0700 > > > > > I have prepared the merge of net-next and the conflicting tag from the > > >

Re: [PATCH] sched/cputime: add steal time support to full dynticks CPU time accounting

On Tue, 2016-05-10 at 13:34 +0800, Wanpeng Li wrote: > From: Wanpeng Li > > This patch adds steal guest time support to full dynticks CPU time  > accounting. After commit ff9a9b4c(sched, time: Switch > VIRT_CPU_ACCOUNTING_GEN  > to jiffy granularity), time is jiffy based

Re: [PATCH] sched/cputime: add steal time support to full dynticks CPU time accounting

On Tue, 2016-05-10 at 13:34 +0800, Wanpeng Li wrote: > From: Wanpeng Li > > This patch adds steal guest time support to full dynticks CPU time  > accounting. After commit ff9a9b4c(sched, time: Switch > VIRT_CPU_ACCOUNTING_GEN  > to jiffy granularity), time is jiffy based sampling even if it's  >

Re: [PATCH v12 05/10] arm64: Kprobes with single stepping support

On Thu, 12 May 2016 16:01:54 +0100 James Morse wrote: > Hi David, Sandeepa, > > On 27/04/16 19:53, David Long wrote: > > From: Sandeepa Prabhu > > > diff --git a/arch/arm64/kernel/kprobes.c b/arch/arm64/kernel/kprobes.c > > new file mode

Re: [PATCH v12 05/10] arm64: Kprobes with single stepping support

On Thu, 12 May 2016 16:01:54 +0100 James Morse wrote: > Hi David, Sandeepa, > > On 27/04/16 19:53, David Long wrote: > > From: Sandeepa Prabhu > > > diff --git a/arch/arm64/kernel/kprobes.c b/arch/arm64/kernel/kprobes.c > > new file mode 100644 > > index 000..dfa1b1f > > --- /dev/null > >

linux-next: manual merge of the akpm-current tree with the dax-misc tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: include/linux/dax.h between commit: ecdb4bf9e327 ("dax: export a low-level __dax_zero_page_range helper") from the dax-misc tree and commit: 29d44f6759f6 ("dax: add dax_get_unmapped_area for pmd mappings")

linux-next: manual merge of the akpm-current tree with the dax-misc tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: include/linux/dax.h between commit: ecdb4bf9e327 ("dax: export a low-level __dax_zero_page_range helper") from the dax-misc tree and commit: 29d44f6759f6 ("dax: add dax_get_unmapped_area for pmd mappings")

[PATCH] MM: increase safety margin provided by PF_LESS_THROTTLE

When nfsd is exporting a filesystem over NFS which is then NFS-mounted on the local machine there is a risk of deadlock. This happens when there are lots of dirty pages in the NFS filesystem and they cause NFSD to be throttled, either in throttle_vm_writeout() or in balance_dirty_pages(). To

[PATCH] MM: increase safety margin provided by PF_LESS_THROTTLE

When nfsd is exporting a filesystem over NFS which is then NFS-mounted on the local machine there is a risk of deadlock. This happens when there are lots of dirty pages in the NFS filesystem and they cause NFSD to be throttled, either in throttle_vm_writeout() or in balance_dirty_pages(). To

Re: [GIT] Networking

On Wed, May 18, 2016 at 4:00 AM, Linus Torvalds wrote: > On Tue, May 17, 2016 at 12:11 PM, David Miller wrote: >> >> Highlights: > > Lowlights: > > 1) the iwlwifi driver seems to be broken > > My laptop that uses the intel 7680 iwlwifi module

Re: [GIT] Networking

On Wed, May 18, 2016 at 4:00 AM, Linus Torvalds wrote: > On Tue, May 17, 2016 at 12:11 PM, David Miller wrote: >> >> Highlights: > > Lowlights: > > 1) the iwlwifi driver seems to be broken > > My laptop that uses the intel 7680 iwlwifi module no longer connects > to the network. It fails with a

linux-next: manual merge of the dax-misc tree with the nvdimm tree

Hi all, Today's linux-next merge of the dax-misc tree got a conflict in: fs/block_dev.c between commit: 8044aae6f374 ("Revert "block: enable dax for raw block devices"") from the nvdimm tree and commit: 02fbd139759f ("dax: Remove complete_unwritten argument") from the dax-misc tree.

linux-next: manual merge of the dax-misc tree with the nvdimm tree

Hi all, Today's linux-next merge of the dax-misc tree got a conflict in: fs/block_dev.c between commit: 8044aae6f374 ("Revert "block: enable dax for raw block devices"") from the nvdimm tree and commit: 02fbd139759f ("dax: Remove complete_unwritten argument") from the dax-misc tree.

Re: 45aebeaf4f67 "ovl: Ensure upper filesystem supports d_type" breaking Docker

Hi Vivek, My sincere apologies - it turns out I *was* running on xfs with ftype=0. Someone in the office had moved docker's storage without me noticing. Apologies to all whose time I wasted. Regards, Daniel Vivek Goyal writes: > On Tue, May 17, 2016 at 10:15:21AM +0200,

Re: 45aebeaf4f67 "ovl: Ensure upper filesystem supports d_type" breaking Docker

Hi Vivek, My sincere apologies - it turns out I *was* running on xfs with ftype=0. Someone in the office had moved docker's storage without me noticing. Apologies to all whose time I wasted. Regards, Daniel Vivek Goyal writes: > On Tue, May 17, 2016 at 10:15:21AM +0200, Miklos Szeredi wrote:

Re: [PATCH 02/17] perf tools: Add evlist channel helpers

On 2016/5/13 21:05, Arnaldo Carvalho de Melo wrote: Em Fri, May 13, 2016 at 07:55:59AM +, Wang Nan escreveu: In this commit sereval helpers are introduced to support the principle several of channel. Channels hold different groups of evsels which configured

Re: [PATCH 02/17] perf tools: Add evlist channel helpers

On 2016/5/13 21:05, Arnaldo Carvalho de Melo wrote: Em Fri, May 13, 2016 at 07:55:59AM +, Wang Nan escreveu: In this commit sereval helpers are introduced to support the principle several of channel. Channels hold different groups of evsels which configured

Re: [PATCH v12 05/10] arm64: Kprobes with single stepping support

On Tue, 17 May 2016 16:58:09 +0800 Huang Shijie wrote: > On Wed, Apr 27, 2016 at 02:53:00PM -0400, David Long wrote: > > + > > +/* > > + * Interrupts need to be disabled before single-step mode is set, and not > > + * reenabled until after single-step mode ends. > > + *

Re: [PATCH v12 05/10] arm64: Kprobes with single stepping support

On Tue, 17 May 2016 16:58:09 +0800 Huang Shijie wrote: > On Wed, Apr 27, 2016 at 02:53:00PM -0400, David Long wrote: > > + > > +/* > > + * Interrupts need to be disabled before single-step mode is set, and not > > + * reenabled until after single-step mode ends. > > + * Without disabling

Re: [PATCH v8 13/14] usb: gadget: udc: adapt to OTG core

On Mon, May 16, 2016 at 12:51:53PM +0300, Roger Quadros wrote: > On 16/05/16 12:23, Peter Chen wrote: > > On Mon, May 16, 2016 at 11:26:57AM +0300, Roger Quadros wrote: > >> Hi, > >> > >> On 16/05/16 10:02, Peter Chen wrote: > >>> On Fri, May 13, 2016 at 01:03:27PM +0300, Roger Quadros wrote: >

Re: [PATCH v8 13/14] usb: gadget: udc: adapt to OTG core

On Mon, May 16, 2016 at 12:51:53PM +0300, Roger Quadros wrote: > On 16/05/16 12:23, Peter Chen wrote: > > On Mon, May 16, 2016 at 11:26:57AM +0300, Roger Quadros wrote: > >> Hi, > >> > >> On 16/05/16 10:02, Peter Chen wrote: > >>> On Fri, May 13, 2016 at 01:03:27PM +0300, Roger Quadros wrote: >

Re: Re: [PATCH v8 3/5] mfd: hi655x: Add MFD driver for hi655x

gt; replied "Applied". Are you expecting anything else? Dependencies? > > > > I didn't see any unsolved review comments actually. But if there is, > > please let us know, so I can send an updated version. > > When I applied your patch, I also added ~40 other patches.

Re: Re: [PATCH v8 3/5] mfd: hi655x: Add MFD driver for hi655x

t-20160418) since your > > replied "Applied". Are you expecting anything else? Dependencies? > > > > I didn't see any unsolved review comments actually. But if there is, > > please let us know, so I can send an updated version. > > When I applied your patch,

RE: [PATCH 1/3] ACPI: table upgrade: use cacheable map for tables

Hi, > From: Aleksey Makarov [mailto:aleksey.maka...@linaro.org] > Subject: [PATCH 1/3] ACPI: table upgrade: use cacheable map for tables > > The new memory allocated in acpi_table_initrd_init() is used to > copy the upgraded tables to it. So it should be mapped with > early_memunmap() instead

RE: [PATCH 1/3] ACPI: table upgrade: use cacheable map for tables

Hi, > From: Aleksey Makarov [mailto:aleksey.maka...@linaro.org] > Subject: [PATCH 1/3] ACPI: table upgrade: use cacheable map for tables > > The new memory allocated in acpi_table_initrd_init() is used to > copy the upgraded tables to it. So it should be mapped with > early_memunmap() instead

Re: [PATCH v3 3/7 UPDATE] perf tools: Add option for the path of buildid dsos under symfs

On 5/17/16 8:48 PM, Hekuang wrote: I don't understand why dso-prefix option is needed? Why make me type yet more options to the analysis command? Why can't the directory be located under the symfs tree in a known location and populated the same way it is without symfs? Because the default

Re: [PATCH v3 3/7 UPDATE] perf tools: Add option for the path of buildid dsos under symfs

On 5/17/16 8:48 PM, Hekuang wrote: I don't understand why dso-prefix option is needed? Why make me type yet more options to the analysis command? Why can't the directory be located under the symfs tree in a known location and populated the same way it is without symfs? Because the default

Re: [PATCH v3 3/7 UPDATE] perf tools: Add option for the path of buildid dsos under symfs

在 2016/5/18 9:51, David Ahern 写道: On 5/17/16 7:47 PM, Hekuang wrote: 在 2016/5/16 10:50, David Ahern 写道: On 5/15/16 7:30 PM, Hekuang wrote: In previous patch, I use 'perf buildid-cache -a' to add vdso binary into the HOST buildid dir. So 'perf buildid-cache' needs the symfs option?

Re: [PATCH v3 3/7 UPDATE] perf tools: Add option for the path of buildid dsos under symfs

在 2016/5/18 9:51, David Ahern 写道: On 5/17/16 7:47 PM, Hekuang wrote: 在 2016/5/16 10:50, David Ahern 写道: On 5/15/16 7:30 PM, Hekuang wrote: In previous patch, I use 'perf buildid-cache -a' to add vdso binary into the HOST buildid dir. So 'perf buildid-cache' needs the symfs option?

Re: CQ and RDMA READ/WRITE APIs

Hi Doug, On Tue, May 17, 2016 at 11:02 PM, Doug Ledford wrote: > Nice catch there Bart. That was well before my role as maintainer and > so settles things well enough for me. IOW, I don't feel I need to worry > about trying to maintain the dual license nature of the RDMA

Re: CQ and RDMA READ/WRITE APIs

Hi Doug, On Tue, May 17, 2016 at 11:02 PM, Doug Ledford wrote: > Nice catch there Bart. That was well before my role as maintainer and > so settles things well enough for me. IOW, I don't feel I need to worry > about trying to maintain the dual license nature of the RDMA stack as it > was

Re: [RFC][PATCH 5/5] sched/core: Add debug code to catch missing update_rq_clock()

On Tue, May 17, 2016 at 01:24:15PM +0100, Matt Fleming wrote: > So, if the code looks like the following, either now or in the future, > > static void __schedule(bool preempt) > { > ... > /* Clear RQCF_ACT_SKIP */ > rq->clock_update_flags = 0; > ... > delta =

Re: [RFC][PATCH 5/5] sched/core: Add debug code to catch missing update_rq_clock()

On Tue, May 17, 2016 at 01:24:15PM +0100, Matt Fleming wrote: > So, if the code looks like the following, either now or in the future, > > static void __schedule(bool preempt) > { > ... > /* Clear RQCF_ACT_SKIP */ > rq->clock_update_flags = 0; > ... > delta =

[PATCH] mm: fix duplicate words and typos

Signed-off-by: Li Peng --- mm/memcontrol.c | 2 +- mm/page_alloc.c | 6 +++--- mm/vmscan.c | 7 +++ mm/zswap.c | 2 +- 4 files changed, 8 insertions(+), 9 deletions(-) diff --git a/mm/memcontrol.c b/mm/memcontrol.c index fe787f5..4b74255 100644 ---

[PATCH] mm: fix duplicate words and typos

Signed-off-by: Li Peng --- mm/memcontrol.c | 2 +- mm/page_alloc.c | 6 +++--- mm/vmscan.c | 7 +++ mm/zswap.c | 2 +- 4 files changed, 8 insertions(+), 9 deletions(-) diff --git a/mm/memcontrol.c b/mm/memcontrol.c index fe787f5..4b74255 100644 --- a/mm/memcontrol.c +++

Re: [PATCH v12 00/10] arm64: Add kernel probes (kprobes) support

On Thu, May 12, 2016 at 10:26:40AM +0800, Li Bin wrote: > > > on 2016/5/11 23:33, James Morse wrote: > > Hi David, > > > > On 27/04/16 19:52, David Long wrote: > >> From: "David A. Long" > >> > >> This patchset is heavily based on Sandeepa Prabhu's ARM v8 kprobes patches,

Re: [PATCH v12 00/10] arm64: Add kernel probes (kprobes) support

On Thu, May 12, 2016 at 10:26:40AM +0800, Li Bin wrote: > > > on 2016/5/11 23:33, James Morse wrote: > > Hi David, > > > > On 27/04/16 19:52, David Long wrote: > >> From: "David A. Long" > >> > >> This patchset is heavily based on Sandeepa Prabhu's ARM v8 kprobes patches, > >> first seen in

Re: [PATCH] mmc: dw_mmc: Consider HLE errors to be data and command errors

On 05/18/2016 09:47 AM, Doug Anderson wrote: > Jaehoon, > > On Mon, Mar 30, 2015 at 8:47 AM, Doug Anderson wrote: >> Jaehoon, >> >> On Sun, Mar 29, 2015 at 5:55 PM, Jaehoon Chung >> wrote: >>> Dear Doug, >>> >>> I'm considering to control HLE

Re: [PATCH] mmc: dw_mmc: Consider HLE errors to be data and command errors

On 05/18/2016 09:47 AM, Doug Anderson wrote: > Jaehoon, > > On Mon, Mar 30, 2015 at 8:47 AM, Doug Anderson wrote: >> Jaehoon, >> >> On Sun, Mar 29, 2015 at 5:55 PM, Jaehoon Chung >> wrote: >>> Dear Doug, >>> >>> I'm considering to control HLE error..So holding this patch. >>> If this is

[PATCH v2] Drivers: hv: vmbus: fix the race when querying & updating the percpu list

There is a rare race when we remove an entry from the global list hv_context.percpu_list[cpu] in hv_process_channel_removal() -> percpu_channel_deq() -> list_del(): at this time, if vmbus_on_event() -> process_chn_event() -> pcpu_relid2channel() is trying to query the list, we can get the general

[PATCH v2] Drivers: hv: vmbus: fix the race when querying & updating the percpu list

There is a rare race when we remove an entry from the global list hv_context.percpu_list[cpu] in hv_process_channel_removal() -> percpu_channel_deq() -> list_del(): at this time, if vmbus_on_event() -> process_chn_event() -> pcpu_relid2channel() is trying to query the list, we can get the general

Re: [PATCH] mmc: dw_mmc: Consider HLE errors to be data and command errors

Hi Doug, On 2016-5-18 8:47, Doug Anderson wrote: Jaehoon, On Mon, Mar 30, 2015 at 8:47 AM, Doug Anderson wrote: Jaehoon, On Sun, Mar 29, 2015 at 5:55 PM, Jaehoon Chung wrote: Dear Doug, I'm considering to control HLE error..So holding this

Re: [PATCH] mmc: dw_mmc: Consider HLE errors to be data and command errors

Hi Doug, On 2016-5-18 8:47, Doug Anderson wrote: Jaehoon, On Mon, Mar 30, 2015 at 8:47 AM, Doug Anderson wrote: Jaehoon, On Sun, Mar 29, 2015 at 5:55 PM, Jaehoon Chung wrote: Dear Doug, I'm considering to control HLE error..So holding this patch. If this is absolutely necessary patch,

Re: [PATCH v3 3/7 UPDATE] perf tools: Add option for the path of buildid dsos under symfs

在 2016/5/16 10:50, David Ahern 写道: On 5/15/16 7:30 PM, Hekuang wrote: In previous patch, I use 'perf buildid-cache -a' to add vdso binary into the HOST buildid dir. So 'perf buildid-cache' needs the symfs option? With this patch 'PATCH v3 3/7 UPDATE', the tree of symfs dir is like this:

Re: [PATCH v3 3/7 UPDATE] perf tools: Add option for the path of buildid dsos under symfs

在 2016/5/16 10:50, David Ahern 写道: On 5/15/16 7:30 PM, Hekuang wrote: In previous patch, I use 'perf buildid-cache -a' to add vdso binary into the HOST buildid dir. So 'perf buildid-cache' needs the symfs option? With this patch 'PATCH v3 3/7 UPDATE', the tree of symfs dir is like this:

Re: [PATCH v3 3/7 UPDATE] perf tools: Add option for the path of buildid dsos under symfs

On 5/17/16 7:47 PM, Hekuang wrote: 在 2016/5/16 10:50, David Ahern 写道: On 5/15/16 7:30 PM, Hekuang wrote: In previous patch, I use 'perf buildid-cache -a' to add vdso binary into the HOST buildid dir. So 'perf buildid-cache' needs the symfs option? With this patch 'PATCH v3 3/7 UPDATE',

Re: [PATCH v3 3/7 UPDATE] perf tools: Add option for the path of buildid dsos under symfs

On 5/17/16 7:47 PM, Hekuang wrote: 在 2016/5/16 10:50, David Ahern 写道: On 5/15/16 7:30 PM, Hekuang wrote: In previous patch, I use 'perf buildid-cache -a' to add vdso binary into the HOST buildid dir. So 'perf buildid-cache' needs the symfs option? With this patch 'PATCH v3 3/7 UPDATE',

Linux-next parallel cp workload hang

Hi, Parallel cp workload (xfstests generic/273) hangs like blow. It's reproducible with a small chance, less the 1/100 i think. Have hit this in linux-next 20160504 0506 0510 trees, testing on xfs with loop or block device. Ext4 survived several rounds of testing. Linux next 20160510 tree hangs

Linux-next parallel cp workload hang

Hi, Parallel cp workload (xfstests generic/273) hangs like blow. It's reproducible with a small chance, less the 1/100 i think. Have hit this in linux-next 20160504 0506 0510 trees, testing on xfs with loop or block device. Ext4 survived several rounds of testing. Linux next 20160510 tree hangs

Re: [PATCH] doc: self-protection: provide initial details

On Tue, May 17, 2016 at 6:26 PM, Jonathan Corbet wrote: > On Mon, 16 May 2016 19:27:28 -0700 > Kees Cook wrote: > >> This document attempts to codify the intent around kernel self-protection >> along with discussion of both existing and desired

Re: [PATCH] doc: self-protection: provide initial details

On Tue, May 17, 2016 at 6:26 PM, Jonathan Corbet wrote: > On Mon, 16 May 2016 19:27:28 -0700 > Kees Cook wrote: > >> This document attempts to codify the intent around kernel self-protection >> along with discussion of both existing and desired technologies, with >> attention given to the

[PATCH] mm: disable fault around on emulated access bit architecture

On Tue, May 17, 2016 at 03:34:23PM +0300, Kirill A. Shutemov wrote: > On Mon, May 16, 2016 at 11:56:32PM +0900, Minchan Kim wrote: > > On Mon, May 16, 2016 at 05:29:00PM +0300, Kirill A. Shutemov wrote: > > > > Kirill, > > > > You wanted to test non-HW access bit system and I did. > > > > What's

[PATCH] mm: disable fault around on emulated access bit architecture

On Tue, May 17, 2016 at 03:34:23PM +0300, Kirill A. Shutemov wrote: > On Mon, May 16, 2016 at 11:56:32PM +0900, Minchan Kim wrote: > > On Mon, May 16, 2016 at 05:29:00PM +0300, Kirill A. Shutemov wrote: > > > > Kirill, > > > > You wanted to test non-HW access bit system and I did. > > > > What's

[PATCH 1/2] kprobes: add a new module parameter

This patch adds a new module parameter which can be used as the symbol name. With this parameter, the module becomes more flexable. Signed-off-by: Huang Shijie --- samples/kprobes/kprobe_example.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

[PATCH 2/2] kprobes: print out the symbol name for the hooks

Print out the symbol name for the hooks, it makes the logs more readable. Signed-off-by: Huang Shijie --- samples/kprobes/kprobe_example.c | 32 1 file changed, 16 insertions(+), 16 deletions(-) diff --git

[PATCH 1/2] kprobes: add a new module parameter

This patch adds a new module parameter which can be used as the symbol name. With this parameter, the module becomes more flexable. Signed-off-by: Huang Shijie --- samples/kprobes/kprobe_example.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

[PATCH 2/2] kprobes: print out the symbol name for the hooks

Print out the symbol name for the hooks, it makes the logs more readable. Signed-off-by: Huang Shijie --- samples/kprobes/kprobe_example.c | 32 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/samples/kprobes/kprobe_example.c

Re: [PATCH v12 10/10] kprobes: Add arm64 case in kprobe example module

On Tue, May 17, 2016 at 11:24:27AM +0100, Mark Brown wrote: > On Tue, May 17, 2016 at 05:57:33PM +0800, Huang Shijie wrote: > > On Wed, Apr 27, 2016 at 02:53:05PM -0400, David Long wrote: > > > > +#ifdef CONFIG_ARM64 > > > + pr_info("pre_handler: p->addr = 0x%p, pc = 0x%lx\n", > > > I think you

Re: [PATCH v12 10/10] kprobes: Add arm64 case in kprobe example module

On Tue, May 17, 2016 at 11:24:27AM +0100, Mark Brown wrote: > On Tue, May 17, 2016 at 05:57:33PM +0800, Huang Shijie wrote: > > On Wed, Apr 27, 2016 at 02:53:05PM -0400, David Long wrote: > > > > +#ifdef CONFIG_ARM64 > > > + pr_info("pre_handler: p->addr = 0x%p, pc = 0x%lx\n", > > > I think you

Re: [f2fs-dev] [PATCH] f2fs: use bio count instead of F2FS_WRITEBACK page count

On Wed, May 18, 2016 at 09:17:00AM +0800, Chao Yu wrote: > Hi Jaegeuk, > > On 2016/5/18 8:44, Jaegeuk Kim wrote: > > This can reduce page counting overhead. > > We change to increase one reference for one bio, but block layer can split or > merge bios by itself, and write_end will be called per

Re: [f2fs-dev] [PATCH] f2fs: use bio count instead of F2FS_WRITEBACK page count

On Wed, May 18, 2016 at 09:17:00AM +0800, Chao Yu wrote: > Hi Jaegeuk, > > On 2016/5/18 8:44, Jaegeuk Kim wrote: > > This can reduce page counting overhead. > > We change to increase one reference for one bio, but block layer can split or > merge bios by itself, and write_end will be called per

Re: [PATCH] Staging: comedi: quatech_daqp_cs.c: fixed a warning issue

On Tue, May 17, 2016 at 06:47:56AM -0700, Greg KH wrote: > A: http://en.wikipedia.org/wiki/Top_post > Q: Were do I find info about this thing called top-posting? > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q:

Re: [PATCH] Staging: comedi: quatech_daqp_cs.c: fixed a warning issue

On Tue, May 17, 2016 at 06:47:56AM -0700, Greg KH wrote: > A: http://en.wikipedia.org/wiki/Top_post > Q: Were do I find info about this thing called top-posting? > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q:

[PATCH v4 3/5] locking/rwsem: Don't wake up one's own task

As rwsem_down_read_failed() will queue itself and potentially call __rwsem_do_wake(sem, RWSEM_WAKE_ANY), it is possible that a reader will try to wake up its own task. This patch adds a check to make sure that this won't happen. Signed-off-by: Waiman Long Reviewed-by: Peter

[PATCH v4 5/5] locking/rwsem: Streamline the rwsem_optimistic_spin() code

This patch moves the owner loading and checking code entirely inside of rwsem_spin_on_owner() to simplify the logic of rwsem_optimistic_spin() loop. Suggested-by: Peter Hurley Signed-off-by: Waiman Long Reviewed-by: Peter Hurley

[PATCH v4 0/5] [PATCH v3 0/4] locking/rwsem: Add reader-owned state to the owner field

v3->v4: - Add a new patch 2 to use WRITE_ONCE() for all rwsem->owner stores to prevent store tearing. v2->v3: - Make minor code changes as suggested by PeterZ & Peter Hurley. - Add 2 minor patches (#2 & #3) to improve the rwsem code - Add a 4th patch to streamline the

[PATCH v4 1/5] locking/rwsem: Add reader-owned state to the owner field

Currently, it is not possible to determine for sure if a reader owns a rwsem by looking at the content of the rwsem data structure. This patch adds a new state RWSEM_READER_OWNED to the owner field to indicate that readers currently own the lock. This enables us to address the following 2 issues

[PATCH v4 3/5] locking/rwsem: Don't wake up one's own task

As rwsem_down_read_failed() will queue itself and potentially call __rwsem_do_wake(sem, RWSEM_WAKE_ANY), it is possible that a reader will try to wake up its own task. This patch adds a check to make sure that this won't happen. Signed-off-by: Waiman Long Reviewed-by: Peter Hurley ---

[PATCH v4 5/5] locking/rwsem: Streamline the rwsem_optimistic_spin() code

This patch moves the owner loading and checking code entirely inside of rwsem_spin_on_owner() to simplify the logic of rwsem_optimistic_spin() loop. Suggested-by: Peter Hurley Signed-off-by: Waiman Long Reviewed-by: Peter Hurley --- kernel/locking/rwsem-xadd.c | 38

[PATCH v4 0/5] [PATCH v3 0/4] locking/rwsem: Add reader-owned state to the owner field

v3->v4: - Add a new patch 2 to use WRITE_ONCE() for all rwsem->owner stores to prevent store tearing. v2->v3: - Make minor code changes as suggested by PeterZ & Peter Hurley. - Add 2 minor patches (#2 & #3) to improve the rwsem code - Add a 4th patch to streamline the

[PATCH v4 1/5] locking/rwsem: Add reader-owned state to the owner field

Currently, it is not possible to determine for sure if a reader owns a rwsem by looking at the content of the rwsem data structure. This patch adds a new state RWSEM_READER_OWNED to the owner field to indicate that readers currently own the lock. This enables us to address the following 2 issues

  1   2   3   4   5   6   7   8   9   10   >