[Bug 1896504] Re: tc/ebpf: unable to use BPF_FUNC_skb_change_head

2020-09-22 Thread Thadeu Lima de Souza Cascardo
** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
   Status: Incomplete

** Changed in: linux (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896504

Title:
  tc/ebpf: unable to use BPF_FUNC_skb_change_head

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896504/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892860] Re: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B-arm64

2020-09-21 Thread Thadeu Lima de Souza Cascardo
UCT mentions commits 9060cb719e61b685ec0102574e10337fa5f445ea (specific
to AF_ALG) and ff7b11aa481f682e0e9711abfeb7d03f5cd612bf (all sockets).

The other commit we should care about is
6d8c50dcb029872b298eea68cc6209c866fd3e14 ("socket: close race condition
between sock_close() and sockfs_setattr()").

If you have that one, you should expect ENOENT (which is what the test
case expects), but only if sock_close wins the race. If it doesn't, you
might still succeed at sockfs_setattr, and then we get this test
failure.

Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892860

Title:
  af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on
  B-arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892860/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892860] Re: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B-arm64

2020-09-21 Thread Thadeu Lima de Souza Cascardo
It seems that you *can* chown a socket, so this call just works fine. No
races with close needed. So, it seems to be a bogus assumption on the
part of the test.

Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892860

Title:
  af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on
  B-arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892860/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896008] Re: linux-libc-dev in proposed cause seccomp_bpf from seccomp in ubuntu_kernel_selftests to fail on F-oem-5.6

2020-09-21 Thread Thadeu Lima de Souza Cascardo
So, the test is running with the newer definition as it is picked up
from linux-libc-dev. But the kernel (linux-oem-5.6, in this case)
doesn't know about it. So it fails.

However, any binaries out there would be using the old definition, which
the linux-oem-5.6 should accept just fine. I guess we will be stuck with
this double definition forever as "we don't break userspace ABI *ever*"
*coff*.

IMHO, it's just fine leaving this for next cycle. But pick it up, cause
we will start seeing binaries out there using the new definition.

Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896008

Title:
  linux-libc-dev in proposed cause seccomp_bpf from seccomp in
  ubuntu_kernel_selftests to fail on F-oem-5.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted

2020-09-18 Thread Thadeu Lima de Souza Cascardo
I pushed a version for focal on my ppa. It is based on the latest
version found on groovy, so there should be other changes besides the
one for setting a better default of crashkernel on /etc/zipl.conf.

It's at ppa:cascardo/kdump2. Note that if the user has changed the value
from the previous default, it will be kept as is. This is done per
entry.

Cascardo.

** Changed in: makedumpfile (Ubuntu Groovy)
   Status: Confirmed => In Progress

** Changed in: makedumpfile (Ubuntu Focal)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877533

Title:
  [20.10 FEAT] Increase the crashkernel setting if the root volume is
  luks2-encrypted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-09-16 Thread Thadeu Lima de Souza Cascardo
** Description changed:

+ [Impact]
+ kmemcaches will fail to be created after they have just been removed but not 
completely ripped out. This will cause some drivers (like lvm snapshots) to 
properly work and cause kernel traces to go on the logs.
+ 
+ [Test case]
+ See comment #9.
+ 
+ [Regression potential]
+ The fix reverts a commit, so we go back to a state of a previously released 
kernel, where a leak was possible. The regression here, though, is better than 
the impact that will also lead to a different leak and prevent users from 
correctly using LVM snapshots.
+ 
+ =
+ 
  One of my bionic servers with HWE 5.4.0 hangs on boot (apparently while
  starting LVM snapshots) after upgrading from Linux 5.4.0-42 to 5.4.0-47,
  with the following trace:
  
    [   29.126292] kobject_add_internal failed for :a-152 with -EEXIST, 
don't try to register things with the same name in the same directory.
    [   29.138854] BUG: kernel NULL pointer dereference, address: 
0020
    [   29.145977] #PF: supervisor read access in kernel mode
    [   29.145979] #PF: error_code(0x) - not-present page
    [   29.145981] PGD 0 P4D 0
    [   29.158800] Oops:  [#1] SMP NOPTI
    [   29.162468] CPU: 6 PID: 2532 Comm: lvm Not tainted 5.4.0-46-generic 
#50~18.04.1-Ubuntu
    [   29.170378] Hardware name: Supermicro AS -2023US-TR4/H11DSU-iN, BIOS 1.3 
07/15/2019
    [   29.178038] RIP: 0010:free_percpu+0x120/0x1f0
    [   29.183786] Code: 43 64 48 01 d0 49 39 c4 0f 83 71 ff ff ff 65 8b 05 a5 
4e bc 58 48 8b 15 0e 4e 20 01 48 98 48 8b 3c c2 4c 01 e7 e8 f0 97 02 00 <48> 8b 
58 20 48 8b 53 38 e9 48 ff ff ff f3 c3 48 8b 43 38 48 89 45
    [   29.202530] RSP: 0018:a2f69c3d38e8 EFLAGS: 00010046
    [   29.209204] RAX:  RBX: 92202ff397c0 RCX: 
a880a000
    [   29.216336] RDX: cf35c0f24f2cc3c0 RSI: 43817c451b92afcb RDI: 

    [   29.223469] RBP: a2f69c3d3918 R08:  R09: 
a74a5300
    [   29.230609] R10: a2f69c3d3820 R11:  R12: 
cf35c0f24f14c3c0
    [   29.237745] R13: cf362fb2a054c3c0 R14: 0287 R15: 
0008
    [   29.244878] FS:  7f93a04b0900() GS:913faed8() 
knlGS:
    [   29.252961] CS:  0010 DS:  ES:  CR0: 80050033
    [   29.258707] CR2: 0020 CR3: 003fa9d9 CR4: 
003406e0
    [   29.265883] Call Trace:
    [   29.268346]  __kmem_cache_release+0x1a/0x30
    [   29.273913]  __kmem_cache_create+0x4f9/0x550
    [   29.278192]  ? __kmalloc_node+0x1eb/0x320
    [   29.282205]  ? kvmalloc_node+0x31/0x80
    [   29.285962]  create_cache+0x120/0x1f0
    [   29.291003]  kmem_cache_create_usercopy+0x17d/0x270
    [   29.295882]  kmem_cache_create+0x16/0x20
    [   29.300152]  dm_bufio_client_create+0x1af/0x3f0 [dm_bufio]
    [   29.305644]  ? snapshot_map+0x5e0/0x5e0 [dm_snapshot]
    [   29.310693]  persistent_read_metadata+0x1ed/0x500 [dm_snapshot]
    [   29.316627]  ? _cond_resched+0x19/0x40
    [   29.320384]  snapshot_ctr+0x79e/0x910 [dm_snapshot]
    [   29.325276]  dm_table_add_target+0x18d/0x370
    [   29.329552]  table_load+0x12a/0x370
    [   29.333045]  ctl_ioctl+0x1e2/0x590
    [   29.336450]  ? retrieve_status+0x1c0/0x1c0
    [   29.340551]  dm_ctl_ioctl+0xe/0x20
    [   29.343958]  do_vfs_ioctl+0xa9/0x640
    [   29.347547]  ? ksys_semctl.constprop.19+0xf7/0x190
    [   29.352337]  ksys_ioctl+0x75/0x80
    [   29.355663]  __x64_sys_ioctl+0x1a/0x20
    [   29.359421]  do_syscall_64+0x57/0x190
    [   29.363094]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
    [   29.368144] RIP: 0033:0x7f939f0286d7
    [   29.371732] Code: b3 66 90 48 8b 05 b1 47 2d 00 64 c7 00 26 00 00 00 48 
c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 
01 f0 ff ff 73 01 c3 48 8b 0d 81 47 2d 00 f7 d8 64 89 01 48
    [   29.390478] RSP: 002b:7ffe918df168 EFLAGS: 0202 ORIG_RAX: 
0010
    [   29.398045] RAX: ffda RBX: 561c107f672c RCX: 
7f939f0286d7
    [   29.405175] RDX: 561c1107c610 RSI: c138fd09 RDI: 
0009
    [   29.412309] RBP: 7ffe918df220 R08: 7f939f59d120 R09: 
7ffe918defd0
    [   29.419442] R10: 561c1107c6c0 R11: 0202 R12: 
7f939f59c4e6
    [   29.426623] R13: 7f939f59c4e6 R14: 7f939f59c4e6 R15: 
7f939f59c4e6
    [   29.433778] Modules linked in: dm_snapshot dm_bufio dm_zero 
nls_iso8859_1 ipmi_ssif input_leds amd64_edac_mod edac_mce_amd joydev kvm_amd 
kvm ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi sunrpc ip_tables x_tables autofs4 btrfs zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core 
bcache crc64 

[Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47

2020-09-16 Thread Thadeu Lima de Souza Cascardo
After reverting commit 79ffe7107b13042c69c4a06394175362121b06b5
(upstream commit d38a2b7a9c939e6d7329ab92b96559ccebf7b135) ("mm:
memcg/slab: fix memory leak at non-root kmem_cache destroy"), things
seem to go back to normal.

The probable reason this one causes a problem is because it has:

@@ -326,6 +326,14 @@ int slab_unmergeable(struct kmem_cache *s)
if (s->refcount < 0)
return 1;
 
+#ifdef CONFIG_MEMCG_KMEM
+   /*
+* Skip the dying kmem_cache.
+*/
+   if (s->memcg_params.dying)
+   return 1;
+#endif
+
return 0;
 }

So, this causes the same-sized slab to become unmergeable, and when a
new slab is created, it will fail creating the sysfs entry.

I haven't investigated why memcg is at play here, and why this one would
be dying, that would involve memcgs being removed during the operation.
But not allowing merges will certainly cause problems here.

The other issue is that this memcg code has been totally
replaced/discarded on 5.9, so it will make things interesting trying to
upstream a proper fix here.

But considering the commit fix a leak and here we will have a different
leak and failures to create slabs, the revert is preferable for now.

Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894780

Title:
  Oops and hang when starting LVM snapshots on 5.4.0-47

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894780/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853193] Re: copy_file_range test fails with linux 5.3+ on bionic

2020-09-11 Thread Thadeu Lima de Souza Cascardo
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/ppc64el/g/glibc/20200911_170104_5f83a@/log.gz

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/ppc64el/g/glibc/20200911_180721_529c2@/log.gz

Comparing the two results, glibc 2.27-3ubuntu1.3 is definitively better.
So, marking as verified.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853193

Title:
  copy_file_range test fails with linux 5.3+ on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1853193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770480] Re: preadv2 test does not consider new flag from linux 4.16

2020-09-11 Thread Thadeu Lima de Souza Cascardo
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/ppc64el/g/glibc/20200911_170104_5f83a@/log.gz

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/ppc64el/g/glibc/20200911_180721_529c2@/log.gz

Comparing the two results, glibc 2.27-3ubuntu1.3 is definitively better.
So, marking as verified.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770480

Title:
  preadv2 test does not consider new flag from linux 4.16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1770480/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888507] Re: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

2020-08-26 Thread Thadeu Lima de Souza Cascardo
** Description changed:

- We need to run BPF filters to analyse and monitor network traffic. The
- BPF filters are created by skydive (http://skydive.network). Currently
- skydive fails to install BPF filters on s390x (using Ubuntu 18.04
- currently, soon moving to Ubuntu 20.04).
+ [Impact]
+ Some bpf programs will fail to execute on s390x, returning EFAULT when they 
should be able to read user memory.
+ 
+ [Test case]
+ apt-get source linux
+ mkdir -p /usr/lib/perf/
+ cp -a linux-5.4.0/tools/perf/include /usr/lib/perf/
+ probe_read=$(grep -w probe_read /usr/lib/perf/include/bpf/bpf.h)
+ probe_read_user=${probe_read//read/read_user}
+ sed -i "/probe_read)/i$probe_read_user" /usr/lib/perf/include/bpf/bpf.h
+ probe_read_user_str=${probe_read//read/read_user_str}
+ sed -i "/probe_read)/i$probe_read_user_str" /usr/lib/perf/include/bpf/bpf.h
+ 
+ ed - linux-5.4.0/tools/perf/examples/bpf/augmented_raw_syscalls.c << EOF
+ 100c
+ int string_len = probe_read_user_str(_arg->value, arg_len, arg);
+ .
+ w
+ EOF
+ perf trace -eopenat,augmented_raw_syscalls.c cat /etc/passwd > /dev/null
+ 
+ You should see:
+  0.332 ( 0.002 ms): cat/3223 openat(dfd: CWD, filename: "/etc/passwd")
 = 3
+ instead of
+  0.334 ( 0.003 ms): cat/3739 openat(dfd: CWD, filename: "")   
 = 3
+ 
+ [Potential regressions]
+ One potential regression is that unprivileged code can be able to exploit the 
changes to read or write kernel memory.
+ 
+ 
+ --
+ 
+ 
+ We need to run BPF filters to analyse and monitor network traffic. The BPF 
filters are created by skydive (http://skydive.network). Currently skydive 
fails to install BPF filters on s390x (using Ubuntu 18.04 currently, soon 
moving to Ubuntu 20.04).
  
  Because of these failures, we decided to try the BPF samples that come
  with the kernel first. These samples also fail on s390x while they work
  fine on Intel.
  
  shense@boe-build:~/bionic/samples/bpf$ uname -a
  Linux boe-build 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:40:36 UTC 
2020 s390x s390x s390x GNU/Linux
  
  Example instructions:
  
  sudo apt install -y dpkg-dev clang llvm libelf-dev
  sudo apt-get source linux-image-unsigned-$(uname -r)
  cd linux-4.15.0/
  make headers_install
  make samples/bpf/
  
  Errors:
  
  shense@boe-build:~/bionic/samples/bpf$ sudo ./test_map_in_map
  [sudo] password for shense:
  invalid relo for insn[4].code 0x85
  bpf_load_program() err=22
  0: (bf) r7 = r1
  1: (b7) r1 = 0
  2: (63) *(u32 *)(r10 -32) = r1
  3: (bf) r1 = r7
  4: (85) call unknown#-1
  BPF_CALL uses reserved fields
  0: (bf) r7 = r1
  1: (b7) r1 = 0
  2: (63) *(u32 *)(r10 -32) = r1
  3: (bf) r1 = r7
  4: (85) call unknown#-1
  BPF_CALL uses reserved fields
- 
  
  shense@boe-build:~/bionic/samples/bpf$ sudo ./map_perf_test
  invalid relo for insn[22].code 0x85
  bpf_load_program() err=22
  0: (bf) r7 = r1
  1: (18) r1 = 0x207265743a25646e
  3: (7b) *(u64 *)(r10 -16) = r1
  4: (18) r1 = 0x705f616c6c6f632e
  6: (7b) *(u64 *)(r10 -24) = r1
  7: (18) r1 = 0x5f6c72755f686d61
  9: (7b) *(u64 *)(r10 -32) = r1
  10: (18) r1 = 0x7420737472657373
  12: (7b) *(u64 *)(r10 -40) = r1
  13: (18) r1 = 0x4661696c65642061
  15: (7b) *(u64 *)(r10 -48) = r1
  16: (b7) r1 = 0
  17: (73) *(u8 *)(r10 -8) = r1
  18: (b7) r2 = 1
  19: (7b) *(u64 *)(r10 -72) = r2
  20: (63) *(u32 *)(r10 -76) = r1
  21: (bf) r1 = r7
  22: (85) call unknown#-1
  BPF_CALL uses reserved fields
  0: (bf) r7 = r1
  1: (18) r1 = 0x207265743a25646e
  3: (7b) *(u64 *)(r10 -16) = r1
  4: (18) r1 = 0x705f616c6c6f632e
  6: (7b) *(u64 *)(r10 -24) = r1
  7: (18) r1 = 0x5f6c72755f686d61
  9: (7b) *(u64 *)(r10 -32) = r1
  10: (18) r1 = 0x7420737472657373
  12: (7b) *(u64 *)(r10 -40) = r1
  13: (18) r1 = 0x4661696c65642061
  15: (7b) *(u64 *)(r10 -48) = r1
  16: (b7) r1 = 0
  17: (73) *(u8 *)(r10 -8) = r1
  18: (b7) r2 = 1
  19: (7b) *(u64 *)(r10 -72) = r2
  20: (63) *(u32 *)(r10 -76) = r1
  21: (bf) r1 = r7
  22: (85) call unknown#-1
  BPF_CALL uses reserved fields

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888507

Title:
  [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888507/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

2020-08-25 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888332

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888332/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

2020-08-25 Thread Thadeu Lima de Souza Cascardo
** Description changed:

+ [Impact]
+ Code that touches DSCR user MSR does not set dscr_inherit, which breaks DSCR 
restore doing context switches and inheritance when forking. DSCR is used to 
control cache hinting. This is caused by lack of kernel interrupt when the DSCR 
user MSR is written, which is controlled by FSCR which would otherwise cause a 
facility unavailable interrupt.
+ 
+ [Test case]
+ apt-get source linux
+ cd linux-5.4.0/tools/testing/tools/selftests/powerpc/
+ make -j 32
+ make -C dscr run_tests
+ make -C ptrace run_tests
+ make -C tm run_tests
+ 
+ Look up for "not ok" versus "ok", specially for dscr_inherit_exec_test,
+ ptrace-tar and tm-resched-tar.
+ 
+ [Potential regression]
+ Manipulating DSCR might break on different machines (with DTs containing 
+ /cpus/ibm,powerpc-cpu-features, for example). Code that does so might crash 
because the facility unavailable interrupt handling might be not working 
correctly.
+ 
+ 
+ 
  Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node)
  
-  # selftests: powerpc/dscr: dscr_inherit_exec_test 
-  # test: dscr_inherit_exec_test
-  # tags: git_version:unknown
-  # Parent DSCR 1 was not inherited over exec (kernel value)
-  # Child didn't exit cleanly
-  # failure: dscr_inherit_exec_test
-  not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1
+  # selftests: powerpc/dscr: dscr_inherit_exec_test
+  # test: dscr_inherit_exec_test
+  # tags: git_version:unknown
+  # Parent DSCR 1 was not inherited over exec (kernel value)
+  # Child didn't exit cleanly
+  # failure: dscr_inherit_exec_test
+  not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888332

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888332/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

2020-08-25 Thread Thadeu Lima de Souza Cascardo
Apparently, cherry-picking 0828137e8f16721842468e33df0460044a0c588b
("powerpc/64s: Don't init FSCR_DSCR in __init_FSCR()") fixes the issue.
Which explains why 5.8 does not show the problem.

Building a kernel with that patch applied so I can test it.

Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888332

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888332/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

2020-08-25 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888332

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888332/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

2020-08-25 Thread Thadeu Lima de Souza Cascardo
** Also affects: ubuntu-kernel-tests/trunk
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-kernel-tests

** No longer affects: ubuntu-kernel-tests/trunk

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888332

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888332/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888334] Re: [Potential Regression] tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on B/E/F

2020-08-25 Thread Thadeu Lima de Souza Cascardo
*** This bug is a duplicate of bug 1888332 ***
https://bugs.launchpad.net/bugs/1888332

Same thing as LP: #1888332. When writing to the privileged DSCR MSR
before running the remainder of the test, things will just work. This is
hinting again to dscr_inherit being unset when using the user DSCR MSR.

Cascardo.

** This bug has been marked a duplicate of bug 1888332
   [Potential Regression] dscr_inherit_exec_test from powerpc in 
ubuntu_kernel_selftests failed on B/E/F

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888334

Title:
  [Potential Regression] tm-resched-dscr from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888334/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888339] Re: [Potential Regression] ptrace-tar from powerpc in ubuntu_kernel_selftests failed on B/E/F

2020-08-25 Thread Thadeu Lima de Souza Cascardo
*** This bug is a duplicate of bug 1888332 ***
https://bugs.launchpad.net/bugs/1888332

Same issue as LP: #1888332. If we use DSCR privileged MSR when writing
in the tracee, it will set dscr_inherit, which will properly restore the
DSCR that is written by the tracer.

Cascardo.

** This bug has been marked a duplicate of bug 1888332
   [Potential Regression] dscr_inherit_exec_test from powerpc in 
ubuntu_kernel_selftests failed on B/E/F

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888339

Title:
  [Potential Regression] ptrace-tar from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888339/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

2020-08-25 Thread Thadeu Lima de Souza Cascardo
This test failure is caused by the kernel not setting dscr_inherit when
the user dscr MSR is written to. Which is caused by FSCR not raising a
facility unavailable interrupt. Which is ironic as one of the other
patches that is backported is 993e3d96fd08c3ebf7566e43be9b8cd622063e6d
("powerpc/64s: Don't let DT CPU features set FSCR_DSCR"), which should
prevent this situation.

The reason dscr_inherit_test does not fail is because it writes to the
kernel MSR first. Changing dscr_inherit_exec_test to do the same, it
passes.

Testing 5.8 shows that it's fixed somehow, though I haven't found the
exact commit that would fix this. Reverting
912c0a7f2b5daa3cbb2bc10f303981e493de73bd ("powerpc/64s: Save FSCR to
init_task.thread.fscr after feature init") seems reasonable here.

But failing to inherit dscr would cause cache performance regressions
that are hard to justify respining the kernel for.

Cascardo.

** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888332

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888332/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888332] Re: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on B/E/F

2020-08-25 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Eoan)
   Status: Incomplete => Confirmed

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888332

Title:
  [Potential Regression] dscr_inherit_exec_test from powerpc in
  ubuntu_kernel_selftests failed on B/E/F

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888332/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892411] [NEW] Package perf-trace examples and include files

2020-08-20 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

[Impact]
perf trace can work with BPF code and is able to use clang to build C code to 
do it. Currently, it won't be able to build them as it requires some include 
files that it looks at /usr/lib/perf/include/bpf/.

As this path is not dependent on the kernel version, shipping the latest
code would make sense as long as headers are backwards compatible.
Example code could be packaged on a versioned directory in a versioned
package.

[Test case]
$ sudo perf trace -e 
open,openat,/usr/lib/perf/examples/bpf/augmented_raw_syscalls.c cat /etc/passwd 
> /dev/null
 0.000 ( 0.027 ms): cat/2256 openat(dfd: CWD, filename: "/etc/ld.so.cache", 
flags: RDONLY|CLOEXEC) = 3
 0.058 ( 0.009 ms): cat/2256 openat(dfd: CWD, filename: 
"/lib/s390x-linux-gnu/libc.so.6", flags: RDONLY|CLOEXEC) = 3
 0.307 ( 0.004 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/locale-archive", flags: RDONLY|CLOEXEC) = 3
 0.326 ( 0.007 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/share/locale/locale.alias", flags: RDONLY|CLOEXEC) = 3
 0.361 ( 0.005 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/C.UTF-8/LC_IDENTIFICATION", flags: RDONLY|CLOEXEC) = 3
 0.373 ( 0.004 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/s390x-linux-gnu/gconv/gconv-modules.cache") = 3
 0.389 ( 0.004 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/C.UTF-8/LC_MEASUREMENT", flags: RDONLY|CLOEXEC) = 3
 0.403 ( 0.003 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/C.UTF-8/LC_TELEPHONE", flags: RDONLY|CLOEXEC) = 3
 0.415 ( 0.004 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/C.UTF-8/LC_ADDRESS", flags: RDONLY|CLOEXEC) = 3
 0.428 ( 0.004 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/C.UTF-8/LC_NAME", flags: RDONLY|CLOEXEC) = 3
 0.440 ( 0.004 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/C.UTF-8/LC_PAPER", flags: RDONLY|CLOEXEC) = 3
 0.456 ( 0.003 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/C.UTF-8/LC_MESSAGES", flags: RDONLY|CLOEXEC) = 3
 0.464 ( 0.003 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/C.UTF-8/LC_MESSAGES/SYS_LC_MESSAGES", flags: RDONLY|CLOEXEC) = 
3
 0.475 ( 0.004 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/C.UTF-8/LC_MONETARY", flags: RDONLY|CLOEXEC) = 3
 0.489 ( 0.003 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/C.UTF-8/LC_COLLATE", flags: RDONLY|CLOEXEC) = 3
 0.511 ( 0.004 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/C.UTF-8/LC_TIME", flags: RDONLY|CLOEXEC) = 3
 0.525 ( 0.003 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/C.UTF-8/LC_NUMERIC", flags: RDONLY|CLOEXEC) = 3
 0.536 ( 0.004 ms): cat/2256 openat(dfd: CWD, filename: 
"/usr/lib/locale/C.UTF-8/LC_CTYPE", flags: RDONLY|CLOEXEC) = 3
 0.565 ( 0.003 ms): cat/2256 openat(dfd: CWD, filename: "/etc/passwd")  
   = 3

[Potential regression]
We might ship incompatible code with the running kernel. It might break 
building such examples.
Or we might break the old contens of the packages we are adding files to.

** Affects: linux (Ubuntu)
 Importance: Low
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
     Status: In Progress

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Groovy)
 Importance: Low
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Groovy)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892411

Title:
  Package perf-trace examples and include files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892411/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888507] Re: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

2020-08-20 Thread Thadeu Lima de Souza Cascardo
** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888507

Title:
  [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888507/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888507] Re: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

2020-08-18 Thread Thadeu Lima de Souza Cascardo
Hi.

So if I understand correctly, this will be 18.04 userspace on top of a
20.04 kernel, that is, 5.4. I noticed 5.4 also lacks probe_read_user. I
will keep working on a backport of this to 5.4 kernel, then. Let me know
if there is anything else missing here.

Thanks.
Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888507

Title:
  [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888507/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891812] Re: Missing Linux Kernel Mitigations

2020-08-17 Thread Thadeu Lima de Souza Cascardo
https://aws.amazon.com/security/security-bulletins/AWS-2019-004/

According to Amazon advisory, fixes have been applied and "no customer
action is required at the Infrastructure level". Reading from other
sources [1], I can only conclude that Amazon has not provided the knobs
needed to do the mitigation. This explains the issue for MDS and TAA.
SSB is likely vulnerable for the same reasons, but I'll look for their
advisory and update it here. Same thing for ITLB multihit.

One possible avenue of investigation is verifying if VERW is being used
and providing the mitigation for the MDS case.

Regards.
Cascardo.

[1]
https://www.reddit.com/r/aws/comments/br38fl/sidechannel_md_clear_cpu_flags_not_being_passed/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891812

Title:
  Missing Linux Kernel Mitigations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1891812/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891565] Re: oss4 does not build on ppc64el on groovy

2020-08-14 Thread Thadeu Lima de Souza Cascardo
Now building on ppa:cascardo/ppa.

** Patch added: "Fix for groovy"
   
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1891565/+attachment/5401581/+files/oss4_4.2-build2010-5ubuntu7.debdiff

** Changed in: binutils (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891565

Title:
  oss4 does not build on ppc64el on groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1891565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891565] Re: oss4 does not build on ppc64el on groovy

2020-08-14 Thread Thadeu Lima de Souza Cascardo
So, dot-symbols on powerpc are not a thing on userspace since a while
(from gcc 3.4 times). And, then, I realized this header comes directly
from alsa, and for a different reason, this same section has already
been dropped there. So applying the same changes makes sense here.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891565

Title:
  oss4 does not build on ppc64el on groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1891565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888507] Re: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

2020-08-14 Thread Thadeu Lima de Souza Cascardo
Hi.

So, we clarified that some of the problems were not caused by the kernel
at all. The only thing missing is support to probe_read_kernel and
probe_read_user on 4.15 kernels. Is that needed for the offering?

If I didn't get it right, I am sorry. So, in order for us to meet your
expectations, I'll try to understand better what are the needs here:

1) Do you want support on 4.15 kernel on Ubuntu 18.04, right? Or is the
offering based on Ubuntu 20.04?

2) Do you expect to be able to use LLVM/clang 10? Or is LLVM/clang 8
sufficient for your needs? The bug has only been open for the linux
package, so we would need to get folks behind LLVM involved, or try to
fix this on the kernel somehow, which might delay things a little. Being
able to use LLVM/clang 8, it seems, would be a best fit to a short
deadline.

3) Building and running samples/bpf/ is not something we test. And
though it might help us catch regressions, I would suppose it's not a
requirement for the offering. If I am wrong in that supposition, are you
relying on the source package for something? Or is anything shipped in
binary packages incorrect (like that s930x typo) preventing things from
building correctly?

Right now, the best course we have, in case what you need is the probe
functions on 4.15 is to get this available on a kernel in -proposed in 3
weeks, and in -updates in 6 weeks. Would that work?

Thank you.
Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888507

Title:
  [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888507/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891565] Re: oss4 does not build on ppc64el on groovy

2020-08-13 Thread Thadeu Lima de Souza Cascardo
** Also affects: binutils (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891565

Title:
  oss4 does not build on ppc64el on groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1891565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891565] [NEW] oss4 does not build on ppc64el on groovy

2020-08-13 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

When building the focal version of oss4 with groovy version of binutils,
it fails with:

/tmp/ccoZchTf.s: Assembler messages:
/tmp/ccoZchTf.s: Error: invalid attempt to declare external version name as 
default in symbol `.snd_pcm_hw_params_set_rate_near@@ALSA_0.9.0rc4'
make[1]: *** [Makefile:16: pcm.lo] Error 1

Downgrading binutils to 2.34-6ubuntu1 fixes the problem. This works with
gcc-9 9.3.0-10ubuntu2. Upgrading to groovy gcc-9 9.3.0-17ubuntu1 will
force the upgrade of binutils, so can't be tested with the working
version of binutils. Using the latest version of gcc-9 or gcc-10 from
groovy with the broken binutils is still broken, so a complete upgrade
does not fix the problem.

The following diff does fix the problem with binutils 2.35-2ubuntu1, though:
$ diff -u lib/libsalsa/alsa-symbols.h.old lib/libsalsa/alsa-symbols.h
--- lib/libsalsa/alsa-symbols.h.old 2020-08-13 22:47:28.249358919 +
+++ lib/libsalsa/alsa-symbols.h 2020-08-13 22:43:35.730423956 +
@@ -35,7 +35,7 @@
__asm__ (".symver ." #real ",." #name "@" #version)
 # define default_symbol_version(real, name, version)   \
__asm__ (".symver " #real "," #name "@@" #version); \
-   __asm__ (".symver ." #real ",." #name "@@" #version)
+// __asm__ (".symver ." #real ",." #name "@@" #version)
 #else
 # define symbol_version(real, name, version) \
__asm__ (".symver " #real "," #name "@" #version)

** Affects: oss4 (Ubuntu)
 Importance: Medium
     Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Changed in: oss4 (Ubuntu)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: oss4 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: oss4 (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891565

Title:
  oss4 does not build on ppc64el on groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1891565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884640] Re: evdi 1.6.0+dfsg-1ubuntu3 ADT test failure with linux-5.8 5.8.0-1.2

2020-08-11 Thread Thadeu Lima de Souza Cascardo
** Patch added: "Fix for groovy"
   
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1884640/+attachment/5400792/+files/evdi_1.7.0+dfsg-1ubuntu1.debdiff

** Changed in: evdi (Ubuntu)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: evdi (Ubuntu)
   Importance: Undecided => Medium

** Changed in: evdi (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884640

Title:
  evdi 1.6.0+dfsg-1ubuntu3 ADT test failure with linux-5.8 5.8.0-1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1884640/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884640] Re: evdi 1.6.0+dfsg-1ubuntu3 ADT test failure with linux-5.8 5.8.0-1.2

2020-08-11 Thread Thadeu Lima de Souza Cascardo
** Description changed:

+ [Impact]
+ evdi-dkms won't build with later kernels than 5.5. In some cases (upstream 
version 1.7.0), it won't build specifically on ppc64el. The fix includes a 
missing header that is indirectly included on other arches.
+ 
+ [Test case]
+ Install the package with a 5.8 kernel. Install linux-headers-5.8.0-12-generic 
and evdi-dkms. Check that the dkms has built for the 5.8 kernel, at 
/lib/modules/5.8.0-12-generic/updates/dkms/evdi.ko.
+ 
+ [Regression potential]
+ Updates to dkms packages can break the modules. They could build ok, but not 
load successfully. And even after loaded just fine, they can stop providing the 
correct functionality, or introduce new bugs.
+ 
+ [Other info]
+ This has been tested to build and load on a ppc64el system running linux 
5.8.0-12-generic and also 5.4.0-37-generic.
+ 
+ 
+ =
+ 
+ 
  Testing failed on:
- amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/e/evdi/20200619_205539_4b87a@/log.gz
- arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/e/evdi/20200619_211747_a93df@/log.gz
- armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/armhf/e/evdi/20200619_210243_40fa8@/log.gz
- ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/e/evdi/20200619_205911_3fda4@/log.gz
- s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/e/evdi/20200619_205610_b6afa@/log.gz
+ amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/e/evdi/20200619_205539_4b87a@/log.gz
+ arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/e/evdi/20200619_211747_a93df@/log.gz
+ armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/armhf/e/evdi/20200619_210243_40fa8@/log.gz
+ ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/e/evdi/20200619_205911_3fda4@/log.gz
+ s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/e/evdi/20200619_205610_b6afa@/log.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884640

Title:
  evdi 1.6.0+dfsg-1ubuntu3 ADT test failure with linux-5.8 5.8.0-1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1884640/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted

2020-08-10 Thread Thadeu Lima de Souza Cascardo
So, of course the patch is useless, as s390x uses zipl. I will work on
upgrade paths during this week, so we can allow upgrades to have the new
setting when the old setting is kept as is.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877533

Title:
  [20.10 FEAT] Increase the crashkernel setting if the root volume is
  luks2-encrypted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted

2020-08-04 Thread Thadeu Lima de Souza Cascardo
Attached is a fix for s390x that is also built at my
ppa:cascardo/kdump2.

** Patch added: "Fix for groovy"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877533/+attachment/5398755/+files/makedumpfile_1.6.7-3ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877533

Title:
  [20.10 FEAT] Increase the crashkernel setting if the root volume is
  luks2-encrypted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted

2020-07-31 Thread Thadeu Lima de Souza Cascardo
I am going to work out on a change to the default crashkernel value on
s390x to match what we do for ppc64el. That will improve the situation
on default installations.

** Changed in: makedumpfile (Ubuntu Groovy)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: makedumpfile (Ubuntu Groovy)
   Status: Won't Fix => In Progress

** Changed in: makedumpfile (Ubuntu Focal)
   Status: Won't Fix => Confirmed

** Changed in: makedumpfile (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877533

Title:
  [20.10 FEAT] Increase the crashkernel setting if the root volume is
  luks2-encrypted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888507] Re: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

2020-07-28 Thread Thadeu Lima de Souza Cascardo
Yep, and the commit that first fixes up these probe_read vs
probe_read_kernel/probe_read_user problems is:

6ae08ae3dea2cfa03dd3665a3c8475c2d429ef47 "bpf: Add probe_read_{user,
kernel} and probe_read_{user, kernel}_str helpers"

So, these helpers are not available until 5.5. We may consider this a
bug, but BPF code will still need to be changed to use the new helpers,
otherwise they will keep failing on s390x.

Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888507

Title:
  [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888507/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888507] Re: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

2020-07-27 Thread Thadeu Lima de Souza Cascardo
After some investigation, I found out that failures caused by "invalid
relo for insn[4].code 0x85" are due to a small typo in some headers.

That has caused LLVM to emit relocations (thinking those missing macro
calls were external function calls) that are not supported by the
loader. This is all in userspace, so no real kernel bugs here. We can
include the typo fixup in the bionic tree, though.

That led to a new failure, caused by faults when trying to read user
memory from the BPF program. I will investigate further.

Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888507

Title:
  [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888507/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886860] Re: cgroup refcount is bogus when cgroup_sk_alloc is disabled

2020-07-27 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Groovy)
   Status: In Progress => Invalid

** Description changed:

- When net_prio and net_cls cgroups are used, cgroup refcount is bogus, as
- it's not incremented anymore, but decremented when sockets are closed.
+ [Impact]
+ When net_prio and net_cls cgroups are used, cgroup refcount is bogus, as it's 
not incremented anymore, but decremented when sockets are closed.
  
  This might lead to crashes possibly because of use-after-free when
  packets are received as shown in LP #1886668.
  
- Cascardo.
+ [Test case]
+ Ran reproducer from comment #2.
+ 
+ [Regression potential]
+ We could break the use of cgroup bpf. The use of cgroup bpf looks to still be 
working from the reproducer.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886860

Title:
  cgroup refcount is bogus when cgroup_sk_alloc is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886860/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886860] Re: cgroup refcount is bogus when cgroup_sk_alloc is disabled

2020-07-27 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Groovy)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Eoan)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886860

Title:
  cgroup refcount is bogus when cgroup_sk_alloc is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886860/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886860] Re: cgroup refcount is bogus when cgroup_sk_alloc is disabled

2020-07-22 Thread Thadeu Lima de Souza Cascardo
Reproducer is here.

https://launchpad.net/~cascardo/+archive/ubuntu/ppa/+sourcepub/11445138
/+listing-archive-extra

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886860

Title:
  cgroup refcount is bogus when cgroup_sk_alloc is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886860/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888381] Re: net test from ubuntu_kernel_selftest will timeout on B-5.0

2020-07-22 Thread Thadeu Lima de Souza Cascardo
Kleber has identified the backport of commit 692d7b5d1f91 ("tls: Fix
recvmsg() to be able to peek across multiple records") as the
responsible for this regression.

It turns out this commit has 4 fixups upstream, 3 of which can be easily
cherry picked, while the fourth one seems related to TLS 1.3 support,
which is not included in our 5.0 kernels yet.

Picking those 3 commits allow the tests to pass without issues.

** Description changed:

+ [Impact]
+ Partial reads on TLS sockets will cause processes to wait indefinitively.
+ 
+ [Test case]
+ Run tls net selftests from the kernel source tree.
+ 
+ [Regression potential]
+ We only touch code on the TLS socket family itself, so regressions on 
subsystems other than the one we are fixing is highly unlikely.
+ 
+ 
+ 
+ 
  Issue found on:
  linux-gke-5.0 - 5.0.0-1045.46 / 5.0.0-1044.45
  linux-oem-osp1 - 5.0.0-1065.70 / 5.0.0-1064.69
  
  The net test in ubuntu_kernel_selftests will timeout and gets killed,
  this issue does not exist in gke 5.0.0-1043.44 and oem-osp1
  5.0.0-1063.68 (the net test passed with 5.0.0-1063.68 without any error)
  
  The test will hang here:
   Opening 127.0.0.1:
   Opening INADDR_ANY:
   bind: Address already in use
   Opening in6addr_any:
   Opening INADDR_ANY:
   bind: Address already in use
   Opening INADDR_ANY: after closing ipv6 socket
   bind: Address already in use
   Timer expired (1800 sec.), nuking pid 27394
  ERROR   ubuntu_kernel_selftests.net ubuntu_kernel_selftests.net 
timestamp=1595327738localtime=Jul 21 10:35:38   Test timeout expired, rc=15
  END ERROR   ubuntu_kernel_selftests.net ubuntu_kernel_selftests.net
  
  Please find the attachment for the complete test log.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888381

Title:
  net test from ubuntu_kernel_selftest will timeout on B-5.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888381/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888507] Re: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

2020-07-22 Thread Thadeu Lima de Souza Cascardo
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888507

Title:
  [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888507/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108

2020-07-09 Thread Thadeu Lima de Souza Cascardo
https://launchpad.net/~cascardo/+archive/ubuntu/ppa/+sourcepub/11419106
/+listing-archive-extra

So, this package on my ppa is built for bionic, but should work on other
series too.

It has a service that will call a wrapper that will start the reproducer
and reboot. The reason for the reboot is because once we add a task to
net_prio cgroup, it will disable cgroup bpf and we can't call the
reproducer again. And the reproducer, though it can cause the refcount
to go below 0 every time, it won't always cause the exact crash from
this bug.

Once you want to disable the reproducer, you should add to the kernel
cmdline the parameter "systemd.mask=cgroup-bpf-net-prio-crash.service".
Then, you need to remove the package and can get your system back.

You may be running some service that will add a task to net_prio or
net_cls cgroup, thus preventing the reproducer to run at all (but not
stop it from rebooting your system over and over again). lxd comes to
mind here.

You may check that it's the case (before installing the reproducer) by looking 
at dmesg and searching for:
cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls 
activation

The following WARN is the demonstration that the refcount underflow has 
happened (though not the crash):
[   12.581125] [ cut here ]
[   12.585021] percpu ref (cgroup_bpf_release_fn) <= 0 (-357) after switching 
to atomic
[   12.585092] WARNING: CPU: 2 PID: 665 at lib/percpu-refcount.c:160 
percpu_ref_switch_to_atomic_rcu+0x12e/0x140

The crash will cause a panic and likely prevent the system from
rebooting, showing you have reproduced the issue.

If you never see the WARN, the bug has been mitigated, though it can
still happen if we modify the reproducer slightly to also change
net_cls.classid.

Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886668

Title:
  linux 4.15.0-109-generic network DoS regression vs -108

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886668/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108

2020-07-09 Thread Thadeu Lima de Souza Cascardo
** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
   Status: Invalid

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Groovy)
   Status: Invalid => In Progress

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Eoan)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886668

Title:
  linux 4.15.0-109-generic network DoS regression vs -108

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886668/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108

2020-07-08 Thread Thadeu Lima de Souza Cascardo
Test kernels at https://people.canonical.com/~cascardo/lp1886668/.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886668

Title:
  linux 4.15.0-109-generic network DoS regression vs -108

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886668/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108

2020-07-08 Thread Thadeu Lima de Souza Cascardo
** Description changed:

  [Impact]
  On systems using cgroups and sockets extensively, like docker, kubernetes, 
lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic.
  
  [Fix]
  Revert the patch that disables sk_alloc cgroup refcounting when tasks are 
added to net_prio cgroup.
  
  [Test case]
- Test that such environments where the issue is reproduced survive some hours 
of uptime. See attached test case that reproduces a different but possibly 
related issue.
+ Test that such environments where the issue is reproduced survive some hours 
of uptime. A different bug was reproduced with a work-in-progress code and was 
not reproduced with the culprit reverted.
  
  [Regression potential]
  The reverted commit fix a memory leak on similar scenarios. But a leak is 
better than a crash. Two other bugs have been opened to track a real fix for 
this issue and the leak.
  
- 
  --
- 
  
  Reported from a user:
  
  Several of our infrastructure VMs recently started crashing (oops
  attached), after they upgraded to -109.  -108 appears to be stable.
  
  Analysing the crash, it appears to be a wild pointer access in a BPF
  filter, which makes this (probably) a network-traffic triggered crash.
  
  [  696.396831] general protection fault:  [#1] SMP PTI
  [  696.396843] Modules linked in: iscsi_target_mod target_core_mod 
ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac 
arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc 
overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid 
sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs 
sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse 
i2c_piix4 pata_acpi floppy
  [  696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic 
#110-Ubuntu
  [  696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018
  [  696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0
  [  696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292
  [  696.397015] RAX: 6d69546e6f697469 RBX:  RCX: 
0014
  [  696.397028] RDX:  RSI: 893fd036 RDI: 
893fb5154800
  [  696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: 

  [  696.397058] R10:  R11: 0003 R12: 
0014
  [  696.397075] R13: 893fb5154800 R14: 0020 R15: 
893fc6ba4d00
  [  696.397091] FS:  () GS:893fdcb8() 
knlGS:
  [  696.397107] CS:  0010 DS:  ES:  CR0: 80050033
  [  696.397119] CR2: 00c0001b4000 CR3: 0006dce0a004 CR4: 
003606e0
  [  696.397135] DR0:  DR1:  DR2: 

  [  696.397152] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  696.397169] Call Trace:
  [  696.397175]  
  [  696.397183]  sk_filter_trim_cap+0xd0/0x1b0
  [  696.397191]  tcp_v4_rcv+0x8b7/0xa80
  [  696.397199]  ip_local_deliver_finish+0x66/0x210
  [  696.397208]  ip_local_deliver+0x7e/0xe0
  [  696.397215]  ? ip_rcv_finish+0x430/0x430
  [  696.397223]  ip_rcv_finish+0x129/0x430
  [  696.397230]  ip_rcv+0x296/0x360
  [  696.397238]  ? inet_del_offload+0x40/0x40
  [  696.397249]  __netif_receive_skb_core+0x432/0xb80
  [  696.397261]  ? skb_send_sock+0x50/0x50
  [  696.397271]  ? tcp4_gro_receive+0x137/0x1a0
  [  696.397280]  __netif_receive_skb+0x18/0x60
  [  696.397290]  ? __netif_receive_skb+0x18/0x60
  [  696.397300]  netif_receive_skb_internal+0x45/0xe0
  [  696.397309]  napi_gro_receive+0xc5/0xf0
  [  696.397317]  xennet_poll+0x9ca/0xbc0
  [  696.397325]  net_rx_action+0x140/0x3a0
  [  696.397334]  __do_softirq+0xe4/0x2d4
  [  696.397344]  irq_exit+0xc5/0xd0
  [  696.397352]  xen_evtchn_do_upcall+0x30/0x50
  [  696.397361]  xen_hvm_callback_vector+0x90/0xa0
  [  696.397371]  
  [  696.397378] RIP: 0010:native_safe_halt+0x12/0x20
  [  696.397390] RSP: 0018:94c4862cbe80 EFLAGS: 0246 ORIG_RAX: 
ff0c
  [  696.397405] RAX: 8efc1800 RBX: 0006 RCX: 

  [  696.397419] RDX:  RSI:  RDI: 

  [  696.397435] RBP: 94c4862cbe80 R08: 0002 R09: 
0001
  [  696.397449] R10: 0010 R11: 0397 R12: 
0006
  [  696.397462] R13:  R14:  R15: 

  [  696.397479]  ? __sched_text_end+0x1/0x1
  [  696.397489]  default_idle+0x20/0x100
  [  696.397499]  

[Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108

2020-07-08 Thread Thadeu Lima de Souza Cascardo
Bugs are LP#1886860 and LP#1886859.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886668

Title:
  linux 4.15.0-109-generic network DoS regression vs -108

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886668/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108

2020-07-08 Thread Thadeu Lima de Souza Cascardo
** Description changed:

+ [Impact]
+ On systems using cgroups and sockets extensively, like docker, kubernetes, 
lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic.
+ 
+ [Fix]
+ Revert the patch that disables sk_alloc cgroup refcounting when tasks are 
added to net_prio cgroup.
+ 
+ [Test case]
+ Test that such environments where the issue is reproduced survive some hours 
of uptime. See attached test case that reproduces a different but possibly 
related issue.
+ 
+ [Regression potential]
+ The reverted commit fix a memory leak on similar scenarios. But a leak is 
better than a crash. Two other bugs have been opened to track a real fix for 
this issue and the leak.
+ 
+ 
+ --
+ 
+ 
  Reported from a user:
  
- Several of our infrastructure VMs recently started crashing (oops 
   
- attached), after they upgraded to -109.  -108 appears to be stable.   
   
-   
   
- Analysing the crash, it appears to be a wild pointer access in a BPF  
   
- filter, which makes this (probably) a network-traffic triggered crash. 
+ Several of our infrastructure VMs recently started crashing (oops
+ attached), after they upgraded to -109.  -108 appears to be stable.
+ 
+ Analysing the crash, it appears to be a wild pointer access in a BPF
+ filter, which makes this (probably) a network-traffic triggered crash.
  
  [  696.396831] general protection fault:  [#1] SMP PTI
  [  696.396843] Modules linked in: iscsi_target_mod target_core_mod 
ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac 
arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc 
overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid 
sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs 
sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse 
i2c_piix4 pata_acpi floppy
  [  696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic 
#110-Ubuntu
  [  696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018
  [  696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0
  [  696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292
  [  696.397015] RAX: 6d69546e6f697469 RBX:  RCX: 
0014
  [  696.397028] RDX:  RSI: 893fd036 RDI: 
893fb5154800
  [  696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: 

  [  696.397058] R10:  R11: 0003 R12: 
0014
  [  696.397075] R13: 893fb5154800 R14: 0020 R15: 
893fc6ba4d00
  [  696.397091] FS:  () GS:893fdcb8() 
knlGS:
  [  696.397107] CS:  0010 DS:  ES:  CR0: 80050033
  [  696.397119] CR2: 00c0001b4000 CR3: 0006dce0a004 CR4: 
003606e0
  [  696.397135] DR0:  DR1:  DR2: 

  [  696.397152] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  696.397169] Call Trace:
  [  696.397175]  
  [  696.397183]  sk_filter_trim_cap+0xd0/0x1b0
  [  696.397191]  tcp_v4_rcv+0x8b7/0xa80
  [  696.397199]  ip_local_deliver_finish+0x66/0x210
  [  696.397208]  ip_local_deliver+0x7e/0xe0
  [  696.397215]  ? ip_rcv_finish+0x430/0x430
  [  696.397223]  ip_rcv_finish+0x129/0x430
  [  696.397230]  ip_rcv+0x296/0x360
  [  696.397238]  ? inet_del_offload+0x40/0x40
  [  696.397249]  __netif_receive_skb_core+0x432/0xb80
  [  696.397261]  ? skb_send_sock+0x50/0x50
  [  696.397271]  ? tcp4_gro_receive+0x137/0x1a0
  [  696.397280]  __netif_receive_skb+0x18/0x60
  [  696.397290]  ? __netif_receive_skb+0x18/0x60
  [  696.397300]  netif_receive_skb_internal+0x45/0xe0
  [  696.397309]  napi_gro_receive+0xc5/0xf0
  [  696.397317]  xennet_poll+0x9ca/0xbc0
  [  696.397325]  net_rx_action+0x140/0x3a0
  [  696.397334]  __do_softirq+0xe4/0x2d4
  [  696.397344]  irq_exit+0xc5/0xd0
  [  696.397352]  xen_evtchn_do_upcall+0x30/0x50
  [  696.397361]  xen_hvm_callback_vector+0x90/0xa0
  [  696.397371]  
  [  696.397378] RIP: 0010:native_safe_halt+0x12/0x20
  [  696.397390] RSP: 0018:94c4862cbe80 EFLAGS: 0246 ORIG_RAX: 
ff0c
  [  696.397405] RAX: 

[Bug 1886859] [NEW] memory is leaked when tasks are moved to net_prio

2020-07-08 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

When net_prio is used without setting ifpriomap and BFP cgroup is used,
memory may be leaked. This was fixed by upstream commit
090e28b229af92dc5b40786ca673999d59e73056, but it had to be reverted to
fix LP #1886668.

When a real fix for this cgroup BFP crash lands, this patch should be
reinstated.

Cascardo.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886859

Title:
  memory is leaked when tasks are moved to net_prio

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886860] [NEW] cgroup refcount is bogus when cgroup_sk_alloc is disabled

2020-07-08 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

When net_prio and net_cls cgroups are used, cgroup refcount is bogus, as
it's not incremented anymore, but decremented when sockets are closed.

This might lead to crashes possibly because of use-after-free when
packets are received as shown in LP #1886668.

Cascardo.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Bionic)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: Confirmed

** Affects: linux (Ubuntu Eoan)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Groovy)
 Importance: Undecided
 Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886860

Title:
  cgroup refcount is bogus when cgroup_sk_alloc is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886860/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108

2020-07-08 Thread Thadeu Lima de Souza Cascardo
This is caused by net_cls and net_prio cgroups disabling cgroup BPF and
causing it to stop refcounting when allocating new sockets. Releasing those
sockets will cause the refcount to go negative, leading to the potential
use-after-free.

Though this revert won't prevent the issue from happening as it could still
theoretically be caused by setting net_cls.classid or net_prio.ifpriomap,
this will prevent it from happening on default system configurations. A 
combination of systemd use of cgroup BPF and extensive cgroup use including
net_prio will cause this. Reports usually involve using lxd, libvirt,
docker or kubernetes and some systemd service with IPAddressDeny or 
IPAddressAllow.

And though this patch has been introduced to avoid some potential memory 
leaks, the cure is worse than the disease. We will need to revisit both 
issues later on and reapply this patch when we have a real fix for the
crash.

Cascardo.

** Patch added: 
"0001-UBUNTU-SAUCE-Revert-netprio_cgroup-Fix-unlimited-mem.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886668/+attachment/5390827/+files/0001-UBUNTU-SAUCE-Revert-netprio_cgroup-Fix-unlimited-mem.patch

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886668

Title:
  linux 4.15.0-109-generic network DoS regression vs -108

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886668/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876982] Re: tunnels over IPv6 are unencrypted when using IPsec

2020-07-03 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876982

Title:
  tunnels over IPv6 are unencrypted when using IPsec

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876982/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876697] Re: test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM / B-GCP-5.4

2020-07-03 Thread Thadeu Lima de Souza Cascardo
So, B-GCP-5.4 as well as F-GCP 5.4.0-1011 have RT_GROUP_SCHED on, and
that has been turned off by later versions, like F-GCP 5.4.0-1012 and
B-GCP-5.4 5.4.0-1016.

@cypressyew, can you confirm that it doesn't happen on such kernels?

Thanks.
Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876697

Title:
  test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM
  / B-GCP-5.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1876697/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted

2020-07-02 Thread Thadeu Lima de Souza Cascardo
@xnox, the unlock must happen for the root filesystem during dump,
independently from where it's going to dump to, though default
configuration is into local /var/crash/.

And even if the memory parameter is picked up depending on the system
size and crashkernel does that too, crashkernel takes memory out of the
system that cannot be used during production.

My opinion is that even we could tell how much memory would be necessary
for dumping, this is a matter of policy. A user with 2GiB can easily
unlock an Argon2i encrypted root filesystem with memory parameter close
to 1GB during boot. But would such user would be surprised to have now
only half of that memory available after boot because the other half was
reserved? Maybe the user only needed 1GiB for production and added the
extra 1GiB for crashkernel. Maybe the user didn't expect that.

Fortunately, the option is configurable. Unfortunately, we don't have an
easy way to advise the user how much memory will be necessary and it can
even change when system configuration changes. And I wouldn't still just
change the parameter without telling the user.

So, my suggestion here is that we try to improve the defaults, consider
changing s390x to match other arches that change that depending on
system memory size. In the future, we could have some tool that advise a
different setting. But right now, users are supposed to test that the
current setting works for them, change it to a working setting, maybe
consider changing their VM size because of that.

So, I am closing this issue as "Won't Fix".
Cascardo.

** Changed in: makedumpfile (Ubuntu Groovy)
   Status: Incomplete => Won't Fix

** Changed in: makedumpfile (Ubuntu Focal)
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877533

Title:
  [20.10 FEAT] Increase the crashkernel setting if the root volume is
  luks2-encrypted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875826] Re: Kdumping on an Ubuntu 20.04 guest with an encrypted root partition drops user to initramfs console

2020-07-02 Thread Thadeu Lima de Souza Cascardo
So, everything done was correct, aside from generating the initrd image.
The one at /boot/ is used for booting. For crashing, it's used the one
from /var/lib/kdump/. You should remove it and reload kdump:

rm /var/lib/kdump/initrd.img-`uname -r`
kdump-config reload

** Changed in: makedumpfile (Ubuntu Groovy)
   Status: New => Invalid

** Changed in: makedumpfile (Ubuntu Focal)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875826

Title:
  Kdumping on an Ubuntu 20.04 guest with an encrypted root partition
  drops user to initramfs console

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1875826/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886065] [NEW] Move do_enforce_all from hooks.mk to arches mk

2020-07-02 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

[Impact]
When rebasing hwe kernels, we need to deal with changes from hooks.mk coming 
from master kernels.

[Fix]
Remove any contents from hooks.mk from master kernels, that is, move 
do_enforce_all around to arches mk files.

[Test case]
Kernel build works, annotation file regressions fail the build, hwe rebase 
works fine without hooks.mk munging.

[Regression potential]
We might fail the kernel build or fail to catch up an annotation file 
regression. Those were covered in the test case.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: linux (Ubuntu Groovy)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886065

Title:
  Move do_enforce_all from hooks.mk to arches mk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886065/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1817721] Re: autopkgtest success rate in Bionic reached an unusable amount

2020-06-30 Thread Thadeu Lima de Souza Cascardo
So after some investigation on systemd failures on ppc64el triggered by
the kernel on eoan, I noticed some coredumps on processes when running
under qemu inside the ADT environment.

As one of these processes is sleep, I am pretty confident this is caused
by the lack of emulation or rather the failure to ignore mffsl extra
bits, aka LP: #1847806.

I am not sure this is the right bug as it mentions lots of other
upstream failures across all arches. But it looks like the ones we are
seeing, and as we are referring this bug in our results, I thought it
was worht mentioning.

Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817721

Title:
  autopkgtest success rate in Bionic reached an unusable amount

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817721/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885757] Re: seccomp_bpf fails on powerpc

2020-06-30 Thread Thadeu Lima de Souza Cascardo
** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885757

Title:
  seccomp_bpf fails on powerpc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1885757/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885757] [NEW] seccomp_bpf fails on powerpc

2020-06-30 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

[Impact]
seccomp_bpf test fails on powerpc and ends up being disabled on some series, or 
causing engineers to waste their time verifying the same failures are the only 
ones we see every kernel release.

[Test case]
Run the test and notice there are no more failures.

[Regression potential]
We may break the test on different architectures. That doesn't break users, 
though, as the changes are only on tests. It has been tested at least on 
ppc64el and amd64.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: linux (Ubuntu Eoan)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: linux (Ubuntu Groovy)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Eoan)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885757

Title:
  seccomp_bpf fails on powerpc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885757/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885757] Re: seccomp_bpf fails on powerpc

2020-06-30 Thread Thadeu Lima de Souza Cascardo
https://lore.kernel.org/linux-
kselftest/20200630164739.1268222-1-casca...@canonical.com/T/#u

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885757

Title:
  seccomp_bpf fails on powerpc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885757/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849844] Re: seccomp test in ubuntu_kernel_selftests failed to build on D amd64

2020-06-30 Thread Thadeu Lima de Souza Cascardo
*** This bug is a duplicate of bug 1872047 ***
https://bugs.launchpad.net/bugs/1872047

** This bug is no longer a duplicate of bug 1864073
   seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests
** This bug has been marked a duplicate of bug 1872047
   kselftest: seccomp kill_after_ptrace() timeout

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849844

Title:
  seccomp test in ubuntu_kernel_selftests failed to build on D amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1864073] Re: seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests

2020-06-30 Thread Thadeu Lima de Souza Cascardo
*** This bug is a duplicate of bug 1872047 ***
https://bugs.launchpad.net/bugs/1872047

** This bug has been marked a duplicate of bug 1872047
   kselftest: seccomp kill_after_ptrace() timeout

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864073

Title:
  seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864073/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853193] Re: copy_file_range test fails with linux 5.3+ on bionic

2020-06-29 Thread Thadeu Lima de Souza Cascardo
** Patch added: "fix for bionic"
   
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/+attachment/5388335/+files/glibc_2.27-3ubuntu1.1.debdiff

** Description changed:

+ [Impact]
+ When tested against newer versions of linux, glibc tests will fail as it 
makes some assumptions about supportead features on the kernel.
+ 
+ [Fix]
+ Do not run the test that checks that copy_file_range will fail with EXDEV 
when done across devices.
+ 
+ [Test case]
+ Build glibc and run its tests on linux 5.3.
+ 
+ [Regression potential]
+ The same test is being ignored right now, we risk ignoring a failure on an 
older version of linux, like 4.15. However, that could happen because the 
feature is backported to said kernel. And we are currently ignoring the failure 
anyway.
+ 
+ ===
+ 
  copy_file_range on linux 5.3 now works across devices, so EXDEV is not
  returned anymore on those cases. glibc, however, tests that is the case
  and its autopkgtest fails, then, when running on linux 5.3.
  
  glibc 2.30 does not fail in that case anymore, so eoan glibc works fine
  on linux 5.3. However, the change on glibc 2.30 was to remove its
  userspace emulation entirely, and require users to fallback on their
  own.
  
  https://sourceware.org/bugzilla/show_bug.cgi?id=24744
  
  Linux commit 5dae222a5ff0c269730393018a5539cc970a4726.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853193

Title:
  copy_file_range test fails with linux 5.3+ on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770480] Re: preadv2 test does not consider new flag from linux 4.16

2020-06-29 Thread Thadeu Lima de Souza Cascardo
** Description changed:

- 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
- /autopkgtest-cosmic-canonical-kernel-team-
- bootstrap/cosmic/arm64/g/glibc/20180510_173125_32961@/log.gz
+ [Impact]
+ When tested against newer versions of linux, glibc tests will fail as it 
makes some assumptions about supportead features on the kernel.
+ 
+ [Fix]
+ Ignore "invalid" (rather unknown) flags success as failure, instead exiting 
as unsupported (equivalent to skip).
+ 
+ [Test case]
+ Build glibc and run its tests on linux 5.3.
+ 
+ [Regression potential]
+ The same test is being ignored right now, we risk ignoring a failure on an 
older version of linux, like 4.15. However, that could happen because the 
feature is backported to said kernel. And we are currently ignoring the failure 
anyway.
+ 
+ ==
+ 
+ 
+ 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/arm64/g/glibc/20180510_173125_32961@/log.gz
  
  FAIL: misc/tst-preadvwritev2
  original exit status 1
  error: tst-preadvwritev2-common.c:45: preadv2 did not fail with an invalid 
flag
  error: 1 test failures
  --
  --
  FAIL: misc/tst-preadvwritev64v2
  original exit status 1
  error: tst-preadvwritev2-common.c:45: preadv2 did not fail with an invalid 
flag
  error: 1 test failures
  
  This is testing for the flag immediately after the last known flag. So,
  if it's 0x8, it's going to test for 0x10.
  
  The test snippet:
  
-   int invalid_flag = RWF_SUPPORTED != 0 ? __builtin_clz (RWF_SUPPORTED) : 2;
-   invalid_flag = 0x1 << ((sizeof (int) * CHAR_BIT) - invalid_flag);
+   int invalid_flag = RWF_SUPPORTED != 0 ? __builtin_clz (RWF_SUPPORTED) : 2;
+   invalid_flag = 0x1 << ((sizeof (int) * CHAR_BIT) - invalid_flag);
  
-   char buf[32];
-   const struct iovec vec = { .iov_base = buf, .iov_len = sizeof (buf) };
-   if (preadv2 (temp_fd, , 1, 0, invalid_flag) != -1)
- FAIL_EXIT1 ("preadv2 did not fail with an invalid flag");
- 
+   char buf[32];
+   const struct iovec vec = { .iov_base = buf, .iov_len = sizeof (buf) };
+   if (preadv2 (temp_fd, , 1, 0, invalid_flag) != -1)
+ FAIL_EXIT1 ("preadv2 did not fail with an invalid flag");
  
  However, linux 4.16 has introduced RWF_APPEND.
  
  commit e1fc742e14e01d84d9693c4aca4ab23da65811fb
  Author: Jürg Billeter 
  Date:   Fri Sep 29 14:07:17 2017 +0200
  
- fs: add RWF_APPEND
+ fs: add RWF_APPEND
  
  ---
  +/* per-IO O_APPEND */
  +#define RWF_APPEND ((__force __kernel_rwf_t)0x0010)
  +
-  /* mask of flags supported by the kernel */
+  /* mask of flags supported by the kernel */
  -#define RWF_SUPPORTED  (RWF_HIPRI | RWF_DSYNC | RWF_SYNC | RWF_NOWAIT)
  +#define RWF_SUPPORTED  (RWF_HIPRI | RWF_DSYNC | RWF_SYNC | RWF_NOWAIT |\
  +RWF_APPEND)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770480

Title:
  preadv2 test does not consider new flag from linux 4.16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1770480/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel

2020-06-18 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826848

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3
  / 5.4 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853193] Re: copy_file_range test fails with linux 5.3+ on bionic

2020-06-18 Thread Thadeu Lima de Souza Cascardo
I am sending a proposed patch. I am building a package that includes
that patch on my ppa:cascardo/ppa. I will trigger tests against that and
verify this really fixes the issue.

** Patch added: "disable cross_device_failure test for copy_file_range"
   
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/+attachment/5385113/+files/test-disable-copy_file_range-cross_device_failure.patch

** Changed in: glibc (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: glibc (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853193

Title:
  copy_file_range test fails with linux 5.3+ on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770480] Re: preadv2 test does not consider new flag from linux 4.16

2020-06-18 Thread Thadeu Lima de Souza Cascardo
I am sending a proposed patch. I am building a package that includes
that patch on my ppa:cascardo/ppa. I will trigger tests against that and
verify this really fixes the issue.

** Patch added: "make preadwritev2 invalid flags tests unsupported"
   
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1770480/+attachment/5385112/+files/test-make-preadwritev2-invalid-flag-unsupported.patch

** Changed in: glibc (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: glibc (Ubuntu Bionic)
 Assignee: Adam Conrad (adconrad) => Thadeu Lima de Souza Cascardo 
(cascardo)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770480

Title:
  preadv2 test does not consider new flag from linux 4.16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1770480/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881339] Re: readdir performance when copying to userspace

2020-06-16 Thread Thadeu Lima de Souza Cascardo
When using a large directory with large names, I noticed a 50% increase
in the time it took to readdir the entire directory. With small names,
the increase did not seem noticeable enough. Tested on a VM with bionic,
no SMAP involved. Compared before memchr and after memchr. Need to
compare before and after uaccess changes, both without SMAP and with
SMAP.

Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881339

Title:
  readdir performance when copying to userspace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881339/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel

2020-06-08 Thread Thadeu Lima de Souza Cascardo
https://git.kernel.org/torvalds/c/065fcfd49763ec71ae345bb5c5a74f961031e70e

Applied to Torvalds' tree.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826848

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3
  / 5.4 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel

2020-06-08 Thread Thadeu Lima de Souza Cascardo
The test failure is intermittent, I have sent a suggested fix upstream,
will send it as SAUCE to the mailing list soon.

https://lore.kernel.org/linux-
kselftest/20200602183837.1540345-1-casca...@canonical.com/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826848

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3
  / 5.4 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1747847] Re: Tests in ubuntu_qrt_kernel_security (021, 022) complains about ASLR not functional on Trusty ARM64

2020-06-05 Thread Thadeu Lima de Souza Cascardo
I noticed that failure too, tested it manually on trusty amd64 with both
64-bit and 32-bit binary, and with 3.2 kernel, and it worked fine. I'll
try the whole suite on a precise VM and see if I can reproduce it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747847

Title:
  Tests in ubuntu_qrt_kernel_security (021, 022) complains about ASLR
  not functional on Trusty ARM64

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1747847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882012] Re: Dependency issue for 3.2 linux-lowlatency meta package

2020-06-04 Thread Thadeu Lima de Souza Cascardo
This is a very old version, present in precise-updates, not the ESM
repo. I don't see us producing lowlatency kernels or meta packages on
ESM. Was that a different source package that produced those lowlatency
packages?

It looks to me this is not a regression, or even a problem at all. It
should not be a blocker.

Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882012

Title:
  Dependency issue for 3.2 linux-lowlatency meta package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882012/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882012] Re: Dependency issue for 3.2 linux-lowlatency meta package

2020-06-04 Thread Thadeu Lima de Souza Cascardo
Confirmed this is a different source package on precise.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882012

Title:
  Dependency issue for 3.2 linux-lowlatency meta package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882012/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade

2020-06-03 Thread Thadeu Lima de Souza Cascardo
That speed comes from
drivers/net/ethernet/cisco/enic/enic_ethtool.c:enic_get_ksettings.

static int enic_get_ksettings(struct net_device *netdev,
  struct ethtool_link_ksettings *ecmd)
{
struct enic *enic = netdev_priv(netdev);
struct ethtool_link_settings *base = >base;

ethtool_link_ksettings_add_link_mode(ecmd, supported,
 1baseT_Full);
ethtool_link_ksettings_add_link_mode(ecmd, supported, FIBRE);
ethtool_link_ksettings_add_link_mode(ecmd, advertising,
 1baseT_Full);
ethtool_link_ksettings_add_link_mode(ecmd, advertising, FIBRE);
base->port = PORT_FIBRE;

if (netif_carrier_ok(netdev)) {
base->speed = vnic_dev_port_speed(enic->vdev);
base->duplex = DUPLEX_FULL;
} else {
base->speed = SPEED_UNKNOWN;
base->duplex = DUPLEX_UNKNOWN;
}

base->autoneg = AUTONEG_DISABLE;

return 0;
}

vnic_dev_port_speed comes from the hardware at function
drivers/net/ethernet/cisco/enic/vnic_dev.c:vnic_dev_notify_setcmd.

static int vnic_dev_notify_setcmd(struct vnic_dev *vdev,
void *notify_addr, dma_addr_t notify_pa, u16 intr)
{
u64 a0, a1;
int wait = 1000;
int r;

memset(notify_addr, 0, sizeof(struct vnic_devcmd_notify));
vdev->notify = notify_addr;
vdev->notify_pa = notify_pa;

a0 = (u64)notify_pa;
a1 = ((u64)intr << 32) & 0xULL;
a1 += sizeof(struct vnic_devcmd_notify);

r = vnic_dev_cmd(vdev, CMD_NOTIFY, , , wait);
vdev->notify_sz = (r == 0) ? (u32)a1 : 0;
return r;
}

struct vnic_devcmd_notify {
u32 csum;   /* checksum over following words */

u32 link_state; /* link up == 1 */
u32 port_speed; /* effective port speed (rate limit) */
u32 mtu;/* MTU */
u32 msglvl; /* requested driver msg lvl */
u32 uif;/* uplink interface */
u32 status; /* status bits (see VNIC_STF_*) */
u32 error;  /* error code (see ERR_*) for first ERR */
u32 link_down_cnt;  /* running count of link down transitions */
u32 perbi_rebuild_cnt;  /* running count of perbi rebuilds */
};

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881821

Title:
  Kernel does not report interface speed correctly for Cisco UCS B200 M5
  blade

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 kernel

2020-06-02 Thread Thadeu Lima de Souza Cascardo
** Description changed:

- Test failed becuase:
-./ip_defrag: sendto overlap: 1400: Operation not permitted
+ [Impact]
+ Failure to run ip_defrag deterministically.
+ 
+ [Fix]
+ Use smaller packets and ignore EPERM.
+ 
+ [Test case]
+ Run the test multiple times without observing failures.
+ 
+ [Regression potential]
+ If the test fix is incorrect, it will cause us to miss real kernel bugs. But 
as it is now, we are already ignoring its results.
  
  
-  selftests: net: ip_defrag.sh
-  
-  ipv6 tx:17 gso:1 (fail)
-  OK
-  ipv4 defrag
-  PASS
-  seed = 1556203721
-  ipv4 defrag with overlaps
-  PASS
-  seed = 1556203722
-  ipv6 defrag
-  seed = 1556203756
-  PASS
-  ipv6 defrag with overlaps
-  seed = 1556203756
-  ./ip_defrag: sendto overlap: 1400: Operation not permitted
-  not ok 1..17 selftests: net: ip_defrag.sh [FAIL]
+ ==
+ 
+ Test failed becuase:
+    ./ip_defrag: sendto overlap: 1400: Operation not permitted
+ 
+  selftests: net: ip_defrag.sh
+  
+  ipv6 tx:17 gso:1 (fail)
+  OK
+  ipv4 defrag
+  PASS
+  seed = 1556203721
+  ipv4 defrag with overlaps
+  PASS
+  seed = 1556203722
+  ipv6 defrag
+  seed = 1556203756
+  PASS
+  ipv6 defrag with overlaps
+  seed = 1556203756
+  ./ip_defrag: sendto overlap: 1400: Operation not permitted
+  not ok 1..17 selftests: net: ip_defrag.sh [FAIL]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826848

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3
  kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881643] Re: pmtu.sh net selftest fail with PMTU dst likely leaked

2020-06-01 Thread Thadeu Lima de Souza Cascardo
** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Focal)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881643

Title:
  pmtu.sh net selftest fail with PMTU dst likely leaked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881643/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881643] [NEW] pmtu.sh net selftest fail with PMTU dst likely leaked

2020-06-01 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/ppc64el/l/linux/20200528_044656_7f57a@/log.gz

[...]
03:48:34 DEBUG| [stdout] # TEST: ipv6: cleanup of cached exceptions - nexthop 
objects  [FAIL]
03:48:34 DEBUG| [stdout] #   can't delete veth device in a timely manner, PMTU 
dst likely leaked
[...]
03:49:17 DEBUG| [stdout] not ok 16 selftests: net: pmtu.sh # exit=1

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881643

Title:
  pmtu.sh net selftest fail with PMTU dst likely leaked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881643/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 kernel

2020-06-01 Thread Thadeu Lima de Souza Cascardo
** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Focal)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826848

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3
  kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881576] Re: seccomp_benchmark times out on eoan

2020-06-01 Thread Thadeu Lima de Souza Cascardo
** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
   Status: Fix Released => In Progress

** Changed in: ubuntu-kernel-tests
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881576

Title:
  seccomp_benchmark times out on eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881576/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881576] Re: seccomp_benchmark times out on eoan

2020-06-01 Thread Thadeu Lima de Souza Cascardo
** Description changed:

- As it tries to calibrate how many samples will take more than 5 seconds
- to execute, it may end up picking up a number of samples that take 10
- (but up to 12) seconds. As the calibration will take double that time,
- it takes around 20 seconds. Then, it executes the whole thing again, and
- then once more, with some added overhead. So, the thing might take more
- than 40 seconds, which is too close to the 45s timeout.
+ [Impact]
+ seccomp selftests will timeout, causing the test to be detected as failure.
+ 
+ [Fix]
+ Set timeout to 90s.
+ 
+ [Test case]
+ Run sudo make run_tests under tools/testing/selftests/seccomp/.
+ 
+ [Regression potential]
+ Minimal, the test could still timeout, but by reading the code, it should 
take around 42s to 50s to execute in the worst cases, so 90s seem safe enough.
+ 
+ ==
+ 
+ 
+ As it tries to calibrate how many samples will take more than 5 seconds to 
execute, it may end up picking up a number of samples that take 10 (but up to 
12) seconds. As the calibration will take double that time, it takes around 20 
seconds. Then, it executes the whole thing again, and then once more, with some 
added overhead. So, the thing might take more than 40 seconds, which is too 
close to the 45s timeout.
  
  So, it times out once in a while depending on the system. Using a
  timeout of 90 seconds should be safe enough for this test.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881576

Title:
  seccomp_benchmark times out on eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881576/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881576] [NEW] seccomp_benchmark times out on eoan

2020-06-01 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

As it tries to calibrate how many samples will take more than 5 seconds
to execute, it may end up picking up a number of samples that take 10
(but up to 12) seconds. As the calibration will take double that time,
it takes around 20 seconds. Then, it executes the whole thing again, and
then once more, with some added overhead. So, the thing might take more
than 40 seconds, which is too close to the 45s timeout.

So, it times out once in a while depending on the system. Using a
timeout of 90 seconds should be safe enough for this test.

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux (Ubuntu Eoan)
 Importance: Undecided
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

** Changed in: linux (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881576

Title:
  seccomp_benchmark times out on eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881576/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1866972] Re: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests

2020-05-29 Thread Thadeu Lima de Souza Cascardo
For what matters, the alternative would probably to pick
fe60b0ce8e7335269722ec080173a9411a9d58a5. More exactly, all the
following commits:

41af3cf587f476f9a879b08219324c8b456e6a4c tracing/uprobe: Add multi-probe per 
uprobe event support
60d53e2c3b75e79c83970fe73db79123d9462c7c tracing/probe: Split trace_event 
related data from trace_probe
ca89bc071d5e4e981dcc52e0ca90f4500d332e42 tracing/kprobe: Add multi-probe per 
event support
fe60b0ce8e7335269722ec080173a9411a9d58a5 tracing/probe: Reject exactly same 
probe event
f8d7ab2bded897607bff6324d5c6ea6b4aecca0c tracing/probe: Fix same probe event 
argument matching

Not tested.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866972

Title:
  ftrace test failed with Register/unregister many kprobe events in
  ubuntu_kernel_selftests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1866972] Re: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests

2020-05-29 Thread Thadeu Lima de Souza Cascardo
] (instance) event tracing - restricts events based on pid[PASS]
+  [71] (instance) event tracing - enable/disable with subsystem level files
[PASS]
+  [72] (instance) ftrace - stacktrace filter command   [PASS]
+  [73] (instance) ftrace - test for function event triggers[PASS]
+  [74] (instance) ftrace - test for function traceon/off triggers  [PASS]
+  [75] (instance) event trigger - test event enable/disable trigger[PASS]
+  [76] (instance) event trigger - test trigger filter  [PASS]
+  [77] (instance) event trigger - test histogram modifiers [PASS]
+  [78] (instance) event trigger - test multiple histogram triggers [PASS]
+  [79] (instance) trace_marker trigger - test snapshot trigger [PASS]
  
- 
-  # of passed: 75
-  # of failed: 1
-  # of unresolved: 2
-  # of untested: 0
-  # of unsupported: 1
-  # of xfailed: 0
-  # of undefined(test bug): 0
-  not ok 1..1 selftests: ftrace: ftracetest [FAIL]
+  # of passed: 75
+  # of failed: 1
+  # of unresolved: 2
+  # of untested: 0
+  # of unsupported: 1
+  # of xfailed: 0
+  # of undefined(test bug): 0
+  not ok 1..1 selftests: ftrace: ftracetest [FAIL]

** Changed in: linux (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866972

Title:
  ftrace test failed with Register/unregister many kprobe events in
  ubuntu_kernel_selftests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881339] [NEW] readdir performance when copying to userspace

2020-05-29 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

The following fixes were backported to bionic and xenial to prevent a
potential security issue:

- Make filldir[64]() verify the directory entry filename is valid
- filldir[64]: remove WARN_ON_ONCE() for bad directory entries

In that process, they introduced a potential performace impact on
readdir. How much is yet to be measured.

9f79b78ef74436c7507bac6bfb7b8b989263bccb Convert filldir[64]() from 
__put_user() to unsafe_put_user()
c512c69187197fe08026cb5bbe7b9709f4f89b73 uaccess: implement a proper 
unsafe_copy_to_user() and switch filldir over to it

The two commits above try to mitigate that performance impact. At least
on x86 with SMAP, that should have some effect. At any other platforms,
at least on bionic and xenial, any improvements should be measured.
Though that is true for x86 with SMAP too.

This bug is opened in order to keep track of that possible performance
improvement we might add in the future as followup for those two
commits.

Cascardo.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux (Ubuntu Xenial)
 Importance: Low
 Status: Triaged

** Affects: linux (Ubuntu Bionic)
 Importance: Low
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: kernel-sru-workflow

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Triaged

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881339

Title:
  readdir performance when copying to userspace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881339/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1862822] Re: init_on_alloc=1 causes big performance regression for ZFS

2020-05-26 Thread Thadeu Lima de Souza Cascardo
init_on_alloc=1 as a default servers Ubuntu users as a security
hardening mechanism, preventing a class of security issues from being
exploitable. Disabling that in general would allow those unknown
vulnerabilities open to be exploited.

It can be turned off during boot by using init_on_alloc=0 kernel
parameter. So any user who is affected by this performance issue can
mitigate that by disabling the hardening option, after considering its
possible consequences.

As we would rather not expose those users who depend or desire that ZFS
performance, I would like to ask if it would be possible to mitigate
that on ZFS by reusing pages or maybe pre-allocating them.

Regards.
Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862822

Title:
  init_on_alloc=1 causes big performance regression for ZFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862822/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349028] Re: getitimer returns it_value=0 erroneously

2020-05-18 Thread Thadeu Lima de Souza Cascardo
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349028

Title:
  getitimer returns it_value=0 erroneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349028/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349028] Re: getitimer returns it_value=0 erroneously

2020-05-18 Thread Thadeu Lima de Souza Cascardo
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349028

Title:
  getitimer returns it_value=0 erroneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349028/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349028] Re: getitimer returns it_value=0 erroneously

2020-05-18 Thread Thadeu Lima de Souza Cascardo
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349028

Title:
  getitimer returns it_value=0 erroneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349028/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879327] Re: Enforce all config annotations

2020-05-18 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
   Status: Confirmed

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Groovy)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Eoan)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Xenial)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879327

Title:
  Enforce all config annotations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879327/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879327] [NEW] Enforce all config annotations

2020-05-18 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

[Impact]
Not all config annotations are enforced, which means config could regress 
without notice.

[Test case]
Check the logs mention much more options being enforced. From the hundreds to 
more than 1.

[Regression potential]
Builds will start failing when config doesn't match annotations. However, this 
is an opt-in for now, which means only those branches prepared to accept it 
will risk such regression.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879327

Title:
  Enforce all config annotations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879327/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted

2020-05-14 Thread Thadeu Lima de Souza Cascardo
Setting as Invalid for linux, as this is not a linux bug. Marking as
Confirmed for makedumpfile, where there is a chance this might be fixed.

However, I disagree with checking for a specific module on a specific
architecture to decide crashkernel size.

crashkernel size is a suggestion. Users are supposed to test that kdump
works with the size they are supposed to configure. We may need to
document that.

** Also affects: makedumpfile (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Groovy)
   Status: New => Invalid

** Changed in: linux (Ubuntu Focal)
   Status: New => Invalid

** Changed in: makedumpfile (Ubuntu Groovy)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu Focal)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877533

Title:
  [20.10 FEAT] Increase the crashkernel setting if the root volume is
  luks2-encrypted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1864073] Re: seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests

2020-05-07 Thread Thadeu Lima de Souza Cascardo
7fb44bf64414954cdc96517612f9785f4a832cc2 ("UBUNTU: SAUCE:
kselftest/runner: allow to properly deliver signals to tests")

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864073

Title:
  seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864073/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1864073] Re: seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests

2020-05-07 Thread Thadeu Lima de Souza Cascardo
7fb44bf64414954cdc96517612f9785f4a832cc2 ("UBUNTU: SAUCE:
kselftest/runner: allow to properly deliver signals to tests") has been
included in Ubuntu-5.3.0-52.46.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864073

Title:
  seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864073/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1864073] Re: seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests

2020-05-07 Thread Thadeu Lima de Souza Cascardo
Andrea and I tracked this down to some interaction of signal handling
between timeout command and the test itself. It may have been fixed in
-proposed already.

Cascardo.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864073

Title:
  seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864073/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876982] Re: tunnels over IPv6 are unencrypted when using IPsec

2020-05-05 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876982

Title:
  tunnels over IPv6 are unencrypted when using IPsec

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876982/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876982] Re: tunnels over IPv6 are unencrypted when using IPsec

2020-05-05 Thread Thadeu Lima de Souza Cascardo
** Description changed:

  [Impact]
  When tunnels are configured over IPv6 using a xfrm policy, it's ignored. That 
means data will be unencrypted when it shouldn't.
  
  [Test case]
  
+ Launch a VM with the given kernel and monitor its network link on the host 
with:
+ tcpdump -n -i virbr0 ip6 and port 4789
+ 
+ In the guest, set up a tunnel using an IPv6 address:
+ ip link add type vxlan id 5 remote fd00:cafe::2 dstport 4789
+ 
+ When setting the link up, observe packets being output on the host side:
+ ip link set vxlan0 up
+ 
+ Set the link down, and add a xfrm policy to block output to that given IPv6 
address:
+ ip link set vxlan0 down
+ ip xfrm policy add dst fd00:cafe::2 dir out action block
+ 
+ Check that using ping won't work with Operation not permitted:
+ ping6 fd00:cafe::2
+ connect: Operation not permitted
+ 
+ Set the vxlan link up and watch that no packets appear on tcpdump:
+ ip link set vxlan0 up
+ 
  [Regression potential]
  Tunnels like VXLAN, GENEVE, etc, will stop to send. The test has shown that 
it still sends at least when no xfrm policy is configured.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876982

Title:
  tunnels over IPv6 are unencrypted when using IPsec

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876982/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876982] [NEW] tunnels over IPv6 are unencrypted when using IPsec

2020-05-05 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

[Impact]
When tunnels are configured over IPv6 using a xfrm policy, it's ignored. That 
means data will be unencrypted when it shouldn't.

[Test case]

[Regression potential]
Tunnels like VXLAN, GENEVE, etc, will stop to send. The test has shown that it 
still sends at least when no xfrm policy is configured.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876982

Title:
  tunnels over IPv6 are unencrypted when using IPsec

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876982/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876697] Re: test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM

2020-05-04 Thread Thadeu Lima de Souza Cascardo
My guess is that the test might be hitting the following code from
kernel/sched/core.c:

#ifdef CONFIG_RT_GROUP_SCHED
/*
 * Do not allow realtime tasks into groups that have no runtime
 * assigned.
 */
if (rt_bandwidth_enabled() && rt_policy(policy) &&
task_group(p)->rt_bandwidth.rt_runtime == 0 &&
!task_group_is_autogroup(task_group(p))) {
retval = -EPERM;
goto unlock;
}
#endif

Which is not really about the capabilities. That is just a guess.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876697

Title:
  test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1876697/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349028] Re: getitimer returns it_value=0 erroneously

2020-04-23 Thread Thadeu Lima de Souza Cascardo
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Medium
 Assignee: Colin Ian King (colin-king)
   Status: Fix Released

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349028

Title:
  getitimer returns it_value=0 erroneously

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349028/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874005] Re: QEMU pegs CPU at 100% when running a Focal guest image

2020-04-22 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874005

Title:
  QEMU pegs CPU at 100% when running a Focal guest image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874005/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1862588] Re: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels

2020-04-15 Thread Thadeu Lima de Souza Cascardo
I sent a revert for the patch that PHLin identified.

** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Disco)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Disco)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Bionic)
   Status: Incomplete => Invalid

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862588

Title:
  user_notification_basic in seccomp of ubuntu_kernel_selftest failed on
  Bionic-5.0 Kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862588/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1862588] Re: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels

2020-04-10 Thread Thadeu Lima de Souza Cascardo
** Description changed:

  [Impact]
  Running seccomp kernel selftests will fail.
  
  [Test case]
  Run linux/tools/testing/selftests/seccomp/seccomp_bpf.
  
  On failure:
+ 
  seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 
(18446744073709551615) == ret (0)
  seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == 
errno (0)
  global.user_notification_basic: Test failed at step #3
  [ FAIL ] global.user_notification_basic
  
  On success:
  
+ [ RUN  ] global.user_notification_basic
+ [   OK ] global.user_notification_basic
+ 
+ 
  [Regression potential]
  The test is checking that the given structure which the kernel will write to 
is all zeroes. It's doing it because it wants userspace to have the possibility 
in the future to give data there indicating support for an extension that might 
be developed in the future. As the test is there right now, not applying the 
breaking uABI fix might cause us to miss applications that would break in 
future kernels. As the backport for that is prone for more regression 
potential, we are deciding to revert the new test.
- 
  
  ==
  
  Issue found on Oracle Bionic 5.0 (oracle : 5.0.0-1011.16 : amd64)
  
  [ RUN  ] global.user_notification_basic
  seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 
(18446744073709551615) == ret (0)
  seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == 
errno (0)
  global.user_notification_basic: Test failed at step #3
  [ FAIL ] global.user_notification_basic
  
  This cannot be reproduced with the kselftest in older kernel, probably a
  test case issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-1011-oracle 5.0.0-1011.16
  ProcVersionSignature: User Name 5.0.0-1011.16-oracle 5.0.21
  Uname: Linux 5.0.0-1011-oracle x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  Date: Mon Feb 10 05:17:54 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oracle-5.0
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862588

Title:
  user_notification_basic in seccomp of ubuntu_kernel_selftest failed on
  Bionic-5.0 Kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862588/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

  1   2   3   4   5   6   7   8   9   10   >