[PATCH 5.4,4.19 2/2] tracing: Increase PERF_MAX_TRACE_SIZE to handle Sentinel1 and docker together

4338d28c60 ---[ end trace 83ab3e8e16275e49 ]--- ``` Link: https://lkml.kernel.org/r/20210831043723.13481-2-robb...@gentoo.org Signed-off-by: Robin H. Johnson Signed-off-by: Steven Rostedt (VMware) Signed-off-by: Thadeu Lima de Souza Cascardo --- include/linux/trace_events.h | 2 +- 1 file changed,

[PATCH 5.15,5.10 2/2] tracing: Increase PERF_MAX_TRACE_SIZE to handle Sentinel1 and docker together

4338d28c60 ---[ end trace 83ab3e8e16275e49 ]--- ``` Link: https://lkml.kernel.org/r/20210831043723.13481-2-robb...@gentoo.org Signed-off-by: Robin H. Johnson Signed-off-by: Steven Rostedt (VMware) Signed-off-by: Thadeu Lima de Souza Cascardo --- include/linux/trace_events.h | 2 +- 1 file changed,

[PATCH 5.15,5.10,5.4,4.19 0/2] Fix warning when tracing with large filenames

The warning described on patch "tracing: Increase PERF_MAX_TRACE_SIZE to handle Sentinel1 and docker together" can be triggered with a perf probe on do_execve with a large path. As PATH_MAX is larger than PERF_MAX_TRACE_SIZE (2048 before the patch), the warning will trigger. The fix was included

[PATCH 5.15,5.10,5.4,4.19 1/2] tracing: Show size of requested perf buffer

y: Robin H. Johnson Signed-off-by: Steven Rostedt (VMware) Signed-off-by: Thadeu Lima de Souza Cascardo --- kernel/trace/trace_event_perf.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/kernel/trace/trace_event_perf.c b/kernel/trace/trace_event_perf.c index 083f648e3265..61

Re: [PATCH] platform: x86: Typo fix in the file classmate-laptop.c

On Wed, Mar 17, 2021 at 02:13:43PM +0530, Bhaskar Chowdhury wrote: > > s/derefence/dereference/ > > Signed-off-by: Bhaskar Chowdhury Acked-by: Thadeu Lima de Souza Cascardo > --- > drivers/platform/x86/classmate-laptop.c | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [PATCH v4] usb: gadget: configfs: Fix KASAN use-after-free

kernel.org > > --- > > Changes in v2: > > Changes in v3: > > - Change commit description > > Changes in v4: > > - Fix build error and adapt patch to kernel-5.12-rc1. > >Replace definition "MAX_USB_STRING_WITH_NULL_LEN" with > >"US

[PATCH] powerpc/perf: prevent mixed EBB and non-EBB events

B and non-EBB events from being add to the same PMU will just revert to the previous behavior and the test will succeed. Fixes: 1908dc911792 (perf: Tweak perf_event_attr::exclusive semantics) Signed-off-by: Thadeu Lima de Souza Cascardo --- arch/powerpc/perf/core-book3s.c | 20

Re: [PATCH v3] usb: gadget: configfs: Fix KASAN use-after-free

gadget. > > -- > balbi I tested this with dummy_hcd on top of a 5.8 kernel and I got lsusb to respond with an error instead of the right manufacturer string, after overwriting such a string after binding. With the patch applied, after the string is overwritten, lsusb will show the updated string. Because of commit 81c7462883b0cc0a4eeef0687f80ad5b5baee5f6 ("USB: replace hardcode maximum usb string length by definition"), the patch will need a fixup. Should I send a v2 with my sign-off? Thanks. Cascardo.

Re: [PATCH 1/2] dccp: ccid: move timers to struct dccp_sock

On Mon, Nov 09, 2020 at 02:15:53PM -0800, Jakub Kicinski wrote: > On Mon, 9 Nov 2020 18:31:34 -0300 Thadeu Lima de Souza Cascardo wrote: > > > Which paths are those (my memory of this code is waning)? I thought > > > disconnect is only called from the user space s

Re: [PATCH 1/2] dccp: ccid: move timers to struct dccp_sock

On Mon, Nov 09, 2020 at 01:15:54PM -0800, Jakub Kicinski wrote: > On Mon, 9 Nov 2020 18:09:09 -0300 Thadeu Lima de Souza Cascardo wrote: > > On Mon, Nov 09, 2020 at 09:49:38AM -0800, Jakub Kicinski wrote: > > > On Mon, 9 Nov 2020 08:48:28 -0300 Thadeu Lima de Souza Cascardo wrote

Re: [PATCH 1/2] dccp: ccid: move timers to struct dccp_sock

On Mon, Nov 09, 2020 at 09:49:38AM -0800, Jakub Kicinski wrote: > On Mon, 9 Nov 2020 08:48:28 -0300 Thadeu Lima de Souza Cascardo wrote: > > On Fri, Oct 16, 2020 at 03:30:16PM -0700, Jakub Kicinski wrote: > > > On Tue, 13 Oct 2020 19:18:48 +0200 Kleber Sacilotto de Souza wro

Re: [PATCH 1/2] dccp: ccid: move timers to struct dccp_sock

On Fri, Oct 16, 2020 at 03:30:16PM -0700, Jakub Kicinski wrote: > On Tue, 13 Oct 2020 19:18:48 +0200 Kleber Sacilotto de Souza wrote: > > From: Thadeu Lima de Souza Cascardo > > > > When dccps_hc_tx_ccid is freed, ccid timers may still trigger. The reason > > d

Re: [PATCH 1/2] dccp: ccid: move timers to struct dccp_sock

On Wed, Oct 14, 2020 at 08:43:22PM -0700, Jakub Kicinski wrote: > On Tue, 13 Oct 2020 19:18:48 +0200 Kleber Sacilotto de Souza wrote: > > From: Thadeu Lima de Souza Cascardo > > > > When dccps_hc_tx_ccid is freed, ccid timers may still trigger. The reason > > d

Re: [LTP] [PATCH] syscall/ptrace08: Simplify the test.

endent on some other behavior/commit that has changed. It passes on 5.4, for example. I'll try to investigate further. Cascardo. > --- > testcases/kernel/syscalls/ptrace/ptrace08.c | 120 ++-- > 1 file changed, 60 insertions(+), 60 deletions(-) > > diff --git a/testc

Re: [PATCH] net/scm: Fix typo in SCM_RIGHTS compat refactoring

> Link: https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-August/216156.html > Reported-by: "Alex Xu (Hello71)" > Link: https://lore.kernel.org/lkml/1596812929.lz7fuo8r2w.none@localhost/ > Suggested-by: Thadeu Lima de Souza Cascardo > Fixes: c0029de50982 ("net/scm: Re

Re: wine fails to start with seccomp updates for v5.9-rc1

[1] seemed related and pointed out at c0029de50982 ("net/scm: Regularize compat handling of scm_detach_fds()"). The use of CMSG_USER_DATA instead of CMSG_COMPAT_DATA seems fishy. Alex, can you try applying the patch below? Cascardo. [1] https://lists.ozlabs.org/pipermail/linuxppc-dev/20

[PATCH] selftests/powerpc: return skip code for spectre_v2

as Vulnerable. Signed-off-by: Thadeu Lima de Souza Cascardo --- tools/testing/selftests/powerpc/security/spectre_v2.c | 8 1 file changed, 8 insertions(+) diff --git a/tools/testing/selftests/powerpc/security/spectre_v2.c b/tools/testing/selftests/powerpc/security/spectre_v2.c index 8c6b982af2a8

[PATCH] nbd: allocate sufficient space for NBD_CMD_STATUS

this on a 32-bit x86 with 15 entries, by loading with nbds_max=15. It failed with -EMSGSIZE, while it worked with 14 or 16 entries. Signed-off-by: Thadeu Lima de Souza Cascardo --- drivers/block/nbd.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c

[PATCH] nbd: allocate sufficient space for NBD_CMD_STATUS

this on a 32-bit x86 with 15 entries, by loading with nbds_max=15. It failed with -EMSGSIZE, while it worked with 14 or 16 entries. Signed-off-by: Thadeu Lima de Souza Cascardo --- drivers/block/nbd.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c

Re: [PATCH] x86/speculation/srbds: do not try to turn mitigation off when not supported

On Mon, Jun 15, 2020 at 10:28:58AM +0200, Borislav Petkov wrote: > On Tue, Jun 09, 2020 at 02:43:13PM -0300, Thadeu Lima de Souza Cascardo wrote: > > When SRBDS is mitigated by TSX OFF, update_srbds_msr will still read and > > Are you talking about this case in srbds_se

[PATCH] x86/speculation/srbds: do not try to turn mitigation off when not supported

"mitigation". Signed-off-by: Thadeu Lima de Souza Cascardo Acked-by: John Johansen Acked-by: Steve Beattie Cc: sta...@vger.kernel.org --- arch/x86/kernel/cpu/bugs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/kernel/cpu/bugs.c b/arch/x86/kernel/cpu/bu

[PATCH v2] selftests/seccomp: use 90s as timeout

. Signed-off-by: Thadeu Lima de Souza Cascardo --- tools/testing/selftests/seccomp/settings | 1 + 1 file changed, 1 insertion(+) create mode 100644 tools/testing/selftests/seccomp/settings diff --git a/tools/testing/selftests/seccomp/settings b/tools/testing/selftests/seccomp/settings new file

[PATCH] selftests/seccomp: use 90s as timeout

. Signed-off-by: Thadeu Lima de Souza Cascardo --- tools/testing/selftests/seccomp/settings | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftests/seccomp/settings b/tools/testing/selftests/seccomp/settings index d61f00d8cad3..ba4d85f74cd6 100644 --- a/tools

[tip: refs/heads/timers/urgent] alarmtimer: Use EOPNOTSUPP instead of ENOTSUPP

The following commit has been merged into the refs/heads/timers/urgent branch of tip: Commit-ID: f18ddc13af981ce3c7b7f26925f099e7c6929aba Gitweb: https://git.kernel.org/tip/f18ddc13af981ce3c7b7f26925f099e7c6929aba Author:Thadeu Lima de Souza Cascardo AuthorDate:Tue, 03

Re: [PATCH v3] sched/core: Fix uclamp ABI bug, clean up and robustify sched_read_attr() ABI logic and code

> Ingo Hi, Ingo. Thanks for the patch. It works just fine for me, I have only one comment about it, below. Acked-by: Thadeu Lima de Souza Cascardo Tested-by: Thadeu Lima de Souza Cascardo I also tested LTP, chrt, and that 5.2 (before the breaking commit) and 5.3 with your patch behave the

[PATCH] alarmtimer: use EOPNOTSUPP instead of ENOTSUPP

we get "95 Operation not supported". Signed-off-by: Thadeu Lima de Souza Cascardo Fixes: 1c6b39ad3f01 (alarmtimers: Return -ENOTSUPP if no RTC device is present) --- kernel/time/alarmtimer.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/time/alarmtimer.c b/kern

[PATCH 1/2] sched: sched_getattr should return E2BIG, not EFBIG

As documented and the behavior before commit 22400674945c (sched: Simplify return logic in sched_read_attr()), sched_getattr should return E2BIG instead of EFBIG when there is not enough space to copy sched_attr. Signed-off-by: Thadeu Lima de Souza Cascardo Fixes: 22400674945c (sched: Simplify

[PATCH 2/2] sched: allow sched_getattr with old size

with this solution is that userspace will ignore there are non-default utilization clamps, but it's arguable whether returning E2BIG in this case makes sense when that same userspace doesn't know about those values anyway. Signed-off-by: Thadeu Lima de Souza Cascardo Fixes: a509a7cd7974 (sched/uclamp

Re: [PATCH] selftests/ftrace: Select an existing function in kprobe_eventname test

ter_functions (if the file exists). > This fixes a similar problem for me. Tested-by: Thadeu Lima de Souza Cascardo > Signed-off-by: Steven Rostedt (VMware) > --- > diff --git a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_eventname.tc > b/tools/testing/selftests/ftrac

Re: [PATCH] selftests/ftrace: avoid failure when trying to probe a notrace function

On Mon, Jul 08, 2019 at 02:56:18PM -0400, Steven Rostedt wrote: > On Mon, 8 Jul 2019 15:19:33 -0300 > Thadeu Lima de Souza Cascardo wrote: > > > Check that the function is on available_filter_functions. If it's not, > > mark the test as unresolved, instead of failing it.

[PATCH] selftests/ftrace: avoid failure when trying to probe a notrace function

Check that the function is on available_filter_functions. If it's not, mark the test as unresolved, instead of failing it. Signed-off-by: Thadeu Lima de Souza Cascardo --- tools/testing/selftests/ftrace/test.d/kprobe/kprobe_eventname.tc | 1 + 1 file changed, 1 insertion(+) diff --git a/tools

[tip:perf/urgent] perf annotate: Fix build on 32 bit for BPF annotation

Commit-ID: 01e985e900d3e602e9b1a55372a8e5274012a417 Gitweb: https://git.kernel.org/tip/01e985e900d3e602e9b1a55372a8e5274012a417 Author: Thadeu Lima de Souza Cascardo AuthorDate: Wed, 3 Apr 2019 16:44:52 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 2 May 2019 16:00:19

PING: Re: [PATCH] perf annotate: Fix build on 32 bit for BPF annotation

On Wed, Apr 03, 2019 at 09:34:02PM +, Song Liu wrote: > > > > On Apr 3, 2019, at 12:44 PM, Thadeu Lima de Souza Cascardo > > wrote: > > > > Commit 6987561c9e86 ("perf annotate: Enable annotation of BPF programs") > > adds > > suppor

[PATCH] perf annotate: Fix build on 32 bit for BPF annotation

Commit 6987561c9e86 ("perf annotate: Enable annotation of BPF programs") adds support for BPF programs annotations but the new code does not build on 32-bit. Fixes: 6987561c9e86 ("perf annotate: Enable annotation of BPF programs") Signed-off-by: Thadeu Lima de Souza Cascardo

Re: [PATCH] nvme: create 'paths' entries for hidden controllers

On Fri, Oct 05, 2018 at 09:32:45AM +0200, Christoph Hellwig wrote: > On Fri, Sep 28, 2018 at 04:17:20PM -0300, Thadeu Lima de Souza Cascardo wrote: > > When using initramfs-tools with only the necessary dependencies to mount > > the root filesystem, it will fail to include nvme dri

Re: [PATCH] nvme: create 'paths' entries for hidden controllers

On Fri, Oct 05, 2018 at 09:32:45AM +0200, Christoph Hellwig wrote: > On Fri, Sep 28, 2018 at 04:17:20PM -0300, Thadeu Lima de Souza Cascardo wrote: > > When using initramfs-tools with only the necessary dependencies to mount > > the root filesystem, it will fail to include nvme dri

[PATCH v2] nvme: create 'paths' entries for hidden controllers

Hellwig Cc: Potnuri Bharat Teja Cc: Keith Busch Cc: Hannes Reinecke Cc: Martin K. Petersen Signed-off-by: Thadeu Lima de Souza Cascardo --- Documentation/ABI/testing/sysfs-block-nvme | 10 drivers/nvme/host/core.c | 2 ++ drivers/nvme/host/multipath.c

[PATCH v2] nvme: create 'paths' entries for hidden controllers

Hellwig Cc: Potnuri Bharat Teja Cc: Keith Busch Cc: Hannes Reinecke Cc: Martin K. Petersen Signed-off-by: Thadeu Lima de Souza Cascardo --- Documentation/ABI/testing/sysfs-block-nvme | 10 drivers/nvme/host/core.c | 2 ++ drivers/nvme/host/multipath.c

[PATCH] nvme: create 'paths' entries for hidden controllers

Hellwig Cc: Potnuri Bharat Teja Cc: Keith Busch Cc: Hannes Reinecke Cc: Martin K. Petersen Signed-off-by: Thadeu Lima de Souza Cascardo --- drivers/nvme/host/core.c | 2 ++ drivers/nvme/host/multipath.c | 28 ++-- drivers/nvme/host/nvme.h | 9 + 3

[PATCH] nvme: create 'paths' entries for hidden controllers

Hellwig Cc: Potnuri Bharat Teja Cc: Keith Busch Cc: Hannes Reinecke Cc: Martin K. Petersen Signed-off-by: Thadeu Lima de Souza Cascardo --- drivers/nvme/host/core.c | 2 ++ drivers/nvme/host/multipath.c | 28 ++-- drivers/nvme/host/nvme.h | 9 + 3

Re: [PATCH] ftrace: use non-archaic spelling of failes

On Thu, May 31, 2018 at 08:15:45AM -0700, Joe Perches wrote: > On Thu, 2018-05-31 at 09:17 -0300, Thadeu Lima de Souza Cascardo wrote: > > diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c > [] > > @@ -4788,7 +4788,7 @@ ftrace_set_addr(struct ftrace_ops *ops, unsigned

Re: [PATCH] ftrace: use non-archaic spelling of failes

On Thu, May 31, 2018 at 08:15:45AM -0700, Joe Perches wrote: > On Thu, 2018-05-31 at 09:17 -0300, Thadeu Lima de Souza Cascardo wrote: > > diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c > [] > > @@ -4788,7 +4788,7 @@ ftrace_set_addr(struct ftrace_ops *ops, unsigned

[PATCH] ftrace: use non-archaic spelling of failes

Signed-off-by: Thadeu Lima de Souza Cascardo --- kernel/trace/ftrace.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c index 8d83bcf9ef69..b218cee1f18c 100644 --- a/kernel/trace/ftrace.c +++ b/kernel/trace/ftrace.c @@ -4788,7

[PATCH] ftrace: use non-archaic spelling of failes

Signed-off-by: Thadeu Lima de Souza Cascardo --- kernel/trace/ftrace.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c index 8d83bcf9ef69..b218cee1f18c 100644 --- a/kernel/trace/ftrace.c +++ b/kernel/trace/ftrace.c @@ -4788,7

Re: [PATCH] fs/binfmt_misc.c: do not allow offset overflow

On Tue, May 29, 2018 at 03:08:54PM -0700, Andrew Morton wrote: > On Tue, 29 May 2018 10:56:48 -0300 Thadeu Lima de Souza Cascardo > wrote: > > > It's possible to overflow the offset to get a negative value, which might > > crash the system, or possibly leak kernel data. >

Re: [PATCH] fs/binfmt_misc.c: do not allow offset overflow

On Tue, May 29, 2018 at 03:08:54PM -0700, Andrew Morton wrote: > On Tue, 29 May 2018 10:56:48 -0300 Thadeu Lima de Souza Cascardo > wrote: > > > It's possible to overflow the offset to get a negative value, which might > > crash the system, or possibly leak kernel data. >

[PATCH] fs/binfmt_misc.c: do not allow offset overflow

on Ubuntu. Signed-off-by: Thadeu Lima de Souza Cascardo Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2") Cc: sta...@vger.kernel.org --- fs/binfmt_misc.c | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/fs/binfmt_misc.c b/fs/binfmt_misc.c index a41b48f82a70..4d

[PATCH] fs/binfmt_misc.c: do not allow offset overflow

on Ubuntu. Signed-off-by: Thadeu Lima de Souza Cascardo Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2") Cc: sta...@vger.kernel.org --- fs/binfmt_misc.c | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/fs/binfmt_misc.c b/fs/binfmt_misc.c index a41b48f82a70..4d

Re: Problem with global pages changeset and kvm

On Tue, May 08, 2018 at 07:15:06AM -0700, Dave Hansen wrote: > Thanks for the excellent bug report! > > On 05/08/2018 02:37 AM, Thadeu Lima de Souza Cascardo wrote: > > 2) The bad address is next to do_syscall_64 on the host. > > So a host address leaked into a guest oops?

Re: Problem with global pages changeset and kvm

On Tue, May 08, 2018 at 07:15:06AM -0700, Dave Hansen wrote: > Thanks for the excellent bug report! > > On 05/08/2018 02:37 AM, Thadeu Lima de Souza Cascardo wrote: > > 2) The bad address is next to do_syscall_64 on the host. > > So a host address leaked into a guest oops?

Problem with global pages changeset and kvm

et me know how I can help investigate this further, or test fixes for this. Cascardo.

Problem with global pages changeset and kvm

et me know how I can help investigate this further, or test fixes for this. Cascardo.

Re: [PATCH 4.15 00/72] 4.15.16-stable review

armhf and ppc64el. I have some problems with the arm64 cross toolchain, not related to the kernel, so builds for arm64 have been failing. So I can report the status for that right now. Boot tested on ppc64el on a Unicamp minicloud VM. Using it without any problems on my Thinkpad X200 with the amd64 kernel. Cascardo.

Re: [PATCH 4.15 00/72] 4.15.16-stable review

armhf and ppc64el. I have some problems with the arm64 cross toolchain, not related to the kernel, so builds for arm64 have been failing. So I can report the status for that right now. Boot tested on ppc64el on a Unicamp minicloud VM. Using it without any problems on my Thinkpad X200 with the amd64 kernel. Cascardo.

Re: [PATCH 4.15 000/105] 4.15.14-stable review

arm64, armhf, i386, ppc64el, s390x. Survived a kernel build on ppc64el (KVM VM) and amd64 (Thinkpad X200). Cascardo.

Re: [PATCH 4.15 000/105] 4.15.14-stable review

arm64, armhf, i386, ppc64el, s390x. Survived a kernel build on ppc64el (KVM VM) and amd64 (Thinkpad X200). Cascardo.

Re: [PATCH net-next v2 2/2] cxgb4: collect hardware dump in second kernel

k that's what Stephen Hemminger meant when he said to use sysfs. No need at all for any special crashdd. Just add an attribute or attribute group to the device object. Otherwise, as Eric Biederman pointed out, you should just add that data into the vmcore before you kexec, so you don't even need to l

Re: [PATCH net-next v2 2/2] cxgb4: collect hardware dump in second kernel

all for any special crashdd. Just add an attribute or attribute group to the device object. Otherwise, as Eric Biederman pointed out, you should just add that data into the vmcore before you kexec, so you don't even need to look at a different file, and the driver does not even need t

Re: [PATCH] test_bpf: Fix testing with CONFIG_BPF_JIT_ALWAYS_ON=y on other arches

On Tue, Mar 20, 2018 at 09:05:15AM -0700, Yonghong Song wrote: > > > On 3/20/18 5:58 AM, Thadeu Lima de Souza Cascardo wrote: > > Function bpf_fill_maxinsns11 is designed to not be able to be JITed on > > x86_64. So, it fails when CONFIG_BPF_JIT_ALWAYS_ON=y, and > >

Re: [PATCH] test_bpf: Fix testing with CONFIG_BPF_JIT_ALWAYS_ON=y on other arches

On Tue, Mar 20, 2018 at 09:05:15AM -0700, Yonghong Song wrote: > > > On 3/20/18 5:58 AM, Thadeu Lima de Souza Cascardo wrote: > > Function bpf_fill_maxinsns11 is designed to not be able to be JITed on > > x86_64. So, it fails when CONFIG_BPF_JIT_ALWAYS_ON=y, and > >

[PATCH] test_bpf: Fix testing with CONFIG_BPF_JIT_ALWAYS_ON=y on other arches

S_ON=y") Signed-off-by: Thadeu Lima de Souza Cascardo <casca...@canonical.com> --- lib/test_bpf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/test_bpf.c b/lib/test_bpf.c index 2efb213716faa..3e9335493fe49 100644 --- a/lib/test_bpf.c +++ b/lib/test_bpf.c @@

[PATCH] test_bpf: Fix testing with CONFIG_BPF_JIT_ALWAYS_ON=y on other arches

S_ON=y") Signed-off-by: Thadeu Lima de Souza Cascardo --- lib/test_bpf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/test_bpf.c b/lib/test_bpf.c index 2efb213716faa..3e9335493fe49 100644 --- a/lib/test_bpf.c +++ b/lib/test_bpf.c @@ -5467,7 +5467,7 @@ static s

Re: [PATCH 4.15 00/52] 4.15.12-stable review

86, ppc64el, arm64, armhf and s390x. Boot tested on ppc64el virtual machine and amd64 Thinkpad X200. Cascardo.

Re: [PATCH 4.15 00/52] 4.15.12-stable review

86, ppc64el, arm64, armhf and s390x. Boot tested on ppc64el virtual machine and amd64 Thinkpad X200. Cascardo.

Re: [PATCH 4.15 000/122] 4.15.8-stable review

On Thu, Mar 08, 2018 at 09:27:23AM -0800, Greg Kroah-Hartman wrote: > On Thu, Mar 08, 2018 at 07:35:41AM -0300, Thadeu Lima de Souza Cascardo wrote: > > On Wed, Mar 07, 2018 at 11:36:52AM -0800, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for

Re: [PATCH 4.15 000/122] 4.15.8-stable review

On Thu, Mar 08, 2018 at 09:27:23AM -0800, Greg Kroah-Hartman wrote: > On Thu, Mar 08, 2018 at 07:35:41AM -0300, Thadeu Lima de Souza Cascardo wrote: > > On Wed, Mar 07, 2018 at 11:36:52AM -0800, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for

Re: [PATCH 4.15 000/122] 4.15.8-stable review

z > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-4.15.y > and the diffstat can be found below. > > thanks, > > greg k-h > > ----- Merged, built on amd64, arm64, armhf, i386, ppc64el, s390x. Cascardo.

Re: [PATCH 4.15 000/122] 4.15.8-stable review

z > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-4.15.y > and the diffstat can be found below. > > thanks, > > greg k-h > > ----- Merged, built on amd64, arm64, armhf, i386, ppc64el, s390x. Cascardo.

Re: [PATCH 5/6] platform/x86: make device_attribute const

For classmate-laptop.c Acked-by: Thadeu Lima de Souza Cascardo <casca...@holoscopio.com>

Re: [PATCH 5/6] platform/x86: make device_attribute const

For classmate-laptop.c Acked-by: Thadeu Lima de Souza Cascardo

[PATCH] tty: fix comment typo s/repsonsible/responsible/

Signed-off-by: Thadeu Lima de Souza Cascardo <casca...@cascardo.eti.br> --- drivers/tty/tty_io.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c index e6d1a65..309d250 100644 --- a/drivers/tty/tty_io.c +++ b/drivers/tty/tt

[PATCH] tty: fix comment typo s/repsonsible/responsible/

Signed-off-by: Thadeu Lima de Souza Cascardo --- drivers/tty/tty_io.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c index e6d1a65..309d250 100644 --- a/drivers/tty/tty_io.c +++ b/drivers/tty/tty_io.c @@ -3370,7 +3370,7

[PATCH v2] powerpc: make /proc/self/stack always print the current stack

, while it's not, which some may consider as a bug. This is also consistent with some other architectures, like x86 and arm, at least. Signed-off-by: Thadeu Lima de Souza Cascardo <casca...@canonical.com> --- arch/powerpc/kernel/stacktrace.c | 9 - 1 file changed, 8 insertions

[PATCH v2] powerpc: make /proc/self/stack always print the current stack

, while it's not, which some may consider as a bug. This is also consistent with some other architectures, like x86 and arm, at least. Signed-off-by: Thadeu Lima de Souza Cascardo --- arch/powerpc/kernel/stacktrace.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git

[PATCH] powerpc: fix /proc/self/stack

For the current task, the kernel stack would only tell the last time the process was rescheduled, if ever. Use the current stack pointer for the current task. This is also consistent with some other architectures. Signed-off-by: Thadeu Lima de Souza Cascardo <casca...@canonical.com> ---

[PATCH] powerpc: fix /proc/self/stack

For the current task, the kernel stack would only tell the last time the process was rescheduled, if ever. Use the current stack pointer for the current task. This is also consistent with some other architectures. Signed-off-by: Thadeu Lima de Souza Cascardo --- arch/powerpc/kernel

[PATCH] serial: core: remove silly test for uart_state

The polling functions were checking for a NULL uart_state, which is indexed from uart_driver->state. It should be always allocated and non-NULL when the tty_driver is registered, and line should not be larger than the tty_driver->num anyways. Signed-off-by: Thadeu Lima de Souza Cascardo

[PATCH] serial: core: remove silly test for uart_state

The polling functions were checking for a NULL uart_state, which is indexed from uart_driver->state. It should be always allocated and non-NULL when the tty_driver is registered, and line should not be larger than the tty_driver->num anyways. Signed-off-by: Thadeu Lima de Souza Ca

Re: [PATCH] serial/8250: remove comment about schedule_timeout

On Thu, Jan 05, 2017 at 04:40:16PM +, One Thousand Gnomes wrote: > On Thu, 5 Jan 2017 13:48:40 -0200 > Thadeu Lima de Souza Cascardo <casca...@canonical.com> wrote: > > > Ted T'so has added the function size_fifo in 1999 for the 2.3 series > > [1], a long time a

Re: [PATCH] serial/8250: remove comment about schedule_timeout

On Thu, Jan 05, 2017 at 04:40:16PM +, One Thousand Gnomes wrote: > On Thu, 5 Jan 2017 13:48:40 -0200 > Thadeu Lima de Souza Cascardo wrote: > > > Ted T'so has added the function size_fifo in 1999 for the 2.3 series > > [1], a long time ago. > > > > Durin

[PATCH] serial/8250: remove comment about schedule_timeout

Souza Cascardo <casca...@canonical.com> Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org> Cc: Jiri Slaby <jsl...@suse.com> Cc: linux-ser...@vger.kernel.org Cc: Russell King <rmk+ker...@armlinux.org.uk> Cc: Theodore Ts'o <ty...@mit.edu> --- drivers/tty/serial/8250/8250

[PATCH] serial/8250: remove comment about schedule_timeout

Souza Cascardo Cc: Greg Kroah-Hartman Cc: Jiri Slaby Cc: linux-ser...@vger.kernel.org Cc: Russell King Cc: Theodore Ts'o --- drivers/tty/serial/8250/8250_port.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/serial/8250/8250_port.c b/drivers/tty/serial/8250

Re: [PATCHv2 1/7] ppc bpf/jit: Disable classic BPF JIT on ppc64le

u Lima de Souza Cascardo <casca...@redhat.com> > > Cc: sta...@vger.kernel.org > Cc: Matt Evans <m...@ozlabs.org> > Cc: Denis Kirjanov <k...@linux-powerpc.org> > Cc: Michael Ellerman <m...@ellerman.id.au> > Cc: Paul Mackerras <pau...@samba.org> >

Re: [PATCHv2 1/7] ppc bpf/jit: Disable classic BPF JIT on ppc64le

u Lima de Souza Cascardo > > Cc: sta...@vger.kernel.org > Cc: Matt Evans > Cc: Denis Kirjanov > Cc: Michael Ellerman > Cc: Paul Mackerras > Cc: Alexei Starovoitov > Cc: Daniel Borkmann > Cc: "David S. Miller" > Cc: Ananth N Mavinakayanahalli

Re: [PATCH] ppc: Fix BPF JIT for ABIv2

On Tue, Jun 21, 2016 at 09:15:48PM +1000, Michael Ellerman wrote: > On Tue, 2016-06-21 at 14:28 +0530, Naveen N. Rao wrote: > > On 2016/06/20 03:56PM, Thadeu Lima de Souza Cascardo wrote: > > > On Sun, Jun 19, 2016 at 11:19:14PM +0530, Naveen N. Rao wrote: > > > >

Re: [PATCH] ppc: Fix BPF JIT for ABIv2

On Tue, Jun 21, 2016 at 09:15:48PM +1000, Michael Ellerman wrote: > On Tue, 2016-06-21 at 14:28 +0530, Naveen N. Rao wrote: > > On 2016/06/20 03:56PM, Thadeu Lima de Souza Cascardo wrote: > > > On Sun, Jun 19, 2016 at 11:19:14PM +0530, Naveen N. Rao wrote: > > > >

Re: [PATCH] ppc: Fix BPF JIT for ABIv2

On Sun, Jun 19, 2016 at 11:19:14PM +0530, Naveen N. Rao wrote: > On 2016/06/17 10:00AM, Thadeu Lima de Souza Cascardo wrote: > > On Fri, Jun 17, 2016 at 10:53:21PM +1000, Michael Ellerman wrote: > > > On Tue, 2016-07-06 at 13:32:23 UTC, "Naveen N. Rao" wrote: > >

Re: [PATCH] ppc: Fix BPF JIT for ABIv2

On Sun, Jun 19, 2016 at 11:19:14PM +0530, Naveen N. Rao wrote: > On 2016/06/17 10:00AM, Thadeu Lima de Souza Cascardo wrote: > > On Fri, Jun 17, 2016 at 10:53:21PM +1000, Michael Ellerman wrote: > > > On Tue, 2016-07-06 at 13:32:23 UTC, "Naveen N. Rao" wrote: > >

[PATCH] ppc: Fix BPF JIT for ABIv2

ced Naveen's patchset and the latest changes in ppc tree for a better way to check for ABI versions. However, since the issue described below affect mainline and stable kernels, would you consider applying it before merging your two patchsets, so that we can more easily backport the fix? Thanks. C

[PATCH] ppc: Fix BPF JIT for ABIv2

ced Naveen's patchset and the latest changes in ppc tree for a better way to check for ABI versions. However, since the issue described below affect mainline and stable kernels, would you consider applying it before merging your two patchsets, so that we can more easily backport the fix? Thanks. Casc

Re: [PATCH 1/1] net: ehea: avoid null pointer dereference

ked-by: Thadeu Lima de Souza Cascardo <casca...@debian.org> > --- > drivers/net/ethernet/ibm/ehea/ehea_main.c | 9 - > 1 file changed, 4 insertions(+), 5 deletions(-) > > diff --git a/drivers/net/ethernet/ibm/ehea/ehea_main.c > b/drivers/net/ethernet/ibm/ehea/ehea_ma

Re: [PATCH 1/1] net: ehea: avoid null pointer dereference

On Tue, May 17, 2016 at 10:28:54PM +0200, Heinrich Schuchardt wrote: > ehea_get_port may return NULL. Do not dereference NULL value. > > Fixes: 8c4877a4128e ("ehea: Use the standard logging functions") > Signed-off-by: Heinrich Schuchardt Acked-by: Thadeu

Re: [PATCH] ehea: Drop owner assignment from platform_driver

On Fri, Feb 19, 2016 at 07:06:46AM -0500, Julia Lawall wrote: > On Fri, 19 Feb 2016, Thadeu Lima de Souza Cascardo wrote: > > On Fri, Feb 19, 2016 at 04:52:19PM +0530, Amitoj Kaur Chawla wrote: > > > platform_driver does not need to set an owner, it will be populated by >

Re: [PATCH] ehea: Drop owner assignment from platform_driver

On Fri, Feb 19, 2016 at 07:06:46AM -0500, Julia Lawall wrote: > On Fri, 19 Feb 2016, Thadeu Lima de Souza Cascardo wrote: > > On Fri, Feb 19, 2016 at 04:52:19PM +0530, Amitoj Kaur Chawla wrote: > > > platform_driver does not need to set an owner, it will be populated by >

Re: [PATCH] ehea: Drop owner assignment from platform_driver

.owner = THIS_MODULE, > .of_match_table = ehea_device_table, > }, > .probe = ehea_probe_adapter, > -- > 1.9.1 > NACK. ehea does not use platform_driver_register, it uses ibmebus_register_driver, which does not set owner. Cascardo.

Re: [PATCH] ehea: Drop owner assignment from platform_driver

.of_match_table = ehea_device_table, > }, > .probe = ehea_probe_adapter, > -- > 1.9.1 > NACK. ehea does not use platform_driver_register, it uses ibmebus_register_driver, which does not set owner. Cascardo.

Re: [BUG] skb corruption and kernel panic at forwarding with fragmentation

On Wed, Jan 06, 2016 at 11:11:41PM +0300, Konstantin Khlebnikov wrote: > On Wed, Jan 6, 2016 at 10:59 PM, Cong Wang wrote: > > On Wed, Jan 6, 2016 at 11:15 AM, Konstantin Khlebnikov > > wrote: > >> Looks like this happens because ip_options_fragment() relies on > >> correct ip options length in

Re: [BUG] skb corruption and kernel panic at forwarding with fragmentation

On Wed, Jan 06, 2016 at 11:11:41PM +0300, Konstantin Khlebnikov wrote: > On Wed, Jan 6, 2016 at 10:59 PM, Cong Wang wrote: > > On Wed, Jan 6, 2016 at 11:15 AM, Konstantin Khlebnikov > > wrote: > >> Looks like this happens because ip_options_fragment()

Re: [PATCH] IGMP: Inhibit reports for local multicast groups

fact, IPv4 local multicast addresses are ignored when Linux bridge multicast snooping adds a new group. static int br_ip4_multicast_add_group(struct net_bridge *br, ... if (ipv4_is_local_multicast(group)) return 0; Cascardo. -- To unsubscribe from this list: send the

Re: [PATCH] IGMP: Inhibit reports for local multicast groups

, ... if (ipv4_is_local_multicast(group)) return 0; Cascardo. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org

  1   2   3   >