[PATCH] staging: wilc1000: Move Macro definition

2016-01-18 Thread Gujulan Elango, Hari Prasath (H.)
From: Hari Prasath Gujulan Elango This patch move's a macro defined in the middle of a structure definition to make it more readable. Signed-off-by: Hari Prasath Gujulan Elango --- drivers/staging/wilc1000/wilc_sdio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/

[PATCH] Staging: goldfish: Add DMA support using dma_alloc_coherent

2016-01-18 Thread Shraddha Barke
Add support for accessing the device through DMA because CPU is unnecessarily used when DMA can do the job. Coherent mapping is allocated by means of dma_alloc_coherent so that the device and CPU are in sync. Signed-off-by: Shraddha Barke --- drivers/staging/goldfish/goldfish_nand.c | 15 +++

[PATCH 2/3] Drivers: hv: vmbus: avoid scheduling in interrupt context in vmbus_initiate_unload()

2016-01-18 Thread Vitaly Kuznetsov
We have to call vmbus_initiate_unload() on crash to make kdump work but the crash can also be happening in interrupt (e.g. Sysrq + c results in such) where we can't schedule or the following will happen: [ 314.905786] bad: scheduling from the idle thread! Just skipping the wait (and even adding

[PATCH 1/3] Drivers: hv: vmbus: avoid infinite loop in init_vp_index()

2016-01-18 Thread Vitaly Kuznetsov
When we pick a CPU to use for a new subchannel we try find a non-used one on the appropriate NUMA node, we keep track of them with the primary->alloced_cpus_in_node mask. Under normal circumstances we don't run out of available CPUs but it is possible when we we don't initialize some cpus in Linux,

[PATCH 0/3] Drivers: hv: fix kdump (again) and more

2016-01-18 Thread Vitaly Kuznetsov
Kdump on crash is reportedly broken for Hyper-V guests and I was able to find two reasons: 1) Inability to boot with nr_cpus=1 (PATCH 1) 2) Sleeping in interrupt context on crash (PATCH 2 and 3) Vitaly Kuznetsov (3): Drivers: hv: vmbus: avoid infinite loop in init_vp_index() Drivers: hv: vmbus

[PATCH 3/3] Drivers: hv: vmbus: don't manipulate with clocksources on crash

2016-01-18 Thread Vitaly Kuznetsov
clocksource_change_rating() involves mutex usage and can't be called in interrupt context. It also makes sense to avoid doing redundant work on crash. Signed-off-by: Vitaly Kuznetsov --- drivers/hv/hv.c | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/drivers/hv/hv.

Re: [PATCH] Staging: goldfish: Add DMA support using dma_alloc_coherent

2016-01-18 Thread kbuild test robot
Hi Shraddha, [auto build test WARNING on v4.4-rc8] [also build test WARNING on next-20160118] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Shraddha-Barke/Staging-goldfish-Add-DMA-support

Re: [PATCH] Staging: goldfish: Add DMA support using dma_alloc_coherent

2016-01-18 Thread Alan Cox
> unnecessarily used when DMA can do the job. Coherent mapping is > allocated > by means of dma_alloc_coherent so that the device and CPU are in > sync. It's also not freed 8) As far as I can see you can replace the devm_kzalloc of cmd->params with a dma_alloc_coherent, and ensure you free it whe

Re: [PATCH] Staging: goldfish: Add DMA support using dma_alloc_coherent

2016-01-18 Thread Shraddha Barke
On Mon, 18 Jan 2016, Alan Cox wrote: unnecessarily used when DMA can do the job. Coherent mapping is allocated by means of dma_alloc_coherent so that the device and CPU are in sync. It's also not freed 8) As far as I can see you can replace the devm_kzalloc of cmd->params with a dma_alloc_c

[PATCH] android: binder: Sanity check at binder ioctl

2016-01-18 Thread Chen Feng
When a process fork a child process, we should not allow the child process use the binder which opened by parent process. But if the binder-object creater is a thread of one process who exit, the other thread can also use this binder-object normally. We can distinguish this by the member proc->tsk

Re: [PATCH] android: binder: Sanity check at binder ioctl

2016-01-18 Thread kbuild test robot
Hi Chen, [auto build test ERROR on v4.4-rc8] [also build test ERROR on next-20160118] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Chen-Feng/android-binder-Sanity-check-at-binder-ioctl

[PATCH RESEND] android: binder: Sanity check at binder ioctl

2016-01-18 Thread Chen Feng
When a process fork a child process, we should not allow the child process use the binder which opened by parent process. But if the binder-object creater is a thread of one process who exit, the other thread can also use this binder-object normally. We can distinguish this by the member proc->tsk

Re: [PATCH RESEND] android: binder: Sanity check at binder ioctl

2016-01-18 Thread Greg KH
On Tue, Jan 19, 2016 at 11:45:36AM +0800, Chen Feng wrote: > When a process fork a child process, we should not allow the > child process use the binder which opened by parent process. > > But if the binder-object creater is a thread of one process who exit, > the other thread can also use this bi

Re: [PATCH RESEND] android: binder: Sanity check at binder ioctl

2016-01-18 Thread chenfeng
On 2016/1/19 15:33, Greg KH wrote: > On Tue, Jan 19, 2016 at 11:45:36AM +0800, Chen Feng wrote: >> When a process fork a child process, we should not allow the >> child process use the binder which opened by parent process. >> >> But if the binder-object creater is a thread of one process who exi