[rcu] df95cc69cc: BUG:KASAN:null-ptr-deref_in__lock_acquire

FYI, we noticed the following commit (built with gcc-7): commit: df95cc69cca894430640237d39453f5d96c40a7d ("rcu: Parallelize expedited grace-period initialization") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git rcu/dev in testcase: trinity with following parameters:

[rcu] df95cc69cc: BUG:KASAN:null-ptr-deref_in__lock_acquire

FYI, we noticed the following commit (built with gcc-7): commit: df95cc69cca894430640237d39453f5d96c40a7d ("rcu: Parallelize expedited grace-period initialization") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git rcu/dev in testcase: trinity with following parameters:

Re: [PATCH BUGFIX V3] block, bfq: add requeue-request hook

> Il giorno 23 feb 2018, alle ore 17:17, Ming Lei ha > scritto: > > Hi Paolo, > > On Fri, Feb 23, 2018 at 04:41:36PM +0100, Paolo Valente wrote: >> >> >>> Il giorno 23 feb 2018, alle ore 16:07, Ming Lei ha >>> scritto: >>> >>> Hi Paolo, >>> >>>

Re: [PATCH BUGFIX V3] block, bfq: add requeue-request hook

> Il giorno 23 feb 2018, alle ore 17:17, Ming Lei ha > scritto: > > Hi Paolo, > > On Fri, Feb 23, 2018 at 04:41:36PM +0100, Paolo Valente wrote: >> >> >>> Il giorno 23 feb 2018, alle ore 16:07, Ming Lei ha >>> scritto: >>> >>> Hi Paolo, >>> >>> On Wed, Feb 07, 2018 at 10:19:20PM +0100,

Re: [v4] ARM: dts: imx: Add support for Advantech DMS-BA16

On Sat, Feb 10, 2018 at 05:55:15AM +0800, Ken Lin wrote: > Add support for Advantech DMS-BA16 board, which uses > the Advantech BA-16 module. > > Signed-off-by: Ken Lin Applied, thanks.

Re: [v4] ARM: dts: imx: Add support for Advantech DMS-BA16

On Sat, Feb 10, 2018 at 05:55:15AM +0800, Ken Lin wrote: > Add support for Advantech DMS-BA16 board, which uses > the Advantech BA-16 module. > > Signed-off-by: Ken Lin Applied, thanks.

Re: [PATCH v5 3/6] powerpc/mm/slice: Enhance for supporting PPC32

On Thu, 22 Feb 2018 15:27:24 +0100 (CET) Christophe Leroy wrote: > In preparation for the following patch which will fix an issue on > the 8xx by re-using the 'slices', this patch enhances the > 'slices' implementation to support 32 bits CPUs. > > On PPC32, the address

Re: [PATCH v5 3/6] powerpc/mm/slice: Enhance for supporting PPC32

On Thu, 22 Feb 2018 15:27:24 +0100 (CET) Christophe Leroy wrote: > In preparation for the following patch which will fix an issue on > the 8xx by re-using the 'slices', this patch enhances the > 'slices' implementation to support 32 bits CPUs. > > On PPC32, the address space is limited to

Re: [PATCHv4 1/2] ARM: imx53: add secure-reg-access support for PMU

On Mon, Feb 12, 2018 at 01:39:44PM +0100, Sebastian Reichel wrote: > On i.MX53 it is necessary to set the DBG_EN bit in the > platform GPC register to enable access to PMU counters > other than the cycle counter. > > Signed-off-by: Sebastian Reichel > --- >

Re: [PATCHv4 1/2] ARM: imx53: add secure-reg-access support for PMU

On Mon, Feb 12, 2018 at 01:39:44PM +0100, Sebastian Reichel wrote: > On i.MX53 it is necessary to set the DBG_EN bit in the > platform GPC register to enable access to PMU counters > other than the cycle counter. > > Signed-off-by: Sebastian Reichel > --- > arch/arm/mach-imx/mach-imx53.c | 39

Re: [PATCH RFC] ARM: imx: avic: set low-power interrupt mask for imx25

On Fri, Feb 09, 2018 at 01:43:23PM +0100, Martin Kaiser wrote: > imx25 contains two registers (LPIMR0 and 1) to define which interrupts > are enabled in low-power mode. As of today, those two registers are > configured to enable all interrupts. Before going to low-power mode, the > AVIC's

Re: [PATCH RFC] ARM: imx: avic: set low-power interrupt mask for imx25

On Fri, Feb 09, 2018 at 01:43:23PM +0100, Martin Kaiser wrote: > imx25 contains two registers (LPIMR0 and 1) to define which interrupts > are enabled in low-power mode. As of today, those two registers are > configured to enable all interrupts. Before going to low-power mode, the > AVIC's

Re: [RFC tip/locking/lockdep v5 04/17] lockdep: Introduce lock_list::dep

On Sat, Feb 24, 2018 at 01:32:50PM +0800, Boqun Feng wrote: [...] > > I also reorder bit number for each kind of dependency, so that we have a > simple __calc_dep_bit(), see the following: > > /* >* DEP_*_BIT in lock_list::dep >* >* For dependency @prev -> @next: >

Re: [RFC tip/locking/lockdep v5 04/17] lockdep: Introduce lock_list::dep

On Sat, Feb 24, 2018 at 01:32:50PM +0800, Boqun Feng wrote: [...] > > I also reorder bit number for each kind of dependency, so that we have a > simple __calc_dep_bit(), see the following: > > /* >* DEP_*_BIT in lock_list::dep >* >* For dependency @prev -> @next: >

Re: [PATCH 2/2] efi/esrt: mark ESRT memory region as nomap

On 02/23/18 at 12:42pm, Tyler Baicar wrote: > The ESRT memory region is being exposed as System RAM in /proc/iomem > which is wrong because it cannot be overwritten. This memory is needed > for kexec kernels in order to properly initialize ESRT, so if it is > overwritten it will cause ESRT

Re: [PATCH 2/2] efi/esrt: mark ESRT memory region as nomap

On 02/23/18 at 12:42pm, Tyler Baicar wrote: > The ESRT memory region is being exposed as System RAM in /proc/iomem > which is wrong because it cannot be overwritten. This memory is needed > for kexec kernels in order to properly initialize ESRT, so if it is > overwritten it will cause ESRT

Re: [PATCH v5 2/6] powerpc/mm/slice: create header files dedicated to slices

On Thu, 22 Feb 2018 15:27:22 +0100 (CET) Christophe Leroy wrote: > In preparation for the following patch which will enhance 'slices' > for supporting PPC32 in order to fix an issue on hugepages on 8xx, > this patch takes out of page*.h all bits related to 'slices' and

Re: [PATCH v5 2/6] powerpc/mm/slice: create header files dedicated to slices

On Thu, 22 Feb 2018 15:27:22 +0100 (CET) Christophe Leroy wrote: > In preparation for the following patch which will enhance 'slices' > for supporting PPC32 in order to fix an issue on hugepages on 8xx, > this patch takes out of page*.h all bits related to 'slices' and put > them into newly

Re: [PATCH 1/2] efi/esrt: fix unsupported version initialization failure

On 02/23/18 at 12:42pm, Tyler Baicar wrote: > If ESRT initialization fails due to an unsupported version, the > early_memremap allocation is never unmapped. This will cause an > early ioremap leak. So, make sure to unmap the memory allocation > before returning from efi_esrt_init(). > >

Re: [PATCH 1/2] efi/esrt: fix unsupported version initialization failure

On 02/23/18 at 12:42pm, Tyler Baicar wrote: > If ESRT initialization fails due to an unsupported version, the > early_memremap allocation is never unmapped. This will cause an > early ioremap leak. So, make sure to unmap the memory allocation > before returning from efi_esrt_init(). > >

Re: [PATCH 1/3] arm64: dts: ls1012a: add cpu idle support

On Sat, Feb 24, 2018 at 02:25:16PM +0800, Shawn Guo wrote: > On Thu, Feb 08, 2018 at 03:54:34PM +0800, Ran Wang wrote: > > From: Yuantian Tang > > > > Signed-off-by: Tang Yuantian > > --- > > arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 18

Re: [PATCH 1/3] arm64: dts: ls1012a: add cpu idle support

On Sat, Feb 24, 2018 at 02:25:16PM +0800, Shawn Guo wrote: > On Thu, Feb 08, 2018 at 03:54:34PM +0800, Ran Wang wrote: > > From: Yuantian Tang > > > > Signed-off-by: Tang Yuantian > > --- > > arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 18 ++ > > 1 files changed, 18

lib/find_bit.c:203:15: error: redefinition of 'find_next_zero_bit_le'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 9cb9c07d6b0c5fd97d83b8ab14d7e308ba4b612f commit: 101110f6271ce956a049250c907bc960030577f8 Kbuild: always define endianess in kconfig.h date: 2 days ago config: m32r-allyesconfig (attached as .config)

lib/find_bit.c:203:15: error: redefinition of 'find_next_zero_bit_le'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 9cb9c07d6b0c5fd97d83b8ab14d7e308ba4b612f commit: 101110f6271ce956a049250c907bc960030577f8 Kbuild: always define endianess in kconfig.h date: 2 days ago config: m32r-allyesconfig (attached as .config)

RE: [Intel-wired-lan] [PATCH net-queue] e1000e: Fix check_for_link return value with autoneg off.

> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On > Behalf Of Benjamin Poirier > Sent: Monday, February 19, 2018 10:12 PM > To: Kirsher, Jeffrey T > Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux- > ker...@vger.kernel.org >

RE: [Intel-wired-lan] [PATCH net-queue] e1000e: Fix check_for_link return value with autoneg off.

> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On > Behalf Of Benjamin Poirier > Sent: Monday, February 19, 2018 10:12 PM > To: Kirsher, Jeffrey T > Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux- > ker...@vger.kernel.org > Subject: [Intel-wired-lan]

Re: [RFC tip/locking/lockdep v5 04/17] lockdep: Introduce lock_list::dep

On Sat, Feb 24, 2018 at 01:32:50PM +0800, Boqun Feng wrote: > On Fri, Feb 23, 2018 at 08:37:32PM +0800, Boqun Feng wrote: > > On Fri, Feb 23, 2018 at 12:55:20PM +0100, Peter Zijlstra wrote: > > > On Thu, Feb 22, 2018 at 03:08:51PM +0800, Boqun Feng wrote: > > > > @@ -1012,6 +1013,33 @@ static

Re: [RFC tip/locking/lockdep v5 04/17] lockdep: Introduce lock_list::dep

On Sat, Feb 24, 2018 at 01:32:50PM +0800, Boqun Feng wrote: > On Fri, Feb 23, 2018 at 08:37:32PM +0800, Boqun Feng wrote: > > On Fri, Feb 23, 2018 at 12:55:20PM +0100, Peter Zijlstra wrote: > > > On Thu, Feb 22, 2018 at 03:08:51PM +0800, Boqun Feng wrote: > > > > @@ -1012,6 +1013,33 @@ static

Re: [PATCH 1/3] arm64: dts: ls1012a: add cpu idle support

On Thu, Feb 08, 2018 at 03:54:34PM +0800, Ran Wang wrote: > From: Yuantian Tang > > Signed-off-by: Tang Yuantian > --- > arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 18 ++ > 1 files changed, 18 insertions(+), 0 deletions(-) Applied

Re: [PATCH 1/3] arm64: dts: ls1012a: add cpu idle support

On Thu, Feb 08, 2018 at 03:54:34PM +0800, Ran Wang wrote: > From: Yuantian Tang > > Signed-off-by: Tang Yuantian > --- > arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 18 ++ > 1 files changed, 18 insertions(+), 0 deletions(-) Applied all, thanks.

[lkp-robot] [rcu] 056becf54e: BUG:KASAN:null-ptr-deref_in__lock_acquire

TO: Paul E. McKenney CC: LKML , Paul E. McKenney , linux-kernel@vger.kernel.org, l...@01.org FYI, we noticed the following commit (built with gcc-7): commit: 056becf54ef1ab39db14a66625353899dba6762f ("rcu:

[lkp-robot] [rcu] 056becf54e: BUG:KASAN:null-ptr-deref_in__lock_acquire

TO: Paul E. McKenney CC: LKML , Paul E. McKenney , linux-kernel@vger.kernel.org, l...@01.org FYI, we noticed the following commit (built with gcc-7): commit: 056becf54ef1ab39db14a66625353899dba6762f ("rcu: Parallelize expedited grace-period initialization")

[PATCH 1/1] iommu/vt-d: Fix a potential memory leak

A memory block was allocated in intel_svm_bind_mm() but never freed in a failure path. This patch fixes this by free it to avoid memory leakage. Cc: Ashok Raj Cc: Jacob Pan Cc: # v4.4+ Signed-off-by: Lu Baolu

[PATCH 1/1] iommu/vt-d: Fix a potential memory leak

A memory block was allocated in intel_svm_bind_mm() but never freed in a failure path. This patch fixes this by free it to avoid memory leakage. Cc: Ashok Raj Cc: Jacob Pan Cc: # v4.4+ Signed-off-by: Lu Baolu --- drivers/iommu/intel-svm.c | 1 + 1 file changed, 1 insertion(+) diff --git

[RFC] vfio iommu type1: improve memory pinning process for raw PFN mapping

When using vfio to pass through a PCIe device (e.g. a GPU card) that has a huge BAR (e.g. 16GB), a lot of cycles are wasted on memory pinning because PFNs of PCI BAR are not backed by struct page, and the corresponding VMA has flags VM_IO|VM_PFNMAP. With this change, memory pinning process will

[RFC] vfio iommu type1: improve memory pinning process for raw PFN mapping

When using vfio to pass through a PCIe device (e.g. a GPU card) that has a huge BAR (e.g. 16GB), a lot of cycles are wasted on memory pinning because PFNs of PCI BAR are not backed by struct page, and the corresponding VMA has flags VM_IO|VM_PFNMAP. With this change, memory pinning process will

[PATCH v3 18/18] selftests: ftrace: Add a testcase for array type with kprobe_event

Add a testcase for array type with kprobe event. This tests good/bad syntax combinations and also the traced data is correct in several way. If the kernel doesn't support array type, it skips the test as UNSUPPORTED. Signed-off-by: Masami Hiramatsu ---

[PATCH v3 18/18] selftests: ftrace: Add a testcase for array type with kprobe_event

Add a testcase for array type with kprobe event. This tests good/bad syntax combinations and also the traced data is correct in several way. If the kernel doesn't support array type, it skips the test as UNSUPPORTED. Signed-off-by: Masami Hiramatsu ---

[PATCH v3 17/18] selftests: ftrace: Add a testcase for $argN with kprobe_event

Add a testcase for array type with kprobe event. This tests whether the traced data is correct or not. If the kernel doesn't support array type, it skips the test as UNSUPPORTED. Signed-off-by: Masami Hiramatsu --- .../ftrace/test.d/kprobe/kprobe_args_argN.tc | 25

[PATCH v3 17/18] selftests: ftrace: Add a testcase for $argN with kprobe_event

Add a testcase for array type with kprobe event. This tests whether the traced data is correct or not. If the kernel doesn't support array type, it skips the test as UNSUPPORTED. Signed-off-by: Masami Hiramatsu --- .../ftrace/test.d/kprobe/kprobe_args_argN.tc | 25

[PATCH v3 15/18] tracing: probeevent: Add array type support

Add array type support for probe events. This allows user to get arraied types from memory address. The array type syntax is TYPE[N] Where TYPE is one of types (u8/16/32/64,s8/16/32/64, x8/16/32/64, symbol, string) and N is a fixed value less than 64. The string array type is a bit

[PATCH v3 15/18] tracing: probeevent: Add array type support

Add array type support for probe events. This allows user to get arraied types from memory address. The array type syntax is TYPE[N] Where TYPE is one of types (u8/16/32/64,s8/16/32/64, x8/16/32/64, symbol, string) and N is a fixed value less than 64. The string array type is a bit

[PATCH v3 16/18] selftests: ftrace: Add a testcase for symbol type

Add a testcase for symbol type with kprobe event. This tests good/bad syntax combinations and also the traced data. If the kernel doesn't support symbol type, it skips the test as UNSUPPORTED. Signed-off-by: Masami Hiramatsu --- Changes in v3: - Use IP/PC register to test

[PATCH v3 16/18] selftests: ftrace: Add a testcase for symbol type

Add a testcase for symbol type with kprobe event. This tests good/bad syntax combinations and also the traced data. If the kernel doesn't support symbol type, it skips the test as UNSUPPORTED. Signed-off-by: Masami Hiramatsu --- Changes in v3: - Use IP/PC register to test the symbol type ---

[PATCH v3 14/18] tracing: probeevent: Add $argN for accessing function args

Add $argN special fetch variable for accessing function arguments. This allows user to trace the Nth argument easily at the function entry. Note that this returns most probably assignment of registers and stacks. In some case, it may not work well. If you need to access correct registers or

[PATCH v3 14/18] tracing: probeevent: Add $argN for accessing function args

Add $argN special fetch variable for accessing function arguments. This allows user to trace the Nth argument easily at the function entry. Note that this returns most probably assignment of registers and stacks. In some case, it may not work well. If you need to access correct registers or

[PATCH v3 13/18] x86: ptrace: Add function argument access API

Add regs_get_argument() which returns N th argument of the function call. Note that this chooses most probably assignment, in some case it can be incorrect (e.g. passing data structure or floating point etc.) This is expected to be called from kprobes or ftrace with regs where the top of stack is

[PATCH v3 13/18] x86: ptrace: Add function argument access API

Add regs_get_argument() which returns N th argument of the function call. Note that this chooses most probably assignment, in some case it can be incorrect (e.g. passing data structure or floating point etc.) This is expected to be called from kprobes or ftrace with regs where the top of stack is

[PATCH v3 11/18] tracing: probeevent: Unify fetch_insn processing common part

Unify the fetch_insn bottom process (from stage 2: dereference indirect data) from kprobe and uprobe events, since those are mostly same. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 47 +

[PATCH v3 11/18] tracing: probeevent: Unify fetch_insn processing common part

Unify the fetch_insn bottom process (from stage 2: dereference indirect data) from kprobe and uprobe events, since those are mostly same. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 47 + kernel/trace/trace_probe_tmpl.h | 55

[PATCH v3 12/18] tracing: probeevent: Add symbol type

Add "symbol" type to probeevent, which is an alias of u32 or u64 (depends on BITS_PER_LONG). This shows the result value in symbol+offset style. This type is only available with kprobe events. Signed-off-by: Masami Hiramatsu --- Changes in v2: - Add symbol type to README

[PATCH v3 12/18] tracing: probeevent: Add symbol type

Add "symbol" type to probeevent, which is an alias of u32 or u64 (depends on BITS_PER_LONG). This shows the result value in symbol+offset style. This type is only available with kprobe events. Signed-off-by: Masami Hiramatsu --- Changes in v2: - Add symbol type to README file. ---

[PATCH v3 10/18] tracing: probeevent: Append traceprobe_ for exported function

Append traceprobe_ for exported function set_print_fmt() as same as other functions. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c |4 ++-- kernel/trace/trace_probe.c |2 +- kernel/trace/trace_probe.h |2 +- kernel/trace/trace_uprobe.c |4

[PATCH v3 10/18] tracing: probeevent: Append traceprobe_ for exported function

Append traceprobe_ for exported function set_print_fmt() as same as other functions. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c |4 ++-- kernel/trace/trace_probe.c |2 +- kernel/trace/trace_probe.h |2 +- kernel/trace/trace_uprobe.c |4 ++-- 4 files

[lkp-robot] [printk] c162d5b433: BUG:KASAN:use-after-scope_in_c

TO: Petr Mladek CC: Cong Wang , Dave Hansen , Johannes Weiner , Mel Gorman , Michal Hocko , Vlastimil Babka , Peter Zijlstra , Linus

[PATCH v3 09/18] tracing: probeevent: Return consumed bytes of dynamic area

Cleanup string fetching routine so that returns the consumed bytes of dynamic area and store the string information as data_loc format instead of data_rloc. This simplifies the fetcharg loop. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 51

[lkp-robot] [printk] c162d5b433: BUG:KASAN:use-after-scope_in_c

TO: Petr Mladek CC: Cong Wang , Dave Hansen , Johannes Weiner , Mel Gorman , Michal Hocko , Vlastimil Babka , Peter Zijlstra , Linus Torvalds , Jan Kara , Mathieu Desnoyers , Tetsuo Handa , Byungchul Park , Tejun Heo , Pavel Machek , Steven Rostedt (VMware) , Sergey Senozhatsky , LKML ,

[PATCH v3 09/18] tracing: probeevent: Return consumed bytes of dynamic area

Cleanup string fetching routine so that returns the consumed bytes of dynamic area and store the string information as data_loc format instead of data_rloc. This simplifies the fetcharg loop. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 51

[PATCH v3 07/18] tracing: probeevent: Introduce new argument fetching code

Replace {k,u}probe event argument fetching framework with switch-case based. Currently that is implemented with structures, macros and chain of function-pointers, which is more complicated than necessary and may get a performance penalty by retpoline. This simplify that with an array of

[PATCH v3 07/18] tracing: probeevent: Introduce new argument fetching code

Replace {k,u}probe event argument fetching framework with switch-case based. Currently that is implemented with structures, macros and chain of function-pointers, which is more complicated than necessary and may get a performance penalty by retpoline. This simplify that with an array of

[PATCH v3 08/18] tracing: probeevent: Unify fetch type tables

Unify {k,u}probe_fetch_type_table to probe_fetch_type_table because the main difference of those type tables (fetcharg methods) are gone. Now we can consolidate it. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 27 +-

[PATCH v3 08/18] tracing: probeevent: Unify fetch type tables

Unify {k,u}probe_fetch_type_table to probe_fetch_type_table because the main difference of those type tables (fetcharg methods) are gone. Now we can consolidate it. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 27 +- kernel/trace/trace_probe.c | 54

[PATCH v3 06/18] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions

Remove unneeded NOKPROBE_SYMBOL from print functions since the print functions are only used when printing out the trace data, and not from kprobe handler. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_probe.c |4 +--- 1 file changed, 1 insertion(+), 3

[PATCH v3 05/18] tracing: probeevent: Cleanup argument field definition

Cleanup event argument definition code in one place for maintenancability. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 32 kernel/trace/trace_probe.c | 21 + kernel/trace/trace_probe.h |2

[PATCH v3 06/18] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions

Remove unneeded NOKPROBE_SYMBOL from print functions since the print functions are only used when printing out the trace data, and not from kprobe handler. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_probe.c |4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git

[PATCH v3 05/18] tracing: probeevent: Cleanup argument field definition

Cleanup event argument definition code in one place for maintenancability. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 32 kernel/trace/trace_probe.c | 21 + kernel/trace/trace_probe.h |2 ++

[PATCH v3 04/18] tracing: probeevent: Cleanup print argument functions

Current print argument functions prints the argument name too. It is not good for printing out multiple values for one argument. This change it to just print out the value. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 20 ++--

[PATCH v3 04/18] tracing: probeevent: Cleanup print argument functions

Current print argument functions prints the argument name too. It is not good for printing out multiple values for one argument. This change it to just print out the value. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 20 ++-- kernel/trace/trace_probe.c |

[PATCH v3 03/18] selftests: ftrace: Add a testcase for string type with kprobe_event

Add a testcase for string type with kprobe event. This tests good/bad syntax combinations and also the traced data is correct in several way. Signed-off-by: Masami Hiramatsu --- .../ftrace/test.d/kprobe/kprobe_args_string.tc | 46 1 file changed,

[PATCH v3 03/18] selftests: ftrace: Add a testcase for string type with kprobe_event

Add a testcase for string type with kprobe event. This tests good/bad syntax combinations and also the traced data is correct in several way. Signed-off-by: Masami Hiramatsu --- .../ftrace/test.d/kprobe/kprobe_args_string.tc | 46 1 file changed, 46 insertions(+)

Re: [RFC tip/locking/lockdep v5 04/17] lockdep: Introduce lock_list::dep

On Fri, Feb 23, 2018 at 08:37:32PM +0800, Boqun Feng wrote: > On Fri, Feb 23, 2018 at 12:55:20PM +0100, Peter Zijlstra wrote: > > On Thu, Feb 22, 2018 at 03:08:51PM +0800, Boqun Feng wrote: > > > @@ -1012,6 +1013,33 @@ static inline bool bfs_error(enum bfs_result res) > > > return res < 0; > > >

[PATCH v3 01/18] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol

In Documentation/trace/kprobetrace.txt, it says @SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data symbol) However, the parser doesn't parse minus offset correctly, since commit 2fba0c8867af ("tracing/kprobes: Fix probe offset to be unsigned") drops minus ("-") offset support

Re: [RFC tip/locking/lockdep v5 04/17] lockdep: Introduce lock_list::dep

On Fri, Feb 23, 2018 at 08:37:32PM +0800, Boqun Feng wrote: > On Fri, Feb 23, 2018 at 12:55:20PM +0100, Peter Zijlstra wrote: > > On Thu, Feb 22, 2018 at 03:08:51PM +0800, Boqun Feng wrote: > > > @@ -1012,6 +1013,33 @@ static inline bool bfs_error(enum bfs_result res) > > > return res < 0; > > >

[PATCH v3 01/18] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol

In Documentation/trace/kprobetrace.txt, it says @SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data symbol) However, the parser doesn't parse minus offset correctly, since commit 2fba0c8867af ("tracing/kprobes: Fix probe offset to be unsigned") drops minus ("-") offset support

[PATCH v3 02/18] selftests: ftrace: Add probe event argument syntax testcase

Add a testcase for probe event argument syntax which ensures the kprobe_events interface correctly parses given event arguments. Signed-off-by: Masami Hiramatsu --- .../ftrace/test.d/kprobe/kprobe_args_syntax.tc | 97 1 file changed, 97

[PATCH v3 02/18] selftests: ftrace: Add probe event argument syntax testcase

Add a testcase for probe event argument syntax which ensures the kprobe_events interface correctly parses given event arguments. Signed-off-by: Masami Hiramatsu --- .../ftrace/test.d/kprobe/kprobe_args_syntax.tc | 97 1 file changed, 97 insertions(+) create mode

[PATCH v3 00/18] tracing: probeevent: Improve fetcharg features

Hi, This is the 3rd version of the fetch-arg improvement series. This includes variable changes on fetcharg framework like, - Add fetcharg testcases (syntax, argN, symbol, string and array) - Rewrite fetcharg framework with fetch_insn, switch-case based instead of function pointer. - Add

[PATCH v3 00/18] tracing: probeevent: Improve fetcharg features

Hi, This is the 3rd version of the fetch-arg improvement series. This includes variable changes on fetcharg framework like, - Add fetcharg testcases (syntax, argN, symbol, string and array) - Rewrite fetcharg framework with fetch_insn, switch-case based instead of function pointer. - Add

Re: [PATCH] drivers/virt: vm_gen_counter: initial driver implementation

Hi Or, Thank you for the patch! Yet something to improve: [auto build test ERROR on char-misc/char-misc-testing] [also build test ERROR on v4.16-rc2 next-20180223] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

Re: [PATCH] drivers/virt: vm_gen_counter: initial driver implementation

Hi Or, Thank you for the patch! Yet something to improve: [auto build test ERROR on char-misc/char-misc-testing] [also build test ERROR on v4.16-rc2 next-20180223] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

Re: [PATCH v3 5/5] linux/const.h: move BIT(_ULL) to linux/const.h for use in assembly

Hi Masahiro, I love your patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.16-rc2 next-20180223] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [PATCH v3 5/5] linux/const.h: move BIT(_ULL) to linux/const.h for use in assembly

Hi Masahiro, I love your patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.16-rc2 next-20180223] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [PATCH v6 11/12] arm64: topology: enable ACPI/PPTT based CPU topology

On 02/23/2018 05:02 AM, Lorenzo Pieralisi wrote: On Thu, Jan 25, 2018 at 09:56:30AM -0600, Jeremy Linton wrote: Hi, On 01/25/2018 06:15 AM, Xiongfeng Wang wrote: Hi Jeremy, I have tested the patch with the newest UEFI. It prints the below error: [4.017371] BUG: arch topology borken [

Re: [PATCH v6 11/12] arm64: topology: enable ACPI/PPTT based CPU topology

On 02/23/2018 05:02 AM, Lorenzo Pieralisi wrote: On Thu, Jan 25, 2018 at 09:56:30AM -0600, Jeremy Linton wrote: Hi, On 01/25/2018 06:15 AM, Xiongfeng Wang wrote: Hi Jeremy, I have tested the patch with the newest UEFI. It prints the below error: [4.017371] BUG: arch topology borken [

Re: [RFC][PATCH 00/10] Use global pages with PTI - Truth about the white man.

Linus, this talk about the memory map bullshit is interesting and all, with that binary encoding and shit. But I want you to take a moment and reflect. I want you to reflect on truth. Ask yourself. "Am I a white man" and then listen to those who... who see you ALL for what you are and couldn't

Re: [RFC][PATCH 00/10] Use global pages with PTI - Truth about the white man.

Linus, this talk about the memory map bullshit is interesting and all, with that binary encoding and shit. But I want you to take a moment and reflect. I want you to reflect on truth. Ask yourself. "Am I a white man" and then listen to those who... who see you ALL for what you are and couldn't

The white man -- Who he is. A Discussion. (Removed by Youtube - Trying to squelch truth spoken to power))

www.liveleak.com/view?i=017_1519418755 This had to be reposted because the youtube people took down the video describing the truth about white society. Speaking truth to power isn't something they was fastioning to slide by. So, dear OpenSource folks, people that run the show on the

The white man -- Who he is. A Discussion. (Removed by Youtube - Trying to squelch truth spoken to power))

www.liveleak.com/view?i=017_1519418755 This had to be reposted because the youtube people took down the video describing the truth about white society. Speaking truth to power isn't something they was fastioning to slide by. So, dear OpenSource folks, people that run the show on the

Re: [RFC][PATCH 00/10] Use global pages with PTI

On Fri, Feb 23, 2018 at 5:49 PM, Dave Hansen wrote: > On 02/22/2018 01:52 PM, Linus Torvalds wrote: >> Side note - and this may be crazy talk - I wonder if it might make >> sense to have a mode where we allow executable read-only kernel pages >> to be marked global

Re: [RFC][PATCH 00/10] Use global pages with PTI

On Fri, Feb 23, 2018 at 5:49 PM, Dave Hansen wrote: > On 02/22/2018 01:52 PM, Linus Torvalds wrote: >> Side note - and this may be crazy talk - I wonder if it might make >> sense to have a mode where we allow executable read-only kernel pages >> to be marked global too (but only in the kernel

Re: Removing architectures without upstream gcc support

On 02/23/2018 01:34 PM, Adam Borowski wrote: On Fri, Feb 23, 2018 at 02:32:08PM -0500, James Bottomley wrote: On Fri, 2018-02-23 at 18:19 +, Al Viro wrote: [...] IIRC, parisc/qemu stuff had been announced a while ago; I have, but it didn't work sufficiently for me to either boot a kernel

Re: Removing architectures without upstream gcc support

On 02/23/2018 01:34 PM, Adam Borowski wrote: On Fri, Feb 23, 2018 at 02:32:08PM -0500, James Bottomley wrote: On Fri, 2018-02-23 at 18:19 +, Al Viro wrote: [...] IIRC, parisc/qemu stuff had been announced a while ago; I have, but it didn't work sufficiently for me to either boot a kernel

RE: [PATCH 3/4] drm/ttm: handle already locked BOs during eviction and swapout.

I missed the Per-VM-BO share the reservation object with root bo. So context is not NULL here. So, this patch is: Reviewed-by: Roger He Thanks Roger(Hongbo.He) -Original Message- From: Christian König [mailto:ckoenig.leichtzumer...@gmail.com] Sent: Friday, February

RE: [PATCH 3/4] drm/ttm: handle already locked BOs during eviction and swapout.

I missed the Per-VM-BO share the reservation object with root bo. So context is not NULL here. So, this patch is: Reviewed-by: Roger He Thanks Roger(Hongbo.He) -Original Message- From: Christian König [mailto:ckoenig.leichtzumer...@gmail.com] Sent: Friday, February 23, 2018 8:06 PM

RE: [PATCH 3/4] drm/ttm: handle already locked BOs during eviction and swapout.

-Original Message- From: Christian König [mailto:ckoenig.leichtzumer...@gmail.com] Sent: Friday, February 23, 2018 8:06 PM To: He, Roger ; amd-...@lists.freedesktop.org; dri-de...@lists.freedesktop.org; linux-kernel@vger.kernel.org Subject: Re: [PATCH 3/4] drm/ttm:

RE: [PATCH 3/4] drm/ttm: handle already locked BOs during eviction and swapout.

-Original Message- From: Christian König [mailto:ckoenig.leichtzumer...@gmail.com] Sent: Friday, February 23, 2018 8:06 PM To: He, Roger ; amd-...@lists.freedesktop.org; dri-de...@lists.freedesktop.org; linux-kernel@vger.kernel.org Subject: Re: [PATCH 3/4] drm/ttm: handle already

[PATCH V4 net 3/3] tuntap: correctly add the missing XDP flush

We don't flush batched XDP packets through xdp_do_flush_map(), this will cause packets stall at TX queue. Consider we don't do XDP on NAPI poll(), the only possible fix is to call xdp_do_flush_map() immediately after xdp_do_redirect(). Note, this in fact won't try to batch packets through devmap,

[PATCH V4 net 3/3] tuntap: correctly add the missing XDP flush

We don't flush batched XDP packets through xdp_do_flush_map(), this will cause packets stall at TX queue. Consider we don't do XDP on NAPI poll(), the only possible fix is to call xdp_do_flush_map() immediately after xdp_do_redirect(). Note, this in fact won't try to batch packets through devmap,

[PATCH V4 net 1/3] Revert "tuntap: add missing xdp flush"

This reverts commit 762c330d670e3d4b795cf7a8d761866fdd1eef49. The reason is we try to batch packets for devmap which causes calling xdp_do_flush() in the process context. Simply disabling preemption may not work since process may move among processors which lead xdp_do_flush() to miss some flushes

[PATCH V4 net 1/3] Revert "tuntap: add missing xdp flush"

This reverts commit 762c330d670e3d4b795cf7a8d761866fdd1eef49. The reason is we try to batch packets for devmap which causes calling xdp_do_flush() in the process context. Simply disabling preemption may not work since process may move among processors which lead xdp_do_flush() to miss some flushes

  1   2   3   4   5   6   7   8   9   10   >