s390 updates for 5.13 merge window

- fix buffer size for in-kernel disassembler for ebpf programs.

- fix two memory leaks in zcrypt driver.

- expose PCI device UID as index, including an indicator if the uid is
  unique.

- remove some oprofile leftovers.

- improve stack unwinder tests.

- don't use gcc atomic builtins anymore, just like all other
  architectures. Even though I'm sure the current code is ok, I
  totally dislike that s390 is the only architecture being special
  here; especially considering that there was a lengthly discussion
  about this topic and the outcome was not to use the builtins.
  Therefore open-code atomic ops again with inline assembly and switch
  to gcc builtins as soon as other architectures are doing.

- couple of other changes to atomic and cmpxchg, and use
  atomic-instrumented.h for KASAN.

- separate zbus creation, registration, and scanning in our PCI code
  which allows for cleaner and easier handling.

- a rather large change to the vfio-ap code to fix circular locking
  dependencies when updating crypto masks.

- move QAOB handling from qdio layer down to drivers.

- add CRW inject facility to common I/O layer. This adds debugs files
  which allow to generate artificial events from user space for
  testing purposes.

- increase SCLP console line length from 80 to 320 characters to avoid
  odd wrapped lines.

- add protected virtualization guest and host indication files, which
  indicate either that a guest is running in pv mode or if the
  hypervisor is capable of starting pv guests.

- various other small fixes and improvements all over the place.
s390/disassembler: increase ebpf disasm buffer size

Current ebpf disassembly buffer size of 64 is too small. E.g. this line
takes 65 bytes:
01fffff8005822e: ec8100ed8065\tclgrj\t%r8,%r1,8,001fffff80058408\n\0

Double the buffer size like it is done for the kernel disassembly buffer.

Fixes the following KASAN finding:

UG: KASAN: stack-out-of-bounds in print_fn_code+0x34c/0x380
Write of size 1 at addr 001fff800ad5f970 by task test_progs/853

CPU: 53 PID: 853 Comm: test_progs Not tainted
5.12.0-rc7-23786-g23457d86b1f0-dirty #19
Hardware name: IBM 3906 M04 704 (LPAR)
Call Trace:
 [<0000000cd8e0538a>] show_stack+0x17a/0x1668
 [<0000000cd8e2a5d8>] dump_stack+0x140/0x1b8
 [<0000000cd8e16e74>] print_address_description.constprop.0+0x54/0x260
 [<0000000cd75a8698>] kasan_report+0xc8/0x130
 [<0000000cd6e26da4>] print_fn_code+0x34c/0x380
 [<0000000cd6ea0f4e>] bpf_int_jit_compile+0xe3e/0xe58
 [<0000000cd72c4c88>] bpf_prog_select_runtime+0x5b8/0x9c0
 [<0000000cd72d1bf8>] bpf_prog_load+0xa78/0x19c0
 [<0000000cd72d7ad6>] __do_sys_bpf.part.0+0x18e/0x768
 [<0000000cd6e0f392>] do_syscall+0x12a/0x220
 [<0000000cd8e333f8>] __do_syscall+0x98/0xc8
 [<0000000cd8e54834>] system_call+0x6c/0x94
1 lock held by test_progs/853:
 #0: 0000000cd9bf7460 (report_lock){....}-{2:2}, at:
     kasan_report+0x96/0x130

addr 001fff800ad5f970 is located in stack of task test_progs/853 at
offset 96 in frame:
 print_fn_code+0x0/0x380
this frame has 1 object:
 [32, 96) 'buffer'

Memory state around the buggy address:
 001fff800ad5f800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 001fff800ad5f880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>001fff800ad5f900: 00 00 f1 f1 f1 f1 00 00 00 00 00 00 00 00 f3 f3
                                                             ^
 001fff800ad5f980: f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 001fff800ad5fa00: 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00 00 00 00

Cc: <stable@vger.kernel.org>
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
1 file changed