[PATCH 6/6] staging: speakup: Comparison to NULL could be written

Fixed coding style for null comparisons in speakup driver to be more consistant with the rest of the kernel coding style. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/selection.c | 2 +- drivers/staging/speakup/varhandlers.c | 6 +++--- 2 files

[PATCH 6/6] staging: speakup: Comparison to NULL could be written

Fixed coding style for null comparisons in speakup driver to be more consistant with the rest of the kernel coding style. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/selection.c | 2 +- drivers/staging/speakup/varhandlers.c | 6 +++--- 2 files changed, 4 insertions(+), 4

[PATCH 5/6] staging: speakup: fixes braces {} should be used on all arms of this statement

This patch fixes the checks reported by checkpatch.pl for braces {} should be used on all arms of this statement. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 32 +++- 1 file changed, 19 insertions(+), 13

[PATCH 5/6] staging: speakup: fixes braces {} should be used on all arms of this statement

This patch fixes the checks reported by checkpatch.pl for braces {} should be used on all arms of this statement. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 32 +++- 1 file changed, 19 insertions(+), 13 deletions(-) diff --git

[PATCH 4/6] staging: speakup: Avoid multiple assignments on same line

This patch fixes the checkpatch.pl warning "multiple assignments should be avoided." Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git

[PATCH 1/6] staging: speakup: Add blank line after function/struct/union/enum declarations

This patch fixes the warnings reported by checkpatch.pl for please use a blank line after function/struct/union/enum declarations. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 1 + drivers/staging/speakup/serialio.c | 1 +

[PATCH 4/6] staging: speakup: Avoid multiple assignments on same line

This patch fixes the checkpatch.pl warning "multiple assignments should be avoided." Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/drivers/staging/speakup/main.c

[PATCH 1/6] staging: speakup: Add blank line after function/struct/union/enum declarations

This patch fixes the warnings reported by checkpatch.pl for please use a blank line after function/struct/union/enum declarations. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 1 + drivers/staging/speakup/serialio.c | 1 + drivers/staging/speakup/speakup_dtlk.c

[PATCH 3/6] staging: speakup: Blank lines removed after an open brace '{'

Blank lines aren't necessary after an open brace '{' as reported by Checkpatch.pl. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/kobjects.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/speakup/kobjects.c

[PATCH 2/6] staging: speakup: Logical continuations should be on the previous line

This patch fixes the checkpatch issue: CHECK: Logical continuations should be on the previous line. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 34 +- 1 file changed, 17 insertions(+), 17 deletions(-) diff

[PATCH 2/6] staging: speakup: Logical continuations should be on the previous line

This patch fixes the checkpatch issue: CHECK: Logical continuations should be on the previous line. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 34 +- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git

[PATCH 3/6] staging: speakup: Blank lines removed after an open brace '{'

Blank lines aren't necessary after an open brace '{' as reported by Checkpatch.pl. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/kobjects.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/speakup/kobjects.c b/drivers/staging/speakup/kobjects.c index

[RFC][PATCH] exec: Don't wait for ptraced threads to be reaped.

Ever since CLONE_THREAD support was added to the kernel it has been possible to dead-lock userspace by ptracing a process and not reaping it's child threads. With use of the cred_guard_mutex in proc the ways userspace can unknowningly trigger a dead-lock have grown. Which makes a simple -f

[PATCH 0/6] multiple checkpatch issues

Improve readability by fixing multiple checkpatch.pl issues in speakup driver. Arushi Singhal (6): staging: speakup: Add blank line after function/struct/union/enum declarations staging: speakup: Logical continuations should be on the previous line staging: speakup: Blank lines removed

[RFC][PATCH] exec: Don't wait for ptraced threads to be reaped.

Ever since CLONE_THREAD support was added to the kernel it has been possible to dead-lock userspace by ptracing a process and not reaping it's child threads. With use of the cred_guard_mutex in proc the ways userspace can unknowningly trigger a dead-lock have grown. Which makes a simple -f

[PATCH 0/6] multiple checkpatch issues

Improve readability by fixing multiple checkpatch.pl issues in speakup driver. Arushi Singhal (6): staging: speakup: Add blank line after function/struct/union/enum declarations staging: speakup: Logical continuations should be on the previous line staging: speakup: Blank lines removed

Re: [Outreachy kernel] [PATCH 6/6] staging: speakup: fixes braces {} should be used on all arms of this statement

On Fri, 2017-03-03 at 19:40 +0100, Julia Lawall wrote: > On Sat, 4 Mar 2017, Arushi Singhal wrote: > > This patch fixes the checks reported by checkpatch.pl > > for braces {} should be used on all arms of this statement. > > > > Signed-off-by: Arushi Singhal > >

Re: [Outreachy kernel] [PATCH 6/6] staging: speakup: fixes braces {} should be used on all arms of this statement

On Fri, 2017-03-03 at 19:40 +0100, Julia Lawall wrote: > On Sat, 4 Mar 2017, Arushi Singhal wrote: > > This patch fixes the checks reported by checkpatch.pl > > for braces {} should be used on all arms of this statement. > > > > Signed-off-by: Arushi Singhal > > --- > >

Re: [GIT PULL] sched.h split-up

On Thu, Mar 2, 2017 at 5:36 PM, Ingo Molnar wrote: > > I tried to test as many build configurations as possible, but some build > breakage > is probably still left - but it should be mostly limited to architectures that > have no cross-compiler binaries available on kernel.org,

Re: [PATCH v3 0/5] Fixed compilation error

On Fri, 2017-03-03 at 21:35 +0530, SIMRAN SINGHAL wrote: > On Fri, Mar 3, 2017 at 9:20 PM, Joe Perches wrote: > > On Fri, 2017-03-03 at 17:05 +0530, simran singhal wrote: > > > Fixed compilation warning in lustre/lustre/llite/range_lock.c > > > > Really? What compilation

Re: [GIT PULL] sched.h split-up

On Thu, Mar 2, 2017 at 5:36 PM, Ingo Molnar wrote: > > I tried to test as many build configurations as possible, but some build > breakage > is probably still left - but it should be mostly limited to architectures that > have no cross-compiler binaries available on kernel.org, and non-default >

Re: [PATCH v3 0/5] Fixed compilation error

On Fri, 2017-03-03 at 21:35 +0530, SIMRAN SINGHAL wrote: > On Fri, Mar 3, 2017 at 9:20 PM, Joe Perches wrote: > > On Fri, 2017-03-03 at 17:05 +0530, simran singhal wrote: > > > Fixed compilation warning in lustre/lustre/llite/range_lock.c > > > > Really? What compilation warning was removed? >

Re: net/kcm: use-after-free in kcm_wq

On Fri, Mar 3, 2017 at 2:11 AM, Dmitry Vyukov wrote: > Also like this one: > > == > BUG: KASAN: use-after-free in atomic_long_read > include/linux/compiler.h:254 [inline] at addr 8800538aba60 > BUG: KASAN:

Re: net/kcm: use-after-free in kcm_wq

On Fri, Mar 3, 2017 at 2:11 AM, Dmitry Vyukov wrote: > Also like this one: > > == > BUG: KASAN: use-after-free in atomic_long_read > include/linux/compiler.h:254 [inline] at addr 8800538aba60 > BUG: KASAN: use-after-free in

Re: [PATCH 1/3] futex: remove duplicated code

On Fri, Mar 03, 2017 at 01:27:10PM +0100, Jiri Slaby wrote: > There is code duplicated over all architecture's headers for > futex_atomic_op_inuser. Namely op decoding, access_ok check for uaddr, > and comparison of the result. > > Remove this duplication and leave up to the arches only the

Re: [PATCH 1/3] futex: remove duplicated code

On Fri, Mar 03, 2017 at 01:27:10PM +0100, Jiri Slaby wrote: > There is code duplicated over all architecture's headers for > futex_atomic_op_inuser. Namely op decoding, access_ok check for uaddr, > and comparison of the result. > > Remove this duplication and leave up to the arches only the

Re: [PATCH 2/3] mtd: Add support for reading MTD devices via the nvmem API

On Fri, 3 Mar 2017 14:36:58 +0100 Boris Brezillon wrote: > On Fri, 3 Mar 2017 13:36:29 +0100 > Alban wrote: > > > On Thu, 2 Mar 2017 22:18:03 +0100 > > Boris Brezillon wrote: > > > > > On Thu, 2 Mar

Re: [PATCH 2/3] mtd: Add support for reading MTD devices via the nvmem API

On Fri, 3 Mar 2017 14:36:58 +0100 Boris Brezillon wrote: > On Fri, 3 Mar 2017 13:36:29 +0100 > Alban wrote: > > > On Thu, 2 Mar 2017 22:18:03 +0100 > > Boris Brezillon wrote: > > > > > On Thu, 2 Mar 2017 20:50:22 +0100 > > > Alban wrote: > > > > > > [snip] > > > > [snip] > > > >

[REGRESSION][v4.9.y][v4.10.y] Input: ALPS - set DualPoint flag for 74 03 28 devices

Hi Ben, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit aeaa881f9b17823028b464893b89c42db797b717 Author: Ben Gamari Date: Tue Oct 4 11:43:30 2016 -0700 Input: ALPS

[REGRESSION][v4.9.y][v4.10.y] Input: ALPS - set DualPoint flag for 74 03 28 devices

Hi Ben, A kernel bug report was opened against Ubuntu [0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit aeaa881f9b17823028b464893b89c42db797b717 Author: Ben Gamari Date: Tue Oct 4 11:43:30 2016 -0700 Input: ALPS - set DualPoint flag

Re: [PATCH] fs/pstore: constify pstore_zbackend structures

On Sun, Feb 19, 2017 at 1:37 AM, Bhumika Goyal wrote: > The references of pstore_zbackend structures are stored into the > pointer zbackend of type struct pstore_zbackend. The pointer zbackend > can be made const as it is only dereferenced. After making this change > the

Re: [PATCH] fs/pstore: constify pstore_zbackend structures

On Sun, Feb 19, 2017 at 1:37 AM, Bhumika Goyal wrote: > The references of pstore_zbackend structures are stored into the > pointer zbackend of type struct pstore_zbackend. The pointer zbackend > can be made const as it is only dereferenced. After making this change > the pstore_zbackend

[PATCH 2/6] staging: speakup: simple_strtoul is replaced with kstrtoul

This patch fixes "simple_strtoul is obsolete, use kstrtoul instead" warning. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/kobjects.c| 4 ++-- drivers/staging/speakup/main.c| 2 +- drivers/staging/speakup/varhandlers.c | 2 +- 3 files

[PATCH 2/6] staging: speakup: simple_strtoul is replaced with kstrtoul

This patch fixes "simple_strtoul is obsolete, use kstrtoul instead" warning. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/kobjects.c| 4 ++-- drivers/staging/speakup/main.c| 2 +- drivers/staging/speakup/varhandlers.c | 2 +- 3 files changed, 4 insertions(+), 4

Re: [PATCH 4/4] tty/serial: sh-sci: remove uneeded IS_ERR_OR_NULL calls

Hello Geert, On Fri, Mar 03, 2017 at 08:21:05PM +0100, Geert Uytterhoeven wrote: > > diff --git a/drivers/tty/serial/sh-sci.c b/drivers/tty/serial/sh-sci.c > > index 91e7dddbf72c..2f4cdd4e7b4f 100644 > > --- a/drivers/tty/serial/sh-sci.c > > +++ b/drivers/tty/serial/sh-sci.c > > @@ -3022,7

Re: [PATCH 4/4] tty/serial: sh-sci: remove uneeded IS_ERR_OR_NULL calls

Hello Geert, On Fri, Mar 03, 2017 at 08:21:05PM +0100, Geert Uytterhoeven wrote: > > diff --git a/drivers/tty/serial/sh-sci.c b/drivers/tty/serial/sh-sci.c > > index 91e7dddbf72c..2f4cdd4e7b4f 100644 > > --- a/drivers/tty/serial/sh-sci.c > > +++ b/drivers/tty/serial/sh-sci.c > > @@ -3022,7

Re: [patch] mm, zoneinfo: print non-populated zones

On 03/03/2017 04:56 AM, David Rientjes wrote: > Initscripts can use the information (protection levels) from > /proc/zoneinfo to configure vm.lowmem_reserve_ratio at boot. > > vm.lowmem_reserve_ratio is an array of ratios for each configured zone on > the system. If a zone is not populated on an

Re: [patch] mm, zoneinfo: print non-populated zones

On 03/03/2017 04:56 AM, David Rientjes wrote: > Initscripts can use the information (protection levels) from > /proc/zoneinfo to configure vm.lowmem_reserve_ratio at boot. > > vm.lowmem_reserve_ratio is an array of ratios for each configured zone on > the system. If a zone is not populated on an

Re: [PATCH 01/10] x86: assembly, ENTRY for fn, GLOBAL for data

On March 1, 2017 2:27:54 AM PST, Ingo Molnar wrote: > >* Thomas Gleixner wrote: > >> On Wed, 1 Mar 2017, Ingo Molnar wrote: >> > >> > * Jiri Slaby wrote: >> > >> > > This is a start of series to unify use of ENTRY, ENDPROC, GLOBAL, >END,

Re: [PATCH 01/10] x86: assembly, ENTRY for fn, GLOBAL for data

On March 1, 2017 2:27:54 AM PST, Ingo Molnar wrote: > >* Thomas Gleixner wrote: > >> On Wed, 1 Mar 2017, Ingo Molnar wrote: >> > >> > * Jiri Slaby wrote: >> > >> > > This is a start of series to unify use of ENTRY, ENDPROC, GLOBAL, >END, >> > > and other macros across x86. When we have all

Re: [RFC PATCH 11/12] staging: android: ion: Make Ion heaps selectable

On 03/03/2017 02:33 AM, Daniel Vetter wrote: > On Thu, Mar 02, 2017 at 01:44:43PM -0800, Laura Abbott wrote: >> >> Currently, all heaps are compiled in all the time. In switching to >> a better platform model, let's allow these to be compiled out for good >> measure. >> >> Signed-off-by: Laura

Re: [RFC PATCH 11/12] staging: android: ion: Make Ion heaps selectable

On 03/03/2017 02:33 AM, Daniel Vetter wrote: > On Thu, Mar 02, 2017 at 01:44:43PM -0800, Laura Abbott wrote: >> >> Currently, all heaps are compiled in all the time. In switching to >> a better platform model, let's allow these to be compiled out for good >> measure. >> >> Signed-off-by: Laura

[PATCH 1/6] staging: speakup: Add blank line after function/struct/union/enum declarations

This patch fixes the warnings reported by checkpatch.pl for please use a blank line after function/struct/union/enum declarations. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 1 + drivers/staging/speakup/serialio.c | 1 +

[PATCH 1/6] staging: speakup: Add blank line after function/struct/union/enum declarations

This patch fixes the warnings reported by checkpatch.pl for please use a blank line after function/struct/union/enum declarations. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 1 + drivers/staging/speakup/serialio.c | 1 + drivers/staging/speakup/speakup_dtlk.c

[PATCH 07/10] Modified initialization code of VI sensing

Signed-off-by: Ryan Lee --- Initialization code of TX(VI sensing) had a problem for interleave mode configuration. Additional configuration for volume, DC blocker, Voltage/Current limit and ADC have been added. sound/soc/codecs/max98927.c | 195

[PATCH 07/10] Modified initialization code of VI sensing

Signed-off-by: Ryan Lee --- Initialization code of TX(VI sensing) had a problem for interleave mode configuration. Additional configuration for volume, DC blocker, Voltage/Current limit and ADC have been added. sound/soc/codecs/max98927.c | 195 +--- 1

Re: net: heap out-of-bounds in fib6_clean_node/rt6_fill_node/fib6_age/fib6_prune_clone

On 3/3/17 6:39 AM, Dmitry Vyukov wrote: > I am getting heap out-of-bounds reports in > fib6_clean_node/rt6_fill_node/fib6_age/fib6_prune_clone while running > syzkaller fuzzer on 86292b33d4b79ee03e2f43ea0381ef85f077c760. They all > follow the same pattern: an object of size 216 is allocated from >

Re: net: heap out-of-bounds in fib6_clean_node/rt6_fill_node/fib6_age/fib6_prune_clone

On 3/3/17 6:39 AM, Dmitry Vyukov wrote: > I am getting heap out-of-bounds reports in > fib6_clean_node/rt6_fill_node/fib6_age/fib6_prune_clone while running > syzkaller fuzzer on 86292b33d4b79ee03e2f43ea0381ef85f077c760. They all > follow the same pattern: an object of size 216 is allocated from >

Re: SUNRPC: Add generic helpers for xdr_stream encode/decode

Hi Trond, On Thu, Mar 2, 2017 at 2:04 AM, Linux Kernel Mailing List wrote: > Web: > https://git.kernel.org/torvalds/c/0ae060ca2bdfe11181094699b0f76437ec210b17 > Commit: 0ae060ca2bdfe11181094699b0f76437ec210b17 > Parent:

Re: SUNRPC: Add generic helpers for xdr_stream encode/decode

Hi Trond, On Thu, Mar 2, 2017 at 2:04 AM, Linux Kernel Mailing List wrote: > Web: > https://git.kernel.org/torvalds/c/0ae060ca2bdfe11181094699b0f76437ec210b17 > Commit: 0ae060ca2bdfe11181094699b0f76437ec210b17 > Parent: 9761a2469dc287c6d75ca148f4fc483becbcad88 > Refname:

[PATCH 6/6] staging: speakup: fixes braces {} should be used on all arms of this statement

This patch fixes the checks reported by checkpatch.pl for braces {} should be used on all arms of this statement. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 29 +++-- 1 file changed, 19 insertions(+), 10

[PATCH 6/6] staging: speakup: fixes braces {} should be used on all arms of this statement

This patch fixes the checks reported by checkpatch.pl for braces {} should be used on all arms of this statement. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 29 +++-- 1 file changed, 19 insertions(+), 10 deletions(-) diff --git

Re: [PATCH v3 2/3] x86/hyperv: move TSC reading method to asm/mshyperv.h

Minor coding comments > diff --git a/arch/x86/include/asm/mshyperv.h b/arch/x86/include/asm/mshyperv.h > index d324dce..4ff25436 100644 > --- a/arch/x86/include/asm/mshyperv.h > +++ b/arch/x86/include/asm/mshyperv.h > @@ -178,6 +178,56 @@ void hyperv_cleanup(void); > #endif > #ifdef

Re: [PATCH] drm/arcpgu: use .mode_fixup instead of .atomic_check

Hi Jose, On Fri, 2017-03-03 at 18:05 +, Jose Abreu wrote: > Hi Alexey, > > > On 03-03-2017 13:27, Alexey Brodkin wrote: > > > > > > So if I understood you correct here what I really need is just to get rid > > of existing check, > > right? I.e. the following is to be in v2 respin: > >

Re: [PATCH] drm/arcpgu: use .mode_fixup instead of .atomic_check

Hi Jose, On Fri, 2017-03-03 at 18:05 +, Jose Abreu wrote: > Hi Alexey, > > > On 03-03-2017 13:27, Alexey Brodkin wrote: > > > > > > So if I understood you correct here what I really need is just to get rid > > of existing check, > > right? I.e. the following is to be in v2 respin: > >

Re: [PATCH v3 2/3] x86/hyperv: move TSC reading method to asm/mshyperv.h

Minor coding comments > diff --git a/arch/x86/include/asm/mshyperv.h b/arch/x86/include/asm/mshyperv.h > index d324dce..4ff25436 100644 > --- a/arch/x86/include/asm/mshyperv.h > +++ b/arch/x86/include/asm/mshyperv.h > @@ -178,6 +178,56 @@ void hyperv_cleanup(void); > #endif > #ifdef

Re: [PATCH 4/4] tty/serial: sh-sci: remove uneeded IS_ERR_OR_NULL calls

Hi Uwe, On Fri, Mar 3, 2017 at 8:12 PM, Uwe Kleine-König wrote: > On Fri, Mar 03, 2017 at 07:58:36PM +0100, Geert Uytterhoeven wrote: >> On Fri, Mar 3, 2017 at 3:22 PM, Richard Genoud >> wrote: >> > Since commit 1d267ea6539f ("serial:

Re: [PATCH 4/4] tty/serial: sh-sci: remove uneeded IS_ERR_OR_NULL calls

Hi Uwe, On Fri, Mar 3, 2017 at 8:12 PM, Uwe Kleine-König wrote: > On Fri, Mar 03, 2017 at 07:58:36PM +0100, Geert Uytterhoeven wrote: >> On Fri, Mar 3, 2017 at 3:22 PM, Richard Genoud >> wrote: >> > Since commit 1d267ea6539f ("serial: mctrl-gpio: simplify init routine"), >> > the

Re: Is it really safe to use workqueues to drive expedited grace periods?

Hello, Paul. Sorry about the long delay. Travel + sickness. Just starting to catch up with things now. On Mon, Feb 13, 2017 at 04:16:00PM -0800, Paul E. McKenney wrote: > Thank you for the information! So if I am to continue using workqueues > for expedited RCU grace periods, I believe that

Re: Is it really safe to use workqueues to drive expedited grace periods?

Hello, Paul. Sorry about the long delay. Travel + sickness. Just starting to catch up with things now. On Mon, Feb 13, 2017 at 04:16:00PM -0800, Paul E. McKenney wrote: > Thank you for the information! So if I am to continue using workqueues > for expedited RCU grace periods, I believe that

Re: [PATCH v9 00/10] mux controller abstraction and iio/i2c muxes

> And conflicts -- if they show up -- will probably be trivial given the > nature of the series. Famous last words... Heh. I agree, though :) signature.asc Description: PGP signature

Re: [PATCH v9 00/10] mux controller abstraction and iio/i2c muxes

> And conflicts -- if they show up -- will probably be trivial given the > nature of the series. Famous last words... Heh. I agree, though :) signature.asc Description: PGP signature

Re: idr: use-after-free write in ida_get_new_above

On Fri, Mar 3, 2017 at 10:51 AM, Dmitry Vyukov wrote: > Hello, > > I am hitting the following use-after-free reports while running > syzkaller fuzzer on commit c82be9d2244aacea9851c86f4fb74694c99cd874: > > == >

Re: idr: use-after-free write in ida_get_new_above

On Fri, Mar 3, 2017 at 10:51 AM, Dmitry Vyukov wrote: > Hello, > > I am hitting the following use-after-free reports while running > syzkaller fuzzer on commit c82be9d2244aacea9851c86f4fb74694c99cd874: > > == > BUG: KASAN:

[PATCH 1/2] staging: media: Clean up tests if NULL returned on failure

Some functions like kmalloc/kzalloc return NULL on failure. When NULL represents failure, !x is commonly used. This was done using Coccinelle: @@ expression *e; identifier l1; @@ e = \(kmalloc\|kzalloc\|kcalloc\|devm_kzalloc\)(...); ... - e == NULL + !e Signed-off-by: simran singhal

[PATCH 1/2] staging: media: Clean up tests if NULL returned on failure

Some functions like kmalloc/kzalloc return NULL on failure. When NULL represents failure, !x is commonly used. This was done using Coccinelle: @@ expression *e; identifier l1; @@ e = \(kmalloc\|kzalloc\|kcalloc\|devm_kzalloc\)(...); ... - e == NULL + !e Signed-off-by: simran singhal ---

Re: [PATCH v17 2/3] usb: USB Type-C connector class

On 2017-03-03 13:59, Heikki Krogerus wrote: On Fri, Mar 03, 2017 at 08:29:18AM +0100, Mats Karrman wrote: How would something like that sound to you guys? Complicated... Need to marinate on that for a while ;) My system is a bit different. It's an i.MX6 SoC with the typec phy and DP

Re: [PATCH v17 2/3] usb: USB Type-C connector class

On 2017-03-03 13:59, Heikki Krogerus wrote: On Fri, Mar 03, 2017 at 08:29:18AM +0100, Mats Karrman wrote: How would something like that sound to you guys? Complicated... Need to marinate on that for a while ;) My system is a bit different. It's an i.MX6 SoC with the typec phy and DP

[PATCH 1/2] dt-bindings: mfd: Fix path to atmel/hlcdc-dc.txt

Atmel hlcdc-dc documentation is actually in Documentation/devicetree/bindings/display/atmel/hlcdc-dc.txt Signed-off-by: Richard Genoud --- Documentation/devicetree/bindings/mfd/atmel-hlcdc.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/2] dt-bindings: mfd: Fix path to atmel/hlcdc-dc.txt

Atmel hlcdc-dc documentation is actually in Documentation/devicetree/bindings/display/atmel/hlcdc-dc.txt Signed-off-by: Richard Genoud --- Documentation/devicetree/bindings/mfd/atmel-hlcdc.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [git pull] vfs.git statx

On Mar 2, 2017, at 9:31 PM, Al Viro wrote: > > statx: Add a system call to make enhanced file info available (2017-03-02 > 20:51:15 -0500) Yay! It is pretty rare that a merge request actually makes me smile, but I'm happy that this patch finally made it in. Thanks

Re: [git pull] vfs.git statx

On Mar 2, 2017, at 9:31 PM, Al Viro wrote: > > statx: Add a system call to make enhanced file info available (2017-03-02 > 20:51:15 -0500) Yay! It is pretty rare that a merge request actually makes me smile, but I'm happy that this patch finally made it in. Thanks David & Al for your

RE: [PATCH] qla2xxx: Fix ql_dump_buffer

> -Original Message- > From: Joe Perches [mailto:j...@perches.com] > Sent: Thursday, March 2, 2017 5:15 PM > To: qla2xxx-upstr...@qlogic.com > Cc: James E.J. Bottomley ; Martin K. Petersen > ; linux-s...@vger.kernel.org; linux- >

RE: [PATCH] qla2xxx: Fix ql_dump_buffer

> -Original Message- > From: Joe Perches [mailto:j...@perches.com] > Sent: Thursday, March 2, 2017 5:15 PM > To: qla2xxx-upstr...@qlogic.com > Cc: James E.J. Bottomley ; Martin K. Petersen > ; linux-s...@vger.kernel.org; linux- > ker...@vger.kernel.org > Subject: [PATCH] qla2xxx: Fix

[PATCH 0/2] Clean up tests if NULL returned on failure

This patch series tests if functions like kmalloc/kzalloc return NULL on failure. When NULL represents failure, !x is commonly used. simran singhal (2): staging: media: Clean up tests if NULL returned on failure staging: rtl8192e: Clean up tests if NULL returned on failure

Re: [PATCH v2] blkcg: allocate struct blkcg_gq outside request queue spinlock

Hello, Tahsin. On Thu, Mar 02, 2017 at 02:33:11PM -0800, Tahsin Erdogan wrote: > > And let blkg_create() verify these conditions after releasing and > > regrabbing the lock. > > > > This also means that the init path can simply pass in GFP_KERNEL. > > I tried that approach, but I encountered two

[PATCH 0/2] Clean up tests if NULL returned on failure

This patch series tests if functions like kmalloc/kzalloc return NULL on failure. When NULL represents failure, !x is commonly used. simran singhal (2): staging: media: Clean up tests if NULL returned on failure staging: rtl8192e: Clean up tests if NULL returned on failure

Re: [PATCH v2] blkcg: allocate struct blkcg_gq outside request queue spinlock

Hello, Tahsin. On Thu, Mar 02, 2017 at 02:33:11PM -0800, Tahsin Erdogan wrote: > > And let blkg_create() verify these conditions after releasing and > > regrabbing the lock. > > > > This also means that the init path can simply pass in GFP_KERNEL. > > I tried that approach, but I encountered two

Re: [PATCH v9 00/10] mux controller abstraction and iio/i2c muxes

On 2017-03-03 17:52, Wolfram Sang wrote: > >> Jonathan, Wolfram, do you have any preferences on how this should be >> coordinated regarding the new iio and i2c drivers (and iio changes)? > > You got the acks, all is fine, I think. > >> My plan is to at some point declare the branch immutable.

Re: [PATCH v9 00/10] mux controller abstraction and iio/i2c muxes

On 2017-03-03 17:52, Wolfram Sang wrote: > >> Jonathan, Wolfram, do you have any preferences on how this should be >> coordinated regarding the new iio and i2c drivers (and iio changes)? > > You got the acks, all is fine, I think. > >> My plan is to at some point declare the branch immutable.

[PATCH 2/2] staging: rtl8192e: Clean up tests if NULL returned on failure

Some functions like kmalloc/kzalloc return NULL on failure. When NULL represents failure, !x is commonly used. This was done using Coccinelle: @@ expression *e; identifier l1; @@ e = \(kmalloc\|kzalloc\|kcalloc\|devm_kzalloc\)(...); ... - e == NULL + !e Signed-off-by: simran singhal

[PATCH 2/2] staging: rtl8192e: Clean up tests if NULL returned on failure

Some functions like kmalloc/kzalloc return NULL on failure. When NULL represents failure, !x is commonly used. This was done using Coccinelle: @@ expression *e; identifier l1; @@ e = \(kmalloc\|kzalloc\|kcalloc\|devm_kzalloc\)(...); ... - e == NULL + !e Signed-off-by: simran singhal ---

Re: [PATCH 0/2] fix the traced mt-exec deadlock

Cc'd linux-api as we are talking about a deliberate user visible API change here. Oleg Nesterov writes: > On 03/02, Eric W. Biederman wrote: >> >> Oleg Nesterov writes: >> >> > our discussion was a bit confusing, and it seems that we did not >> > fully

Re: [PATCH 0/2] fix the traced mt-exec deadlock

Cc'd linux-api as we are talking about a deliberate user visible API change here. Oleg Nesterov writes: > On 03/02, Eric W. Biederman wrote: >> >> Oleg Nesterov writes: >> >> > our discussion was a bit confusing, and it seems that we did not >> > fully convince each other. So let me ask what

Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline

Hi Steve, On Thu, Mar 02, 2017 at 06:12:43PM -0800, Steve Longerbeam wrote: > > > On 03/02/2017 03:48 PM, Steve Longerbeam wrote: > > > > > >On 03/02/2017 08:02 AM, Sakari Ailus wrote: > >>Hi Steve, > >> > >>On Wed, Feb 15, 2017 at 06:19:16PM -0800, Steve Longerbeam wrote: >

Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline

Hi Steve, On Thu, Mar 02, 2017 at 06:12:43PM -0800, Steve Longerbeam wrote: > > > On 03/02/2017 03:48 PM, Steve Longerbeam wrote: > > > > > >On 03/02/2017 08:02 AM, Sakari Ailus wrote: > >>Hi Steve, > >> > >>On Wed, Feb 15, 2017 at 06:19:16PM -0800, Steve Longerbeam wrote: >

Re: [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

On 03/03/2017 08:45 AM, Laurent Pinchart wrote: > Hi Daniel, > > On Friday 03 Mar 2017 11:04:33 Daniel Vetter wrote: >> On Thu, Mar 02, 2017 at 01:44:32PM -0800, Laura Abbott wrote: >>> Hi, >>> >>> There's been some recent discussions[1] about Ion-like frameworks. There's >>> apparently interest

Re: [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

On 03/03/2017 08:45 AM, Laurent Pinchart wrote: > Hi Daniel, > > On Friday 03 Mar 2017 11:04:33 Daniel Vetter wrote: >> On Thu, Mar 02, 2017 at 01:44:32PM -0800, Laura Abbott wrote: >>> Hi, >>> >>> There's been some recent discussions[1] about Ion-like frameworks. There's >>> apparently interest

net/ipv4: division by 0 in tcp_select_window

Hello, The following program triggers division by 0 in tcp_select_window: https://gist.githubusercontent.com/dvyukov/ef28c0fd2ab57a655508ef7621b12e6c/raw/079011e2a9523a390b0621cbc1e5d9d5e637fd6d/gistfile1.txt divide error: [#1] SMP KASAN Modules linked in: CPU: 3 PID: 0 Comm: swapper/3 Not

net/ipv4: division by 0 in tcp_select_window

Hello, The following program triggers division by 0 in tcp_select_window: https://gist.githubusercontent.com/dvyukov/ef28c0fd2ab57a655508ef7621b12e6c/raw/079011e2a9523a390b0621cbc1e5d9d5e637fd6d/gistfile1.txt divide error: [#1] SMP KASAN Modules linked in: CPU: 3 PID: 0 Comm: swapper/3 Not

Re: [PATCH v11 2/9] mmc: cavium: Add core MMC driver for Cavium SOCs

On 03/03/2017 03:47 AM, Ulf Hansson wrote: On 6 February 2017 at 14:39, Jan Glauber wrote: [...] +} + +static void prepare_ext_dma(struct mmc_host *mmc, struct mmc_request *mrq, + union mio_emm_dma *emm_dma) +{ + struct cvm_mmc_slot *slot =

Re: [PATCH v11 2/9] mmc: cavium: Add core MMC driver for Cavium SOCs

On 03/03/2017 03:47 AM, Ulf Hansson wrote: On 6 February 2017 at 14:39, Jan Glauber wrote: [...] +} + +static void prepare_ext_dma(struct mmc_host *mmc, struct mmc_request *mrq, + union mio_emm_dma *emm_dma) +{ + struct cvm_mmc_slot *slot = mmc_priv(mmc); + +

Re: [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

On 03/03/2017 08:25 AM, Laurent Pinchart wrote: > Hi Laura, > > Thank you for the patches. > > On Thursday 02 Mar 2017 13:44:32 Laura Abbott wrote: >> Hi, >> >> There's been some recent discussions[1] about Ion-like frameworks. There's >> apparently interest in just keeping Ion since it works

Re: [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

On 03/03/2017 08:25 AM, Laurent Pinchart wrote: > Hi Laura, > > Thank you for the patches. > > On Thursday 02 Mar 2017 13:44:32 Laura Abbott wrote: >> Hi, >> >> There's been some recent discussions[1] about Ion-like frameworks. There's >> apparently interest in just keeping Ion since it works

Re: net: heap out-of-bounds in fib6_clean_node/rt6_fill_node/fib6_age/fib6_prune_clone

On Fri, Mar 3, 2017 at 8:12 PM, David Ahern wrote: > On 3/3/17 6:39 AM, Dmitry Vyukov wrote: >> I am getting heap out-of-bounds reports in >> fib6_clean_node/rt6_fill_node/fib6_age/fib6_prune_clone while running >> syzkaller fuzzer on

Re: net: heap out-of-bounds in fib6_clean_node/rt6_fill_node/fib6_age/fib6_prune_clone

On Fri, Mar 3, 2017 at 8:12 PM, David Ahern wrote: > On 3/3/17 6:39 AM, Dmitry Vyukov wrote: >> I am getting heap out-of-bounds reports in >> fib6_clean_node/rt6_fill_node/fib6_age/fib6_prune_clone while running >> syzkaller fuzzer on 86292b33d4b79ee03e2f43ea0381ef85f077c760. They all >> follow

Re: [PATCH 4/4] tty/serial: sh-sci: remove uneeded IS_ERR_OR_NULL calls

On Fri, Mar 03, 2017 at 07:58:36PM +0100, Geert Uytterhoeven wrote: > Hi Richard, > > On Fri, Mar 3, 2017 at 3:22 PM, Richard Genoud > wrote: > > Since commit 1d267ea6539f ("serial: mctrl-gpio: simplify init routine"), > > the mctrl_gpio_to_gpiod() function can't

Re: [PATCH 4/4] tty/serial: sh-sci: remove uneeded IS_ERR_OR_NULL calls

On Fri, Mar 03, 2017 at 07:58:36PM +0100, Geert Uytterhoeven wrote: > Hi Richard, > > On Fri, Mar 3, 2017 at 3:22 PM, Richard Genoud > wrote: > > Since commit 1d267ea6539f ("serial: mctrl-gpio: simplify init routine"), > > the mctrl_gpio_to_gpiod() function can't return an error anymore. > >

Re: [PATCH v17 2/3] usb: USB Type-C connector class

On 03/03/2017 04:59 AM, Heikki Krogerus wrote: Hi, On Fri, Mar 03, 2017 at 08:29:18AM +0100, Mats Karrman wrote: On 2017-03-03 04:13, Guenter Roeck wrote: On 03/02/2017 07:22 AM, Mats Karrman wrote: Looking forward, one thing I have run into is how to connect the typec driver with a

Re: [PATCH v17 2/3] usb: USB Type-C connector class

On 03/03/2017 04:59 AM, Heikki Krogerus wrote: Hi, On Fri, Mar 03, 2017 at 08:29:18AM +0100, Mats Karrman wrote: On 2017-03-03 04:13, Guenter Roeck wrote: On 03/02/2017 07:22 AM, Mats Karrman wrote: Looking forward, one thing I have run into is how to connect the typec driver with a

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