Re: Question about the ipi_raise filter usage and output

On Wed, Feb 7, 2024 at 10:28 AM richard clark wrote: > > On Tue, Feb 6, 2024 at 5:39 PM Valentin Schneider wrote: > > > > You should have access to the generic fields which include the CPU from > > which the event happens. Any of "CPU", "cpu" or &

Re: Question about the ipi_raise filter usage and output

On Tue, Feb 6, 2024 at 5:39 PM Valentin Schneider wrote: > > You should have access to the generic fields which include the CPU from > which the event happens. Any of "CPU", "cpu" or "common_cpu" would match > this. > > So if you're on a recent enough kernel (v6.6 or above AFAICT), you should >

Re: Question about the ipi_raise filter usage and output

On Tue, Feb 6, 2024 at 12:05 AM Valentin Schneider wrote: > > On 05/02/24 14:39, Mark Rutland wrote: > > [adding Valentin] > > > > Thanks! > > > On Mon, Feb 05, 2024 at 08:06:09AM -0500, Steven Rostedt wrote: > >> On Mon, 5 Feb 2024 10:28:57 + > >> Mark Rutland wrote: > >> > >> > > I try to

Re: Question about the ipi_raise filter usage and output

Hi Steve, On Mon, Feb 5, 2024 at 6:38 PM Steven Rostedt wrote: > > On Mon, 5 Feb 2024 17:57:29 +0800 > richard clark wrote: > > > I try to write below: > > echo 'target_cpus == 11 && reason == "Function call interrupts"' > > > events/ipi/ipi_ra

Question about the ipi_raise filter usage and output

Hi guys, With the ipi_raise event enabled and filtered with: echo 'reason == "Function call interrupts"' > filter, then the 'cat trace' output below messages: ... insmod-3355[010] 1.. 24479.230381: ipi_raise: target_mask=,0bff (Function call interrupts) ... The above output is

Re: Why KASAN doesn't detect this stack oob fault?

Willy Tarreau 于2020年8月23日周日 下午12:56写道： > > On Sun, Aug 23, 2020 at 11:04:34AM +0800, richard clark wrote: > > Hi guys, > > > > I ins a kmod with below code in a KASAN enabled kernel ( > > 5.7.0, > > CONFIG_KASAN=y > > CONFIG_KASAN_GENERIC=y >

Why KASAN doesn't detect this stack oob fault?

Hi guys, I ins a kmod with below code in a KASAN enabled kernel ( 5.7.0, CONFIG_KASAN=y CONFIG_KASAN_GENERIC=y CONFIG_KASAN_OUTLINE=y): static int kmod_init(void) { int i; int arr[4]; for (i = 0; i < 20; i++) { arr[i] = i; printk("arr[%d] = %d\n", i, arr[i]); }

[PATCH] Update the obsolete comments of 'register_blkdev' func

>From the code of 'register_blkdev(...)', the major number range should be in [1..BLKDEV_MAJOR_HASH_SIZE-1] while not [1..BLKDEV_MAJOR_MAX] in case of calling 'register_blkdev(...) with @major = 0, so correct the wrong info of the function's comments Signed-off-by: Richard Clark Cc: J

External kmod build failed on KASAN-enabled kernel

Hi, The same kmod source code can be built on KASAN-disabled kernel (5.7.0), but after enable it with CONFIG_KASAN=y, the kmod can't build on the new installed KASAN-enabled kernel with below error message, seems no relevant answers for this issue with google: root@build-ws:/home/mm/slab# make