/spi-spi-geni-qcom-Add-SPI-driver-support-for-GENI-based-QUP/20180824-190528
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
config: i386-allmodconfig
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
make ARCH=i386 allmodconfig
make ARCH=i386
All
/spi-spi-geni-qcom-Add-SPI-driver-support-for-GENI-based-QUP/20180824-190528
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
config: i386-allmodconfig
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
make ARCH=i386 allmodconfig
make ARCH=i386
All
On Fri, Aug 24, 2018 at 01:47:10PM -0500, Brijesh Singh wrote:
> I am more inclined towards creating a new section with PMD aligned and
> sized. This section will contains the decrypted data. In early
> boot code we will update the mapping with C=0. If caller wants to create
> a shared variable
On Fri, Aug 24, 2018 at 01:47:10PM -0500, Brijesh Singh wrote:
> I am more inclined towards creating a new section with PMD aligned and
> sized. This section will contains the decrypted data. In early
> boot code we will update the mapping with C=0. If caller wants to create
> a shared variable
On Fri, Aug 24, 2018 at 7:29 PM, wrote:
>
>
> On August 24, 2018 5:58:43 PM PDT, Linus Torvalds
> wrote:
>>Adding a few people to the cc.
>>
>>On Fri, Aug 24, 2018 at 1:24 PM Nadav Amit
>>wrote:
>>> >
>>> > Can you actually find something that changes the fixmaps after boot
>>> > (again,
On Fri, Aug 24, 2018 at 7:29 PM, wrote:
>
>
> On August 24, 2018 5:58:43 PM PDT, Linus Torvalds
> wrote:
>>Adding a few people to the cc.
>>
>>On Fri, Aug 24, 2018 at 1:24 PM Nadav Amit
>>wrote:
>>> >
>>> > Can you actually find something that changes the fixmaps after boot
>>> > (again,
/sys/devices/system/cpu/cpuX/microcode
Before:
-r processor_flags
-r version
After:
-r--r--r-- processor_flags
-r--r--r-- version
Microcode version has been already readable for non root users via
/proc/cpuinfo. However it is easier to access it from
/sys/devices/system/cpu/cpuX/microcode
Before:
-r processor_flags
-r version
After:
-r--r--r-- processor_flags
-r--r--r-- version
Microcode version has been already readable for non root users via
/proc/cpuinfo. However it is easier to access it from
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 33e17876ea4edcd7f5c01efa78e8d02889261abf
commit: 0fbe9a245c60bedebb6dd329966f463bb724450a microblaze: add endianness
options to LDFLAGS instead of LD
date: 4 weeks ago
config: microblaze-allyesconfig
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 33e17876ea4edcd7f5c01efa78e8d02889261abf
commit: 0fbe9a245c60bedebb6dd329966f463bb724450a microblaze: add endianness
options to LDFLAGS instead of LD
date: 4 weeks ago
config: microblaze-allyesconfig
On 8/24/18 6:26 PM, Vinson Lee wrote:
Include linux/in6.h for struct in6_addr.
/usr/include/linux/rds.h:156:18: error: field ‘laddr’ has incomplete type
struct in6_addr laddr;
^
/usr/include/linux/rds.h:157:18: error: field ‘faddr’ has incomplete type
struct
On 8/24/18 6:26 PM, Vinson Lee wrote:
Include linux/in6.h for struct in6_addr.
/usr/include/linux/rds.h:156:18: error: field ‘laddr’ has incomplete type
struct in6_addr laddr;
^
/usr/include/linux/rds.h:157:18: error: field ‘faddr’ has incomplete type
struct
On 7/11/2018 10:37 PM, Kirill Tkhai Wrote:
> Hi,
>
> I'm observing "KASAN: use-after-free Read in shrink_slab" on recent
> linux-next in the code I've added:
>
> https://syzkaller.appspot.com/bug?id=91767fc6346a4b9e0309a8cd7e2f356c434450b9
>
> It seems to be not related to my patchset, since
On 7/11/2018 10:37 PM, Kirill Tkhai Wrote:
> Hi,
>
> I'm observing "KASAN: use-after-free Read in shrink_slab" on recent
> linux-next in the code I've added:
>
> https://syzkaller.appspot.com/bug?id=91767fc6346a4b9e0309a8cd7e2f356c434450b9
>
> It seems to be not related to my patchset, since
On Sat, 25 Aug 2018 10:45:09 +0900
Masami Hiramatsu wrote:
> On Fri, 24 Aug 2018 19:23:52 -0400
> Steven Rostedt wrote:
>
> > On Fri, 17 Aug 2018 01:40:30 +0900
> > Masami Hiramatsu wrote:
> >
> > > Add a testcase for max stack tracer, which checks basic
> > > max stack usage tracing and
On Sat, 25 Aug 2018 10:45:09 +0900
Masami Hiramatsu wrote:
> On Fri, 24 Aug 2018 19:23:52 -0400
> Steven Rostedt wrote:
>
> > On Fri, 17 Aug 2018 01:40:30 +0900
> > Masami Hiramatsu wrote:
> >
> > > Add a testcase for max stack tracer, which checks basic
> > > max stack usage tracing and
On August 24, 2018 5:58:43 PM PDT, Linus Torvalds
wrote:
>Adding a few people to the cc.
>
>On Fri, Aug 24, 2018 at 1:24 PM Nadav Amit
>wrote:
>> >
>> > Can you actually find something that changes the fixmaps after boot
>> > (again, ignoring kmap)?
>>
>> At least the alternatives mechanism
On August 24, 2018 5:58:43 PM PDT, Linus Torvalds
wrote:
>Adding a few people to the cc.
>
>On Fri, Aug 24, 2018 at 1:24 PM Nadav Amit
>wrote:
>> >
>> > Can you actually find something that changes the fixmaps after boot
>> > (again, ignoring kmap)?
>>
>> At least the alternatives mechanism
On Fri, 17 Aug 2018 01:44:18 +0900
Masami Hiramatsu wrote:
> Add a basic testcase for blktrace. For making it portable,
> this test uses a loop device.
blktrace is a bit special, as it's maintained by the block subsystem
and not really truly part of ftrace. It lives in the tracing directory,
On Fri, 17 Aug 2018 01:44:18 +0900
Masami Hiramatsu wrote:
> Add a basic testcase for blktrace. For making it portable,
> this test uses a loop device.
blktrace is a bit special, as it's maintained by the block subsystem
and not really truly part of ftrace. It lives in the tracing directory,
On Fri, 17 Aug 2018 01:43:49 +0900
Masami Hiramatsu wrote:
> Add a testcase for tracing output format using trace_marker.
> This tests raw, hex and bin format output.
I'd like to deprecate these formats. They are useless ever since we
implemented trace_pipe_raw.
Let's not add this test.
On Fri, 17 Aug 2018 01:43:49 +0900
Masami Hiramatsu wrote:
> Add a testcase for tracing output format using trace_marker.
> This tests raw, hex and bin format output.
I'd like to deprecate these formats. They are useless ever since we
implemented trace_pipe_raw.
Let's not add this test.
On Fri, 17 Aug 2018 01:43:20 +0900
Masami Hiramatsu wrote:
> Add a testcase for tracing_cpumask with function tracer.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../selftests/ftrace/test.d/ftrace/func_cpumask.tc | 34
>
> 1 file changed, 34 insertions(+)
> create
On Fri, 17 Aug 2018 01:43:20 +0900
Masami Hiramatsu wrote:
> Add a testcase for tracing_cpumask with function tracer.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../selftests/ftrace/test.d/ftrace/func_cpumask.tc | 34
>
> 1 file changed, 34 insertions(+)
> create
On Fri, 17 Aug 2018 01:42:52 +0900
Masami Hiramatsu wrote:
> Add a testcase for wakeup_rt tracer. This requires chrt
> command to test.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../selftests/ftrace/test.d/tracer/wakeup_rt.tc| 25
>
> 1 file changed, 25
On Fri, 17 Aug 2018 01:42:52 +0900
Masami Hiramatsu wrote:
> Add a testcase for wakeup_rt tracer. This requires chrt
> command to test.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../selftests/ftrace/test.d/tracer/wakeup_rt.tc| 25
>
> 1 file changed, 25
On Fri, 24 Aug 2018 22:42:11 +1000
Stephen Rothwell wrote:
> Hi Masami,
>
> On Fri, 24 Aug 2018 20:47:56 +0900 Masami Hiramatsu
> wrote:
> >
> > gcc-7.3.0 cross build ld shows below warnings.
> >
> > MODPOST vmlinux.o
> > /opt/gcc-7.3.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld:
On Fri, 24 Aug 2018 22:42:11 +1000
Stephen Rothwell wrote:
> Hi Masami,
>
> On Fri, 24 Aug 2018 20:47:56 +0900 Masami Hiramatsu
> wrote:
> >
> > gcc-7.3.0 cross build ld shows below warnings.
> >
> > MODPOST vmlinux.o
> > /opt/gcc-7.3.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld:
On Fri, 24 Aug 2018 17:52:11 -0400
Steven Rostedt wrote:
> On Fri, 17 Aug 2018 01:34:23 +0900
> Masami Hiramatsu wrote:
>
> > Use raw loopback address instead of localhost, because
> > "localhost" can depend on nsswitch and in some case
> > we can not resolve the localhost.
> >
> >
On Fri, 24 Aug 2018 17:52:11 -0400
Steven Rostedt wrote:
> On Fri, 17 Aug 2018 01:34:23 +0900
> Masami Hiramatsu wrote:
>
> > Use raw loopback address instead of localhost, because
> > "localhost" can depend on nsswitch and in some case
> > we can not resolve the localhost.
> >
> >
On Fri, 24 Aug 2018 19:23:52 -0400
Steven Rostedt wrote:
> On Fri, 17 Aug 2018 01:40:30 +0900
> Masami Hiramatsu wrote:
>
> > Add a testcase for max stack tracer, which checks basic
> > max stack usage tracing and its filter feature.
> >
> > Signed-off-by: Masami Hiramatsu
> > ---
> >
On Fri, 24 Aug 2018 19:23:52 -0400
Steven Rostedt wrote:
> On Fri, 17 Aug 2018 01:40:30 +0900
> Masami Hiramatsu wrote:
>
> > Add a testcase for max stack tracer, which checks basic
> > max stack usage tracing and its filter feature.
> >
> > Signed-off-by: Masami Hiramatsu
> > ---
> >
On Sat, 25 Aug 2018 10:35:13 +0900
Masami Hiramatsu wrote:
> On Fri, 24 Aug 2018 16:37:37 -0400
> Steven Rostedt wrote:
>
> > On Fri, 17 Aug 2018 01:30:36 +0900
> > Masami Hiramatsu wrote:
> >
> > > Add --console hidden option for debug test cases.
> > > This option allows to put "sh" or
On Sat, 25 Aug 2018 10:35:13 +0900
Masami Hiramatsu wrote:
> On Fri, 24 Aug 2018 16:37:37 -0400
> Steven Rostedt wrote:
>
> > On Fri, 17 Aug 2018 01:30:36 +0900
> > Masami Hiramatsu wrote:
> >
> > > Add --console hidden option for debug test cases.
> > > This option allows to put "sh" or
On Fri, 24 Aug 2018 16:37:37 -0400
Steven Rostedt wrote:
> On Fri, 17 Aug 2018 01:30:36 +0900
> Masami Hiramatsu wrote:
>
> > Add --console hidden option for debug test cases.
> > This option allows to put "sh" or something else
> > when the test case hits a bug.
>
> Can you add more
On Fri, 24 Aug 2018 16:37:37 -0400
Steven Rostedt wrote:
> On Fri, 17 Aug 2018 01:30:36 +0900
> Masami Hiramatsu wrote:
>
> > Add --console hidden option for debug test cases.
> > This option allows to put "sh" or something else
> > when the test case hits a bug.
>
> Can you add more
Include linux/in6.h for struct in6_addr.
/usr/include/linux/rds.h:156:18: error: field ‘laddr’ has incomplete type
struct in6_addr laddr;
^
/usr/include/linux/rds.h:157:18: error: field ‘faddr’ has incomplete type
struct in6_addr faddr;
^
Include linux/in6.h for struct in6_addr.
/usr/include/linux/rds.h:156:18: error: field ‘laddr’ has incomplete type
struct in6_addr laddr;
^
/usr/include/linux/rds.h:157:18: error: field ‘faddr’ has incomplete type
struct in6_addr faddr;
^
Hi all,
I am a Ph.D. student from China. Our research team is dedicated to
helping FLOSS ecosystems have healthy and sustainable development. The
Linux kernel is one of the key study cases for us because as a
prominent FLOSS project, the Linux kernel has many unique practices.
Recently, we
Hi all,
I am a Ph.D. student from China. Our research team is dedicated to
helping FLOSS ecosystems have healthy and sustainable development. The
Linux kernel is one of the key study cases for us because as a
prominent FLOSS project, the Linux kernel has many unique practices.
Recently, we
Adding a few people to the cc.
On Fri, Aug 24, 2018 at 1:24 PM Nadav Amit wrote:
> >
> > Can you actually find something that changes the fixmaps after boot
> > (again, ignoring kmap)?
>
> At least the alternatives mechanism appears to do so.
>
> IIUC the following path is possible when adding a
Adding a few people to the cc.
On Fri, Aug 24, 2018 at 1:24 PM Nadav Amit wrote:
> >
> > Can you actually find something that changes the fixmaps after boot
> > (again, ignoring kmap)?
>
> At least the alternatives mechanism appears to do so.
>
> IIUC the following path is possible when adding a
On Fri, Aug 24, 2018 at 4:58 PM, Jann Horn wrote:
> Reset the KASAN shadow state of the task stack when rewinding RSP.
> Without this, a kernel oops will leave parts of the stack poisoned, and
> code running under do_exit() can trip over such poisoned regions and cause
> nonsensical
On Fri, Aug 24, 2018 at 4:58 PM, Jann Horn wrote:
> Reset the KASAN shadow state of the task stack when rewinding RSP.
> Without this, a kernel oops will leave parts of the stack poisoned, and
> code running under do_exit() can trip over such poisoned regions and cause
> nonsensical
Hi Jérôme,
On 24 Aug 2018, at 15:25, jgli...@redhat.com wrote:
> From: Jérôme Glisse
>
> Before this patch migration pmd entry (!pmd_present()) would have
> been treated as a bad entry (pmd_bad() returns true on migration
> pmd entry). The outcome was that device driver would believe that
> the
Hi Jérôme,
On 24 Aug 2018, at 15:25, jgli...@redhat.com wrote:
> From: Jérôme Glisse
>
> Before this patch migration pmd entry (!pmd_present()) would have
> been treated as a bad entry (pmd_bad() returns true on migration
> pmd entry). The outcome was that device driver would believe that
> the
Reset the KASAN shadow state of the task stack when rewinding RSP.
Without this, a kernel oops will leave parts of the stack poisoned, and
code running under do_exit() can trip over such poisoned regions and cause
nonsensical false-positive KASAN reports about stack-out-of-bounds bugs.
This patch
Reset the KASAN shadow state of the task stack when rewinding RSP.
Without this, a kernel oops will leave parts of the stack poisoned, and
code running under do_exit() can trip over such poisoned regions and cause
nonsensical false-positive KASAN reports about stack-out-of-bounds bugs.
This patch
On Mon, 2018-07-23 at 14:41 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Dave Hansen
>
> commit 39a0526fb3f7d93433d146304278477eb463f8af upstream
[...]
> --- a/arch/x86/include/asm/mmu_context.h
On Mon, 2018-07-23 at 14:41 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Dave Hansen
>
> commit 39a0526fb3f7d93433d146304278477eb463f8af upstream
[...]
> --- a/arch/x86/include/asm/mmu_context.h
On Fri, 24 Aug 2018 06:50:48 PDT (-0700), Will Deacon wrote:
On Fri, Aug 24, 2018 at 02:34:27PM +0100, Will Deacon wrote:
On Fri, Aug 24, 2018 at 06:24:19AM -0700, Guenter Roeck wrote:
> On Fri, Aug 24, 2018 at 02:10:27PM +0100, Will Deacon wrote:
> > On Fri, Aug 24, 2018 at 06:07:22AM -0700,
On Fri, 24 Aug 2018 06:50:48 PDT (-0700), Will Deacon wrote:
On Fri, Aug 24, 2018 at 02:34:27PM +0100, Will Deacon wrote:
On Fri, Aug 24, 2018 at 06:24:19AM -0700, Guenter Roeck wrote:
> On Fri, Aug 24, 2018 at 02:10:27PM +0100, Will Deacon wrote:
> > On Fri, Aug 24, 2018 at 06:07:22AM -0700,
On Thu, Aug 09, 2018 at 06:02:39PM +0530, Amit Kucheria wrote:
> The SROT registers are initialised by the secure firmware at boot. We
> don't have write access to the registers. Check if the block is enabled
> before continuing.
>
Should this be merged to patch 6?
> Signed-off-by: Amit
On Thu, Aug 09, 2018 at 06:02:39PM +0530, Amit Kucheria wrote:
> The SROT registers are initialised by the secure firmware at boot. We
> don't have write access to the registers. Check if the block is enabled
> before continuing.
>
Should this be merged to patch 6?
> Signed-off-by: Amit
On Thu, Aug 09, 2018 at 06:02:33PM +0530, Amit Kucheria wrote:
> We've earlier added support to split the register address space into TM
> and SROT regions.
>
> Split up the regmap address space into two for the remaining platforms that
> have a similar register layout and make corresponding
On Thu, Aug 09, 2018 at 06:02:33PM +0530, Amit Kucheria wrote:
> We've earlier added support to split the register address space into TM
> and SROT regions.
>
> Split up the regmap address space into two for the remaining platforms that
> have a similar register layout and make corresponding
On Fri, 17 Aug 2018 01:41:55 +0900
Masami Hiramatsu wrote:
> Add a test case for stacktrace filter command for ftrace.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../ftrace/test.d/ftrace/func-filter-stacktrace.tc | 12
> 1 file changed, 12 insertions(+)
> create mode 100644
On Fri, 17 Aug 2018 01:41:55 +0900
Masami Hiramatsu wrote:
> Add a test case for stacktrace filter command for ftrace.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../ftrace/test.d/ftrace/func-filter-stacktrace.tc | 12
> 1 file changed, 12 insertions(+)
> create mode 100644
On Fri, 17 Aug 2018 01:41:27 +0900
Masami Hiramatsu wrote:
> Add a simple testcase for trace_pipe which can consume
> ringbuffer.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../selftests/ftrace/test.d/00basic/trace_pipe.tc | 15 +++
> 1 file changed, 15 insertions(+)
> create
On Fri, 17 Aug 2018 01:41:27 +0900
Masami Hiramatsu wrote:
> Add a simple testcase for trace_pipe which can consume
> ringbuffer.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../selftests/ftrace/test.d/00basic/trace_pipe.tc | 15 +++
> 1 file changed, 15 insertions(+)
> create
On Fri, 17 Aug 2018 01:40:59 +0900
Masami Hiramatsu wrote:
> Add a testcase for function filter on module.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../ftrace/test.d/ftrace/func_mod_trace.tc | 24
>
> 1 file changed, 24 insertions(+)
> create mode 100644
>
On Fri, 17 Aug 2018 01:40:59 +0900
Masami Hiramatsu wrote:
> Add a testcase for function filter on module.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../ftrace/test.d/ftrace/func_mod_trace.tc | 24
>
> 1 file changed, 24 insertions(+)
> create mode 100644
>
On Thu, Aug 09, 2018 at 06:02:34PM +0530, Amit Kucheria wrote:
> c(1) + x(1) was actually meant to be c(1) * x(1).
>
> While we're at it, add some brackets to make it nicer to read.
>
> Signed-off-by: Amit Kucheria
> ---
> Documentation/devicetree/bindings/thermal/thermal.txt | 2 +-
> 1 file
On Thu, Aug 09, 2018 at 06:02:34PM +0530, Amit Kucheria wrote:
> c(1) + x(1) was actually meant to be c(1) * x(1).
>
> While we're at it, add some brackets to make it nicer to read.
>
> Signed-off-by: Amit Kucheria
> ---
> Documentation/devicetree/bindings/thermal/thermal.txt | 2 +-
> 1 file
On Fri, 17 Aug 2018 01:40:30 +0900
Masami Hiramatsu wrote:
> Add a testcase for max stack tracer, which checks basic
> max stack usage tracing and its filter feature.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../ftrace/test.d/ftrace/func_stack_tracer.tc | 39
>
On Fri, 17 Aug 2018 01:40:30 +0900
Masami Hiramatsu wrote:
> Add a testcase for max stack tracer, which checks basic
> max stack usage tracing and its filter feature.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../ftrace/test.d/ftrace/func_stack_tracer.tc | 39
>
hello,
On Thu, Aug 09, 2018 at 06:02:33PM +0530, Amit Kucheria wrote:
> We've earlier added support to split the register address space into TM
> and SROT regions.
>
> Split up the regmap address space into two for the remaining platforms that
> have a similar register layout and make
hello,
On Thu, Aug 09, 2018 at 06:02:33PM +0530, Amit Kucheria wrote:
> We've earlier added support to split the register address space into TM
> and SROT regions.
>
> Split up the regmap address space into two for the remaining platforms that
> have a similar register layout and make
On Fri, 17 Aug 2018 01:40:02 +0900
Masami Hiramatsu wrote:
> Add a testcase for function profiling per-cpu statistics
> interface. There is already func_profile.tc, but that is
> mainly focusing on the combination of function-profiler
> and function tracer. This testcase ensures trace_stat
>
On Fri, 17 Aug 2018 01:40:02 +0900
Masami Hiramatsu wrote:
> Add a testcase for function profiling per-cpu statistics
> interface. There is already func_profile.tc, but that is
> mainly focusing on the combination of function-profiler
> and function tracer. This testcase ensures trace_stat
>
On Fri, 17 Aug 2018 01:39:34 +0900
Masami Hiramatsu wrote:
> Add a testcase for changing ringbuffer size. This tests
> not only ringbuffer size but also tests the imbalance
> per-cpu buffer size change too.
>
> Signed-off-by: Masami Hiramatsu
I'm fine with this, but one day I need to port
On Fri, 17 Aug 2018 01:39:34 +0900
Masami Hiramatsu wrote:
> Add a testcase for changing ringbuffer size. This tests
> not only ringbuffer size but also tests the imbalance
> per-cpu buffer size change too.
>
> Signed-off-by: Masami Hiramatsu
I'm fine with this, but one day I need to port
On Wed, Aug 08, 2018 at 12:38:14PM +0530, Viresh Kumar wrote:
> A cooling map entry may now contain a list of phandles and their
> arguments representing multiple devices which share the trip point.
>
> This patch updates the thermal OF core to parse them properly. The trip
> point and
On Wed, Aug 08, 2018 at 12:38:14PM +0530, Viresh Kumar wrote:
> A cooling map entry may now contain a list of phandles and their
> arguments representing multiple devices which share the trip point.
>
> This patch updates the thermal OF core to parse them properly. The trip
> point and
Hey
On Tue, Jul 31, 2018 at 11:59:13AM -0700, Matthias Kaehlcke wrote:
> The documentation claims that the 'reg' property consists of two values,
> the SPMI address and the length of the controller's registers. However
> the SPMI bus to which it is added specifies "#size-cells = <0>;". Remove
>
Hey
On Tue, Jul 31, 2018 at 11:59:13AM -0700, Matthias Kaehlcke wrote:
> The documentation claims that the 'reg' property consists of two values,
> the SPMI address and the length of the controller's registers. However
> the SPMI bus to which it is added specifies "#size-cells = <0>;". Remove
>
On Fri, Aug 24, 2018 at 4:07 PM dbasehore . wrote:
>
>
>
> On Fri, Aug 24, 2018 at 1:49 AM Andi Shyti wrote:
>>
>> Hi Derek,
>>
>> > > > On Thu, Aug 23, 2018 at 04:10:13PM -0700, Derek Basehore wrote:
>> > > > > We only need to wait 10ms instead of 30ms before starting fastboot or
>> > > > >
On Fri, Aug 24, 2018 at 4:07 PM dbasehore . wrote:
>
>
>
> On Fri, Aug 24, 2018 at 1:49 AM Andi Shyti wrote:
>>
>> Hi Derek,
>>
>> > > > On Thu, Aug 23, 2018 at 04:10:13PM -0700, Derek Basehore wrote:
>> > > > > We only need to wait 10ms instead of 30ms before starting fastboot or
>> > > > >
On Fri, 17 Aug 2018 01:34:51 +0900
Masami Hiramatsu wrote:
> Improve kprobe events on module testcase to check module
> load/unload with disabled/enabled events. This also change
> the target module to trace_printk.ko, so it depends on
> CONFIG_SAMPLE_TRACE_PRINTK=m.
>
> Signed-off-by: Masami
On Fri, 17 Aug 2018 01:34:51 +0900
Masami Hiramatsu wrote:
> Improve kprobe events on module testcase to check module
> load/unload with disabled/enabled events. This also change
> the target module to trace_printk.ko, so it depends on
> CONFIG_SAMPLE_TRACE_PRINTK=m.
>
> Signed-off-by: Masami
From: Guy Luz
Fixed a Lines should not end with a '(' issue.
Signed-off-by: Guy Luz
---
drivers/staging/comedi/drivers/cb_pcidas64.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/comedi/drivers/cb_pcidas64.c
From: Guy Luz
Fixed a Lines should not end with a '(' issue.
Signed-off-by: Guy Luz
---
drivers/staging/comedi/drivers/cb_pcidas64.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/comedi/drivers/cb_pcidas64.c
Add NUMA emulation support to emulate NUMA on non-NUMA platforms. A new
CONFIG_NUMA_EMU option enables NUMA emulation and a new kernel command
line option "numa=fake=N" allows users to specify the configuration for
emulation.
When NUMA emulation is enabled, a flat (non-NUMA) machine will be split
Add NUMA emulation support to emulate NUMA on non-NUMA platforms. A new
CONFIG_NUMA_EMU option enables NUMA emulation and a new kernel command
line option "numa=fake=N" allows users to specify the configuration for
emulation.
When NUMA emulation is enabled, a flat (non-NUMA) machine will be split
On Fri, 17 Aug 2018 01:39:06 +0900
Masami Hiramatsu wrote:
> Add trace_printk sample module test. This requires to
> enable trace_printk.ko module for test.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../selftests/ftrace/test.d/event/trace_printk.tc | 27
>
> 1 file
On Fri, 17 Aug 2018 01:39:06 +0900
Masami Hiramatsu wrote:
> Add trace_printk sample module test. This requires to
> enable trace_printk.ko module for test.
>
> Signed-off-by: Masami Hiramatsu
> ---
> .../selftests/ftrace/test.d/event/trace_printk.tc | 27
>
> 1 file
On Fri, Aug 24, 2018 at 10:54:31PM +, Eric Wong wrote:
> The pipe_poll function does not use locks, and adding an entry
> to the waitqueue is not guaranteed to happen before pipe->nrbufs
> (or other fields) are read, leading to missed wakeups.
>
> Looking at Ruby CI build logs and backtraces,
#syz dup KASAN: use-after-free Read in rds_find_bound
unknown command "dup"
The problem is a missing synchronize_net() in rds_release.
References:
https://www.spinics.net/lists/netdev/msg475074.html
https://www.spinics.net/lists/netdev/msg507908.html
--
You received this message
On Fri, Aug 24, 2018 at 10:54:31PM +, Eric Wong wrote:
> The pipe_poll function does not use locks, and adding an entry
> to the waitqueue is not guaranteed to happen before pipe->nrbufs
> (or other fields) are read, leading to missed wakeups.
>
> Looking at Ruby CI build logs and backtraces,
#syz dup KASAN: use-after-free Read in rds_find_bound
unknown command "dup"
The problem is a missing synchronize_net() in rds_release.
References:
https://www.spinics.net/lists/netdev/msg475074.html
https://www.spinics.net/lists/netdev/msg507908.html
--
You received this message
On Fri, Aug 24, 2018 at 09:59:21PM +0200, Emmanuel Vadot wrote:
>
> Hi,
>
> On Fri, 24 Aug 2018 16:58:40 +0200
> Maxime Ripard wrote:
>
> > Hi,
> >
> > On Mon, Aug 20, 2018 at 04:27:15PM +0200, Emmanuel Vadot wrote:
> > > On Mon, 20 Aug 2018 16:07:37 +0200
> > > Maxime Ripard wrote:
> > >
On Fri, Aug 24, 2018 at 09:59:21PM +0200, Emmanuel Vadot wrote:
>
> Hi,
>
> On Fri, 24 Aug 2018 16:58:40 +0200
> Maxime Ripard wrote:
>
> > Hi,
> >
> > On Mon, Aug 20, 2018 at 04:27:15PM +0200, Emmanuel Vadot wrote:
> > > On Mon, 20 Aug 2018 16:07:37 +0200
> > > Maxime Ripard wrote:
> > >
The pipe_poll function does not use locks, and adding an entry
to the waitqueue is not guaranteed to happen before pipe->nrbufs
(or other fields) are read, leading to missed wakeups.
Looking at Ruby CI build logs and backtraces, I've noticed
occasional instances where processes are stuck in
The pipe_poll function does not use locks, and adding an entry
to the waitqueue is not guaranteed to happen before pipe->nrbufs
(or other fields) are read, leading to missed wakeups.
Looking at Ruby CI build logs and backtraces, I've noticed
occasional instances where processes are stuck in
On Fri, 17 Aug 2018 01:38:09 +0900
Masami Hiramatsu wrote:
> Add a testcase for nop tracer. This tracer has 2 test
> options, so check it too.
>
I'd rather not include this. In fact, I'd love to get rid of the nop
options. They were added to make sure options worked when we first
added them.
On Fri, 17 Aug 2018 01:38:09 +0900
Masami Hiramatsu wrote:
> Add a testcase for nop tracer. This tracer has 2 test
> options, so check it too.
>
I'd rather not include this. In fact, I'd love to get rid of the nop
options. They were added to make sure options worked when we first
added them.
On středa 15. srpna 2018 21:04:49 CEST, Kosta Zertsekel wrote:
This change increases the source code readability.
Instead of using `spi->child[cs].direct_access.XXX` use `dir_acc->XXX`.
Instead of using `orion_spi->child[cs].direct_access.vaddr` use `vaddr`.
Signed-off-by: Kosta Zertsekel
On středa 15. srpna 2018 21:04:49 CEST, Kosta Zertsekel wrote:
This change increases the source code readability.
Instead of using `spi->child[cs].direct_access.XXX` use `dir_acc->XXX`.
Instead of using `orion_spi->child[cs].direct_access.vaddr` use `vaddr`.
Signed-off-by: Kosta Zertsekel
On Fri, Aug 24, 2018 at 02:54:39PM -0700, Kees Cook wrote:
> The overflow was real, but the results went unused, so while the flaw
> is harmless, it's noisy for kernel fuzzers, and the fix makes things
> technically more efficient.
yes, yes, yes, yes and no. Compiler is quite capable of
On Fri, Aug 24, 2018 at 02:54:39PM -0700, Kees Cook wrote:
> The overflow was real, but the results went unused, so while the flaw
> is harmless, it's noisy for kernel fuzzers, and the fix makes things
> technically more efficient.
yes, yes, yes, yes and no. Compiler is quite capable of
1 - 100 of 818 matches
Mail list logo
