[PATCH] pinctrl/spear/plgpio: Delete two error messages for a failed memory allocation in plgpio_probe()

From: Markus Elfring Date: Wed, 27 Dec 2017 22:34:28 +0100 Omit extra messages for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH] pinctrl/spear/plgpio: Delete two error messages for a failed memory allocation in plgpio_probe()

From: Markus Elfring Date: Wed, 27 Dec 2017 22:34:28 +0100 Omit extra messages for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/pinctrl/spear/pinctrl-plgpio.c | 8 ++-- 1 file changed, 2

Re: lost connection to test machine (3)

Dmitry Vyukov wrote: > On Wed, Dec 27, 2017 at 7:18 PM, syzbot > wrote: > > Hello, > > > > syzkaller hit the following crash on > > beacbc68ac3e23821a681adb30b45dc55b17488d > >

Re: lost connection to test machine (3)

Dmitry Vyukov wrote: > On Wed, Dec 27, 2017 at 7:18 PM, syzbot > wrote: > > Hello, > > > > syzkaller hit the following crash on > > beacbc68ac3e23821a681adb30b45dc55b17488d > > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master > > compiler: gcc (GCC) 7.1.1 20170620 > >

Re: [RFC V7 2/2] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On Tue, Dec 26, 2017 at 10:45 PM, Viresh Kumar wrote: > On 26-12-17, 14:23, Rob Herring wrote: >> > cpu_opp_table: cpu_opp_table { >> > compatible = "operating-points-v2"; >> > opp-shared; >> > >> > opp00 { >> >

Re: [RFC V7 2/2] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On Tue, Dec 26, 2017 at 10:45 PM, Viresh Kumar wrote: > On 26-12-17, 14:23, Rob Herring wrote: >> > cpu_opp_table: cpu_opp_table { >> > compatible = "operating-points-v2"; >> > opp-shared; >> > >> > opp00 { >> >

[PATCH] Staging: ipx: fixed several no space before tabs coding style issues

Fixed several coding style warnings of "please, no space before tabs". Signed-off-by: Jianshen Liu --- drivers/staging/ipx/af_ipx.c| 56 - drivers/staging/ipx/ipx_proc.c | 2 +- drivers/staging/ipx/ipx_route.c | 6 ++--- 3 files

[PATCH] Staging: ipx: fixed several no space before tabs coding style issues

Fixed several coding style warnings of "please, no space before tabs". Signed-off-by: Jianshen Liu --- drivers/staging/ipx/af_ipx.c| 56 - drivers/staging/ipx/ipx_proc.c | 2 +- drivers/staging/ipx/ipx_route.c | 6 ++--- 3 files changed, 32

Re: [PATCH] dt: bindings: as3645a: Fix the example node

On Thu 2017-12-07 09:42:29, Rob Herring wrote: > On Wed, Dec 6, 2017 at 4:32 PM, Dan Murphy wrote: > > Rob > > > > On 12/06/2017 03:52 PM, Rob Herring wrote: > >> On Tue, Dec 05, 2017 at 07:36:37AM -0600, Dan Murphy wrote: > >>> Fix the address-cells and size-cells example node >

Re: [PATCH] dt: bindings: as3645a: Fix the example node

On Thu 2017-12-07 09:42:29, Rob Herring wrote: > On Wed, Dec 6, 2017 at 4:32 PM, Dan Murphy wrote: > > Rob > > > > On 12/06/2017 03:52 PM, Rob Herring wrote: > >> On Tue, Dec 05, 2017 at 07:36:37AM -0600, Dan Murphy wrote: > >>> Fix the address-cells and size-cells example node > >>> to reflect

Re: v4.15: camera problems on n900

On Wed, Dec 27, 2017 at 10:05:43PM +0100, Pavel Machek wrote: > Hi! > > In v4.14, back camera on N900 works. On v4.15-rc1.. it works for few > seconds, but then I get repeated oopses. > > On v4.15-rc0.5 (commit ed30b147e1f6e396e70a52dbb6c7d66befedd786), > camera does not start. > >

Re: v4.15: camera problems on n900

On Wed, Dec 27, 2017 at 10:05:43PM +0100, Pavel Machek wrote: > Hi! > > In v4.14, back camera on N900 works. On v4.15-rc1.. it works for few > seconds, but then I get repeated oopses. > > On v4.15-rc0.5 (commit ed30b147e1f6e396e70a52dbb6c7d66befedd786), > camera does not start. > >

Re: [PATCH] Device tree binding for Avago APDS990X light sensor

On Wed, Dec 27, 2017 at 09:01:47PM +0100, Pavel Machek wrote: > Hi! > > > > +Required properties: > > > +- compatible: "avago,apds990x" > > > +- reg: address on the I2C bus > > > +- interrupts: external interrupt line number > > > +- Vdd-supply: power supply for VDD > > > +- Vled-supply: power

Re: [PATCH] Device tree binding for Avago APDS990X light sensor

On Wed, Dec 27, 2017 at 09:01:47PM +0100, Pavel Machek wrote: > Hi! > > > > +Required properties: > > > +- compatible: "avago,apds990x" > > > +- reg: address on the I2C bus > > > +- interrupts: external interrupt line number > > > +- Vdd-supply: power supply for VDD > > > +- Vled-supply: power

Re: [PATCH] Device tree binding for Avago APDS990X light sensor

On Wed, Dec 27, 2017 at 07:50:42PM +0100, Filip Matijević wrote: > Hi Sakari, > > and thank you for your input - I've added a few comments below. > > On 12/27/2017 07:00 PM, Sakari Ailus wrote: > > Hi Pavel, > > > > Thanks for the patch. Please see my comments below. > > > > On Wed, Dec 27,

Re: [PATCH] Device tree binding for Avago APDS990X light sensor

On Wed, Dec 27, 2017 at 07:50:42PM +0100, Filip Matijević wrote: > Hi Sakari, > > and thank you for your input - I've added a few comments below. > > On 12/27/2017 07:00 PM, Sakari Ailus wrote: > > Hi Pavel, > > > > Thanks for the patch. Please see my comments below. > > > > On Wed, Dec 27,

[PATCH] pinctrl: msm: Delete an error message for a failed memory allocation in msm_pinctrl_probe()

From: Markus Elfring Date: Wed, 27 Dec 2017 22:04:22 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH] pinctrl: msm: Delete an error message for a failed memory allocation in msm_pinctrl_probe()

From: Markus Elfring Date: Wed, 27 Dec 2017 22:04:22 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/pinctrl/qcom/pinctrl-msm.c | 5 ++--- 1 file changed, 2

v4.15: camera problems on n900

Hi! In v4.14, back camera on N900 works. On v4.15-rc1.. it works for few seconds, but then I get repeated oopses. On v4.15-rc0.5 (commit ed30b147e1f6e396e70a52dbb6c7d66befedd786), camera does not start. Any ideas what might be wrong there?

v4.15: camera problems on n900

Hi! In v4.14, back camera on N900 works. On v4.15-rc1.. it works for few seconds, but then I get repeated oopses. On v4.15-rc0.5 (commit ed30b147e1f6e396e70a52dbb6c7d66befedd786), camera does not start. Any ideas what might be wrong there?

Re: [patch 2/4] nohz: Prevent erroneous tick stop invocations

On Wed, 27 Dec 2017, Thomas Gleixner wrote: > Bah, no. We need to move that into the nohz logic somehow to prevent that > repetitive expiry yesterday reprogramming. Lemme think about it some more. The patch below should be the proper cure. Thanks, tglx 8<--- Subject:

Re: [patch 2/4] nohz: Prevent erroneous tick stop invocations

On Wed, 27 Dec 2017, Thomas Gleixner wrote: > Bah, no. We need to move that into the nohz logic somehow to prevent that > repetitive expiry yesterday reprogramming. Lemme think about it some more. The patch below should be the proper cure. Thanks, tglx 8<--- Subject:

Re: [patch 0/4] timer/nohz: Fix timer/nohz woes

On Sat, 23 Dec 2017, Paul E. McKenney wrote: > diff --git a/kernel/time/timer.c b/kernel/time/timer.c > index ffebcf878fba..94cce780c574 100644 > --- a/kernel/time/timer.c > +++ b/kernel/time/timer.c > @@ -1875,6 +1875,7 @@ int timers_dead_cpu(unsigned int cpu) > >

Re: [patch 0/4] timer/nohz: Fix timer/nohz woes

On Sat, 23 Dec 2017, Paul E. McKenney wrote: > diff --git a/kernel/time/timer.c b/kernel/time/timer.c > index ffebcf878fba..94cce780c574 100644 > --- a/kernel/time/timer.c > +++ b/kernel/time/timer.c > @@ -1875,6 +1875,7 @@ int timers_dead_cpu(unsigned int cpu) > >

Re: [PATCH v6 00/11] Intel SGX Driver

Hi! > > Would you list guarantees provided by SGX? > > Obviously, confidentiality and integrity. SGX was designed to address > an Iago threat model, a very difficult challenge to address in > reality. Do you have link on "Iago threat model"? > I don't have the citation immediately available,

Re: [PATCH v6 00/11] Intel SGX Driver

Hi! > > Would you list guarantees provided by SGX? > > Obviously, confidentiality and integrity. SGX was designed to address > an Iago threat model, a very difficult challenge to address in > reality. Do you have link on "Iago threat model"? > I don't have the citation immediately available,

Re: [PATCH 3/4] libbpf: break loop earlier

Hello, On Wed, 2017-12-27 at 11:00 -0800, Alexei Starovoitov wrote: > On Wed, Dec 27, 2017 at 07:02:28PM +0100, Eric Leblond wrote: > > Get out of the loop when we have a match. > > > > Signed-off-by: Eric Leblond > > --- > > tools/lib/bpf/libbpf.c | 1 + > > 1 file changed, 1

Re: [PATCH 3/4] libbpf: break loop earlier

Hello, On Wed, 2017-12-27 at 11:00 -0800, Alexei Starovoitov wrote: > On Wed, Dec 27, 2017 at 07:02:28PM +0100, Eric Leblond wrote: > > Get out of the loop when we have a match. > > > > Signed-off-by: Eric Leblond > > --- > > tools/lib/bpf/libbpf.c | 1 + > > 1 file changed, 1 insertion(+) > >

Re: [PATCH v2] mtd: spi-nor: Added ISSI is25lp080d support

Hi Romain, Le 27/12/2017 à 15:46, Romain Porte a écrit : > On 27/12/2017 14:58, Romain Porte wrote: >> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c >> index 8bafd462f..18e826d36 100644 >> --- a/drivers/mtd/spi-nor/spi-nor.c >> +++ b/drivers/mtd/spi-nor/spi-nor.c >>

Re: [PATCH v2] mtd: spi-nor: Added ISSI is25lp080d support

Hi Romain, Le 27/12/2017 à 15:46, Romain Porte a écrit : > On 27/12/2017 14:58, Romain Porte wrote: >> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c >> index 8bafd462f..18e826d36 100644 >> --- a/drivers/mtd/spi-nor/spi-nor.c >> +++ b/drivers/mtd/spi-nor/spi-nor.c >>

Re: [PATCH v6 2/8] module: use relative references for __ksymtab entries

On 27 December 2017 at 20:13, Linus Torvalds wrote: > On Wed, Dec 27, 2017 at 12:11 PM, Ard Biesheuvel > wrote: >> >> I tried to keep the generic patches generic, so perhaps I should just >> put the arm64 vmlinux.lds.S change in a patch

Re: [PATCH v6 2/8] module: use relative references for __ksymtab entries

On 27 December 2017 at 20:13, Linus Torvalds wrote: > On Wed, Dec 27, 2017 at 12:11 PM, Ard Biesheuvel > wrote: >> >> I tried to keep the generic patches generic, so perhaps I should just >> put the arm64 vmlinux.lds.S change in a patch on its own? > > I guess it doesn't matter, but regardless

Re: [PATCHv3 0/2] capability controlled user-namespaces

Hello Mahesh, On 27 December 2017 at 18:09, Mahesh Bandewar (महेश बंडेवार) wrote: > Hello James, > > Seems like I missed your name to be added into the review of this > patch series. Would you be willing be pull this into the security > tree? Serge Hallyn has already ACKed

Re: [PATCHv3 0/2] capability controlled user-namespaces

Hello Mahesh, On 27 December 2017 at 18:09, Mahesh Bandewar (महेश बंडेवार) wrote: > Hello James, > > Seems like I missed your name to be added into the review of this > patch series. Would you be willing be pull this into the security > tree? Serge Hallyn has already ACKed it. We seem to have

Re: [PATCH 0/3] mtd: spi-nor: fix DMA-unsafe buffer issue between MTD and SPI

On Wed, 2017-12-27 at 10:36 +, Mark Brown wrote: > On Tue, Dec 26, 2017 at 06:45:28PM +, Trent Piepho wrote: > > > Or, since this only fixes instances of DMA-unsafe buffers used in > > access to SPI NOR flash chips, and since there are other SPI master > > interface users, those chip

Re: [PATCH 0/3] mtd: spi-nor: fix DMA-unsafe buffer issue between MTD and SPI

On Wed, 2017-12-27 at 10:36 +, Mark Brown wrote: > On Tue, Dec 26, 2017 at 06:45:28PM +, Trent Piepho wrote: > > > Or, since this only fixes instances of DMA-unsafe buffers used in > > access to SPI NOR flash chips, and since there are other SPI master > > interface users, those chip

Re: WARNING in strp_data_ready

On Wed, Dec 27, 2017 at 9:08 PM, Ozgur wrote: > > > 27.12.2017, 22:21, "Dmitry Vyukov" : >> On Wed, Dec 27, 2017 at 8:09 PM, Tom Herbert wrote: >>> Did you try the patch I posted? >> >> Hi Tom, > > Hello Dmitry, > >> No. And I didn't

Re: WARNING in strp_data_ready

On Wed, Dec 27, 2017 at 9:08 PM, Ozgur wrote: > > > 27.12.2017, 22:21, "Dmitry Vyukov" : >> On Wed, Dec 27, 2017 at 8:09 PM, Tom Herbert wrote: >>> Did you try the patch I posted? >> >> Hi Tom, > > Hello Dmitry, > >> No. And I didn't know I need to. Why? >> If you think the patch needs

Re: [PATCH v6 2/8] module: use relative references for __ksymtab entries

On Wed, Dec 27, 2017 at 12:11 PM, Ard Biesheuvel wrote: > > I tried to keep the generic patches generic, so perhaps I should just > put the arm64 vmlinux.lds.S change in a patch on its own? I guess it doesn't matter, but regardless of where it gets introduced I would

Re: [PATCH v6 2/8] module: use relative references for __ksymtab entries

On Wed, Dec 27, 2017 at 12:11 PM, Ard Biesheuvel wrote: > > I tried to keep the generic patches generic, so perhaps I should just > put the arm64 vmlinux.lds.S change in a patch on its own? I guess it doesn't matter, but regardless of where it gets introduced I would like to see the explanation

Re: [PATCH 11/12] drm/amd/powerplay: drop unneeded newline

On Wed, 27 Dec 2017, Michel Dänzer wrote: > On 2017-12-27 03:51 PM, Julia Lawall wrote: > > PP_ASSERT_WITH_CODE prints a newline at the end of the message string, > > so the message string does not need to include a newline explicitly. > > Done using Coccinelle. > > > > Signed-off-by: Julia

Re: [PATCH 11/12] drm/amd/powerplay: drop unneeded newline

On Wed, 27 Dec 2017, Michel Dänzer wrote: > On 2017-12-27 03:51 PM, Julia Lawall wrote: > > PP_ASSERT_WITH_CODE prints a newline at the end of the message string, > > so the message string does not need to include a newline explicitly. > > Done using Coccinelle. > > > > Signed-off-by: Julia

Re: [lkp-robot] [tpm] b008bd39b1: kmsg.tpm_tpm#:A_TPM_error(#)occurred_attempting_get_random

On Wed, Dec 27, 2017 at 10:55:32AM +0800, kernel test robot wrote: > caused below changes (please refer to attached dmesg/kmsg for entire > log/backtrace): > > [5.903660] tpm_tis 00:05: 1.2 TPM (device-id 0xFE, rev-id 70) > [5.934271] tpm tpm0: A TPM error (7) occurred attempting to

Re: [lkp-robot] [tpm] b008bd39b1: kmsg.tpm_tpm#:A_TPM_error(#)occurred_attempting_get_random

On Wed, Dec 27, 2017 at 10:55:32AM +0800, kernel test robot wrote: > caused below changes (please refer to attached dmesg/kmsg for entire > log/backtrace): > > [5.903660] tpm_tis 00:05: 1.2 TPM (device-id 0xFE, rev-id 70) > [5.934271] tpm tpm0: A TPM error (7) occurred attempting to

Re: [PATCH v6 2/8] module: use relative references for __ksymtab entries

On 27 December 2017 at 20:07, Linus Torvalds wrote: > On Wed, Dec 27, 2017 at 12:50 AM, Ard Biesheuvel > wrote: >> diff --git a/include/linux/compiler.h b/include/linux/compiler.h >> index 52e611ab9a6c..fe752d365334 100644 >> ---

Re: [PATCH v6 2/8] module: use relative references for __ksymtab entries

On 27 December 2017 at 20:07, Linus Torvalds wrote: > On Wed, Dec 27, 2017 at 12:50 AM, Ard Biesheuvel > wrote: >> diff --git a/include/linux/compiler.h b/include/linux/compiler.h >> index 52e611ab9a6c..fe752d365334 100644 >> --- a/include/linux/compiler.h >> +++ b/include/linux/compiler.h >> @@

Re: [PATCH v6 2/8] module: use relative references for __ksymtab entries

On Wed, Dec 27, 2017 at 12:50 AM, Ard Biesheuvel wrote: > diff --git a/include/linux/compiler.h b/include/linux/compiler.h > index 52e611ab9a6c..fe752d365334 100644 > --- a/include/linux/compiler.h > +++ b/include/linux/compiler.h > @@ -327,4 +327,15 @@ static

Re: [PATCH v6 2/8] module: use relative references for __ksymtab entries

On Wed, Dec 27, 2017 at 12:50 AM, Ard Biesheuvel wrote: > diff --git a/include/linux/compiler.h b/include/linux/compiler.h > index 52e611ab9a6c..fe752d365334 100644 > --- a/include/linux/compiler.h > +++ b/include/linux/compiler.h > @@ -327,4 +327,15 @@ static __always_inline void

Re: [PATCH] Device tree binding for Avago APDS990X light sensor

Hi! > > +Required properties: > > +- compatible: "avago,apds990x" > > +- reg: address on the I2C bus > > +- interrupts: external interrupt line number > > +- Vdd-supply: power supply for VDD > > +- Vled-supply: power supply for LEDA > > AFAIK the custom is to use lower case letters for regulator

Re: [PATCH] Device tree binding for Avago APDS990X light sensor

Hi! > > +Required properties: > > +- compatible: "avago,apds990x" > > +- reg: address on the I2C bus > > +- interrupts: external interrupt line number > > +- Vdd-supply: power supply for VDD > > +- Vled-supply: power supply for LEDA > > AFAIK the custom is to use lower case letters for regulator

Re: [PATCH v6 1/8] arch: enable relative relocations for arm64, power, x86, s390 and x86

On 27 December 2017 at 19:54, Linus Torvalds wrote: > On Wed, Dec 27, 2017 at 12:50 AM, Ard Biesheuvel > wrote: >> diff --git a/arch/arm64/kernel/vmlinux.lds.S >> b/arch/arm64/kernel/vmlinux.lds.S >> index 7da3e5c366a0..49ae5b43fe2b

Re: [PATCH v6 1/8] arch: enable relative relocations for arm64, power, x86, s390 and x86

On 27 December 2017 at 19:54, Linus Torvalds wrote: > On Wed, Dec 27, 2017 at 12:50 AM, Ard Biesheuvel > wrote: >> diff --git a/arch/arm64/kernel/vmlinux.lds.S >> b/arch/arm64/kernel/vmlinux.lds.S >> index 7da3e5c366a0..49ae5b43fe2b 100644 >> --- a/arch/arm64/kernel/vmlinux.lds.S >> +++

Re: [PATCH] x86-32: fix kexec with stack canary (CONFIG_CC_STACKPROTECTOR)

On Wed, 27 Dec 2017, Linus Torvalds wrote: > From: Linus Torvalds > Date: Wed, 27 Dec 2017 11:41:30 -0800 > Subject: [PATCH] x86-32: fix kexec with stack canary > (CONFIG_CC_STACKPROTECTOR) > > Commit e802a51ede91 ("x86/idt: Consolidate IDT invalidation") cleaned

Re: [PATCH] x86-32: fix kexec with stack canary (CONFIG_CC_STACKPROTECTOR)

On Wed, 27 Dec 2017, Linus Torvalds wrote: > From: Linus Torvalds > Date: Wed, 27 Dec 2017 11:41:30 -0800 > Subject: [PATCH] x86-32: fix kexec with stack canary > (CONFIG_CC_STACKPROTECTOR) > > Commit e802a51ede91 ("x86/idt: Consolidate IDT invalidation") cleaned up > and unified the IDT

Re: [PATCH v6 1/8] arch: enable relative relocations for arm64, power, x86, s390 and x86

On Wed, Dec 27, 2017 at 12:50 AM, Ard Biesheuvel wrote: > diff --git a/arch/arm64/kernel/vmlinux.lds.S b/arch/arm64/kernel/vmlinux.lds.S > index 7da3e5c366a0..49ae5b43fe2b 100644 > --- a/arch/arm64/kernel/vmlinux.lds.S > +++ b/arch/arm64/kernel/vmlinux.lds.S > @@ -156,7

Re: [PATCH v6 1/8] arch: enable relative relocations for arm64, power, x86, s390 and x86

On Wed, Dec 27, 2017 at 12:50 AM, Ard Biesheuvel wrote: > diff --git a/arch/arm64/kernel/vmlinux.lds.S b/arch/arm64/kernel/vmlinux.lds.S > index 7da3e5c366a0..49ae5b43fe2b 100644 > --- a/arch/arm64/kernel/vmlinux.lds.S > +++ b/arch/arm64/kernel/vmlinux.lds.S > @@ -156,7 +156,7 @@ SECTIONS >

[PATCH] x86-32: fix kexec with stack canary (CONFIG_CC_STACKPROTECTOR)

From: Linus Torvalds Date: Wed, 27 Dec 2017 11:41:30 -0800 Subject: [PATCH] x86-32: fix kexec with stack canary (CONFIG_CC_STACKPROTECTOR) Commit e802a51ede91 ("x86/idt: Consolidate IDT invalidation") cleaned up and unified the IDT invalidation that existed in a

Re: [RFC PATCH] mm: memcontrol: memory+swap accounting for cgroup-v2

Hi Tejun, In my previous messages, I think the message "memsw improves the performance of the job" might have been conveyed. Please ignore that. The message I want to express is the "memsw provides users the ability to consistently limit their job's memory (specifically anon memory) irrespective

[PATCH] x86-32: fix kexec with stack canary (CONFIG_CC_STACKPROTECTOR)

From: Linus Torvalds Date: Wed, 27 Dec 2017 11:41:30 -0800 Subject: [PATCH] x86-32: fix kexec with stack canary (CONFIG_CC_STACKPROTECTOR) Commit e802a51ede91 ("x86/idt: Consolidate IDT invalidation") cleaned up and unified the IDT invalidation that existed in a couple of places. It changed no

Re: [RFC PATCH] mm: memcontrol: memory+swap accounting for cgroup-v2

Hi Tejun, In my previous messages, I think the message "memsw improves the performance of the job" might have been conveyed. Please ignore that. The message I want to express is the "memsw provides users the ability to consistently limit their job's memory (specifically anon memory) irrespective

[PATCH 4/5] tracing: Fix crash when it fails to alloc ring buffer

From: Jing Xia Double free of the ring buffer happens when it fails to alloc new ring buffer instance for max_buffer if TRACER_MAX_TRACE is configured. The root cause is that the pointer is not set to NULL after the buffer is freed in allocate_trace_buffers(), and the

[PATCH 4/5] tracing: Fix crash when it fails to alloc ring buffer

From: Jing Xia Double free of the ring buffer happens when it fails to alloc new ring buffer instance for max_buffer if TRACER_MAX_TRACE is configured. The root cause is that the pointer is not set to NULL after the buffer is freed in allocate_trace_buffers(), and the freeing of the ring buffer

[PATCH 5/5] tracing: Fix possible double free on failure of allocating trace buffer

From: "Steven Rostedt (VMware)" Jing Xia and Chunyan Zhang reported that on failing to allocate part of the tracing buffer, memory is freed, but the pointers that point to them are not initialized back to NULL, and later paths may try to free the freed memory again. Jing and

[PATCH 2/5] tracing: Remove extra zeroing out of the ring buffer page

From: "Steven Rostedt (VMware)" The ring_buffer_read_page() takes care of zeroing out any extra data in the page that it returns. There's no need to zero it out again from the consumer. It was removed from one consumer of this function, but read_buffers_splice_read() did not

[PATCH 5/5] tracing: Fix possible double free on failure of allocating trace buffer

From: "Steven Rostedt (VMware)" Jing Xia and Chunyan Zhang reported that on failing to allocate part of the tracing buffer, memory is freed, but the pointers that point to them are not initialized back to NULL, and later paths may try to free the freed memory again. Jing and Chunyan fixed one of

[PATCH 2/5] tracing: Remove extra zeroing out of the ring buffer page

From: "Steven Rostedt (VMware)" The ring_buffer_read_page() takes care of zeroing out any extra data in the page that it returns. There's no need to zero it out again from the consumer. It was removed from one consumer of this function, but read_buffers_splice_read() did not remove it, and

[PATCH 3/5] ring-buffer: Do no reuse reader page if still in use

From: "Steven Rostedt (VMware)" To free the reader page that is allocated with ring_buffer_alloc_read_page(), ring_buffer_free_read_page() must be called. For faster performance, this page can be reused by the ring buffer to avoid having to free and allocate new pages. The

Re: [PATCH V1 0/1] Fix kernel panic caused by device ID duplication presented to the IOMMU

Hi Robin, On Tue, Dec 19, 2017 at 04:34:46PM +, Robin Murphy wrote: > Hi Tomasz, > > On 19/12/17 15:13, Tomasz Nowicki wrote: > >Here is my lspci output of ThunderX2 for which I am observing kernel panic > >coming from > >SMMUv3 driver -> arm_smmu_write_strtab_ent() -> BUG_ON(ste_live): > >

[PATCH 0/5] [GIT PULL] tracing: Bug fixes for 4.15 and earlier

Linus, While doing tests on tracing over the network, I found that the packets were getting corrupted. In the process I found three bugs. One was the culprit, but the other two scared me. After deeper investigation, they were not as major as I thought they were, due to a signed compared to an

Re: [PATCH 2/2] ARM: dts: imx6: RDU2: correct RTC compatible

On Wed, Dec 27, 2017 at 3:11 AM, Fabio Estevam wrote: > Hi Andrey, > > On Wed, Dec 27, 2017 at 1:56 AM, Andrey Smirnov > wrote: >> The RTC is manufactured by Maxim. This is a cosmetic fix, as Linux >> doesn't match the vendor string for i2c devices.

[PATCH 1/5] ring-buffer: Mask out the info bits when returning buffer page length

From: "Steven Rostedt (VMware)" Two info bits were added to the "commit" part of the ring buffer data page when returned to be consumed. This was to inform the user space readers that events have been missed, and that the count may be stored at the end of the page. What

[PATCH 3/5] ring-buffer: Do no reuse reader page if still in use

From: "Steven Rostedt (VMware)" To free the reader page that is allocated with ring_buffer_alloc_read_page(), ring_buffer_free_read_page() must be called. For faster performance, this page can be reused by the ring buffer to avoid having to free and allocate new pages. The issue arises when the

Re: [PATCH V1 0/1] Fix kernel panic caused by device ID duplication presented to the IOMMU

Hi Robin, On Tue, Dec 19, 2017 at 04:34:46PM +, Robin Murphy wrote: > Hi Tomasz, > > On 19/12/17 15:13, Tomasz Nowicki wrote: > >Here is my lspci output of ThunderX2 for which I am observing kernel panic > >coming from > >SMMUv3 driver -> arm_smmu_write_strtab_ent() -> BUG_ON(ste_live): > >

[PATCH 0/5] [GIT PULL] tracing: Bug fixes for 4.15 and earlier

Linus, While doing tests on tracing over the network, I found that the packets were getting corrupted. In the process I found three bugs. One was the culprit, but the other two scared me. After deeper investigation, they were not as major as I thought they were, due to a signed compared to an

Re: [PATCH 2/2] ARM: dts: imx6: RDU2: correct RTC compatible

On Wed, Dec 27, 2017 at 3:11 AM, Fabio Estevam wrote: > Hi Andrey, > > On Wed, Dec 27, 2017 at 1:56 AM, Andrey Smirnov > wrote: >> The RTC is manufactured by Maxim. This is a cosmetic fix, as Linux >> doesn't match the vendor string for i2c devices. >> >> Cc: Sascha Hauer >> Cc: Fabio Estevam

[PATCH 1/5] ring-buffer: Mask out the info bits when returning buffer page length

From: "Steven Rostedt (VMware)" Two info bits were added to the "commit" part of the ring buffer data page when returned to be consumed. This was to inform the user space readers that events have been missed, and that the count may be stored at the end of the page. What wasn't handled, was the

[PATCH 1/4] phy: usb: phy-brcm-usb: Fix two DT properties to match bindings doc

Change "brcm,has_xhci" and "brcm,has_eohci" device tree properties to the preferred "brcm,has-xhci" and "brcm,has-eohci". This also matches the existing device tree bindings document. Fixes: 49859e55e364 ("phy: usb: phy-brcm-usb: Add Broadcom STB USB phy driver") Signed-off-by: Al Cooper

[PATCH 2/4] phy: usb: phy-brcm-usb-init: Some Low Speed keyboards fail on 7271

From: Al Cooper Enable the the Low Speed Keep Alive signal on the 7271b0 by setting the LS_KEEP_ALIVE bit in the USB CTRL OBRIDGE register otherwise some Dell Low Speed keyboards fail. Also do a little cleanup of the EBRIDGE ESTOP_SCB_REQ bit. Since this is only used on

[PATCH 0/4] Bug fixes for the Broadcom STB USB phy driver

This patchset contains a series of bug fixes for the Broadcom STB USB phy driver. Al Cooper (4): phy: usb: phy-brcm-usb: Fix two DT properties to match bindings doc phy: usb: phy-brcm-usb-init: Some Low Speed keyboards fail on 7271 phy: usb: phy-brcm-usb-init: Power down USB 3.0 PHY when

[PATCH 1/4] phy: usb: phy-brcm-usb: Fix two DT properties to match bindings doc

Change "brcm,has_xhci" and "brcm,has_eohci" device tree properties to the preferred "brcm,has-xhci" and "brcm,has-eohci". This also matches the existing device tree bindings document. Fixes: 49859e55e364 ("phy: usb: phy-brcm-usb: Add Broadcom STB USB phy driver") Signed-off-by: Al Cooper ---

[PATCH 2/4] phy: usb: phy-brcm-usb-init: Some Low Speed keyboards fail on 7271

From: Al Cooper Enable the the Low Speed Keep Alive signal on the 7271b0 by setting the LS_KEEP_ALIVE bit in the USB CTRL OBRIDGE register otherwise some Dell Low Speed keyboards fail. Also do a little cleanup of the EBRIDGE ESTOP_SCB_REQ bit. Since this is only used on one platform, remove it

[PATCH 0/4] Bug fixes for the Broadcom STB USB phy driver

This patchset contains a series of bug fixes for the Broadcom STB USB phy driver. Al Cooper (4): phy: usb: phy-brcm-usb: Fix two DT properties to match bindings doc phy: usb: phy-brcm-usb-init: Some Low Speed keyboards fail on 7271 phy: usb: phy-brcm-usb-init: Power down USB 3.0 PHY when

[PATCH 3/4] phy: usb: phy-brcm-usb-init: Power down USB 3.0 PHY when XHCI disabled

From: Al Cooper Set PHY3_IDDQ_OVERRIDE in the xhci uninit routine. This will save additional power when the XHCI driver is not enabled. Fixes: 49859e55e364 ("phy: usb: phy-brcm-usb: Add Broadcom STB USB phy driver") Signed-off-by: Al Cooper ---

[PATCH 4/4] phy: usb: phy-brcm-usb-init: DRD mode can cause crash on startup

From: Al Cooper This is caused by a bug in the BDC core. When the BDC core comes out of reset and it's not selected, it gets a backup clock. When the BDC core is selected, it get's the main clock. If HOST mode is then selected the BDC core has the main clock shut off but

Re: [PATCH 1/2] ARM: dts: imx6: RDU2: disable internal watchdog

On Wed, Dec 27, 2017 at 3:09 AM, Fabio Estevam wrote: > Hi Andrey, > > On Wed, Dec 27, 2017 at 1:56 AM, Andrey Smirnov > wrote: >> The system has an external watchdog in the environment processor >> so the internal watchdog is of no use. >> >> Cc:

[PATCH 3/4] phy: usb: phy-brcm-usb-init: Power down USB 3.0 PHY when XHCI disabled

From: Al Cooper Set PHY3_IDDQ_OVERRIDE in the xhci uninit routine. This will save additional power when the XHCI driver is not enabled. Fixes: 49859e55e364 ("phy: usb: phy-brcm-usb: Add Broadcom STB USB phy driver") Signed-off-by: Al Cooper --- drivers/phy/broadcom/phy-brcm-usb-init.c | 2 ++

[PATCH 4/4] phy: usb: phy-brcm-usb-init: DRD mode can cause crash on startup

From: Al Cooper This is caused by a bug in the BDC core. When the BDC core comes out of reset and it's not selected, it gets a backup clock. When the BDC core is selected, it get's the main clock. If HOST mode is then selected the BDC core has the main clock shut off but the backup clock is not

Re: [PATCH 1/2] ARM: dts: imx6: RDU2: disable internal watchdog

On Wed, Dec 27, 2017 at 3:09 AM, Fabio Estevam wrote: > Hi Andrey, > > On Wed, Dec 27, 2017 at 1:56 AM, Andrey Smirnov > wrote: >> The system has an external watchdog in the environment processor >> so the internal watchdog is of no use. >> >> Cc: Sascha Hauer >> Cc: Fabio Estevam >> Cc: Rob

Re: WARNING in strp_data_ready

On Wed, Dec 27, 2017 at 8:09 PM, Tom Herbert wrote: > Did you try the patch I posted? Hi Tom, No. And I didn't know I need to. Why? If you think the patch needs additional testing, you can ask syzbot to test it. See

Re: WARNING in strp_data_ready

On Wed, Dec 27, 2017 at 8:09 PM, Tom Herbert wrote: > Did you try the patch I posted? Hi Tom, No. And I didn't know I need to. Why? If you think the patch needs additional testing, you can ask syzbot to test it. See

[PATCH v3 bpf-next 1/2] tools/bpftool: use version from the kernel source tree

Bpftool determines it's own version based on the kernel version, which is picked from the linux/version.h header. It's strange to use the version of the installed kernel headers, and makes much more sense to use the version of the actual source tree, where bpftool sources are. Fix this by

[PATCH v3 bpf-next 1/2] tools/bpftool: use version from the kernel source tree

Bpftool determines it's own version based on the kernel version, which is picked from the linux/version.h header. It's strange to use the version of the installed kernel headers, and makes much more sense to use the version of the actual source tree, where bpftool sources are. Fix this by

[PATCH v3 bpf-next 2/2] tools/bpftool: fix bpftool build with bintutils >= 2.9

Bpftool build is broken with binutils version 2.29 and later. The cause is commit 003ca0fd2286 ("Refactor disassembler selection") in the binutils repo, which changed the disassembler() function signature. Fix this by adding a new "feature" to the tools/build/features infrastructure and make it

[PATCH v3 bpf-next 2/2] tools/bpftool: fix bpftool build with bintutils >= 2.9

Bpftool build is broken with binutils version 2.29 and later. The cause is commit 003ca0fd2286 ("Refactor disassembler selection") in the binutils repo, which changed the disassembler() function signature. Fix this by adding a new "feature" to the tools/build/features infrastructure and make it

Re: WARNING in strp_data_ready

Did you try the patch I posted? On Wed, Dec 27, 2017 at 10:25 AM, Dmitry Vyukov wrote: > On Wed, Dec 6, 2017 at 4:44 PM, Dmitry Vyukov wrote: >>> wrote: On 10/24/2017 08:20 AM, syzbot wrote: > Hello, > >

Re: Donation

I Mikhail Fridman. has selected you specially as one of my beneficiaries for my Charitable Donation, Just as I have declared on May 23, 2016 to give my fortune as charity. Check the link below for confirmation:

Re: WARNING in strp_data_ready

Did you try the patch I posted? On Wed, Dec 27, 2017 at 10:25 AM, Dmitry Vyukov wrote: > On Wed, Dec 6, 2017 at 4:44 PM, Dmitry Vyukov wrote: >>> wrote: On 10/24/2017 08:20 AM, syzbot wrote: > Hello, > > syzkaller hit the following crash on >

Re: Donation

I Mikhail Fridman. has selected you specially as one of my beneficiaries for my Charitable Donation, Just as I have declared on May 23, 2016 to give my fortune as charity. Check the link below for confirmation:

Re: [PATCH v2 bpf-next 2/2] tools/bpftool: fix bpftool build with bintutils >= 2.8

On Tue, Dec 26, 2017 at 06:32:05PM -0800, Alexei Starovoitov wrote: > On Fri, Dec 22, 2017 at 06:50:01PM +, Quentin Monnet wrote: > > Hi Roman, > > > > 2017-12-22 16:11 UTC+ ~ Roman Gushchin > > > Bpftool build is broken with binutils version 2.28 and later. > > > > Could

Re: [PATCH v2 bpf-next 2/2] tools/bpftool: fix bpftool build with bintutils >= 2.8

On Tue, Dec 26, 2017 at 06:32:05PM -0800, Alexei Starovoitov wrote: > On Fri, Dec 22, 2017 at 06:50:01PM +, Quentin Monnet wrote: > > Hi Roman, > > > > 2017-12-22 16:11 UTC+ ~ Roman Gushchin > > > Bpftool build is broken with binutils version 2.28 and later. > > > > Could you check the

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