Re: [PATCH 4.19 00/48] 4.19.139-rc1 review

From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Guenter Roeck <linux@roeck-us.net>, Shuah Khan <shuah@kernel.org>,
	patches@kernelci.org,
	Ben Hutchings <ben.hutchings@codethink.co.uk>,
	lkft-triage@lists.linaro.org,
	linux- stable <stable@vger.kernel.org>,
	Masami Hiramatsu <masami.hiramatsu@linaro.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	zanussi@kernel.org
Subject: Re: [PATCH 4.19 00/48] 4.19.139-rc1 review
Date: Tue, 11 Aug 2020 13:58:04 +0530	[thread overview]
Message-ID: <CA+G9fYsZs6u8LH6gJ=bnc8UWrNzLZXnaq2oMY+psNCQPzyPxdQ@mail.gmail.com> (raw)
In-Reply-To: <20200810151804.199494191@linuxfoundation.org>

On Mon, 10 Aug 2020 at 21:00, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 4.19.139 release.
> There are 48 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Wed, 12 Aug 2020 15:17:47 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
>         https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.139-rc1.gz
> or in the git tree and branch at:
>         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h

Results from Linaro’s test farm.
Regressions on x86_64.

We have added LTP tracing test suite this week and started noticing
kernel BUG on x86_64 KASAN enabled kernel. Which means this issue might not be
specific to this release candidate.

[   90.134426] ==================================================================
[   90.141651] BUG: KASAN: use-after-free in trace_stack_print+0x133/0x150
[   90.148264] Read of size 8 at addr ffff888228015ffc by task cat/3569
[   90.154613]
[   90.156106] CPU: 3 PID: 3569 Comm: cat Not tainted 4.19.139-rc1 #1
[   90.162278] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
2.2 05/23/2018
[   90.169669] Call Trace:
[   90.172115]  dump_stack+0x7d/0xaa
[   90.175463]  print_address_description+0x67/0x229
[   90.180165]  ? trace_stack_print+0x133/0x150
[   90.184460]  kasan_report.cold+0xae/0x2fe
[   90.188469]  __asan_load8+0x54/0x90
[   90.191959]  trace_stack_print+0x133/0x150
[   90.196051]  print_trace_line+0x3c7/0x930
[   90.200063]  ? tracing_buffers_read+0x310/0x310
[   90.204589]  tracing_read_pipe+0x2db/0x530
[   90.208687]  __vfs_read+0xe5/0x3c0
[   90.212093]  ? __x64_sys_copy_file_range+0x360/0x360
[   90.217059]  ? fsnotify+0x7cb/0x7f0
[   90.220550]  ? _cond_resched+0x14/0x30
[   90.224296]  ? __inode_security_revalidate+0x5d/0x70
[   90.229262]  ? avc_policy_seqno+0x21/0x30
[   90.233273]  ? security_file_permission+0xc6/0xf0
[   90.237970]  ? security_file_permission+0xc6/0xf0
[   90.242667]  ? rw_verify_area+0x73/0x140
[   90.246584]  vfs_read+0xc8/0x1d0
[   90.249808]  ksys_read+0xbb/0x170
[   90.253120]  ? kernel_write+0xa0/0xa0
[   90.256786]  ? __audit_syscall_exit+0x3bb/0x430
[   90.261320]  __x64_sys_read+0x3e/0x50
[   90.264985]  do_syscall_64+0x63/0x160
[   90.268649]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   90.273693] RIP: 0033:0x7f9596d9e071
[   90.277266] Code: fe ff ff 48 8d 3d 3f 71 09 00 48 83 ec 08 e8 26
ee 01 00 66 0f 1f 44 00 00 48 8d 05 91 e8 2c 00 8b 00 85 c0 75 13 31
c0 0f 05 <48> 3d 00 f0 ff ff 77 57 c3 66 0f 1f 44 00 00 41 54 49 89 d4
55 48
[   90.296011] RSP: 002b:00007ffee5028688 EFLAGS: 00000246 ORIG_RAX:
0000000000000000
[   90.303575] RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 00007f9596d9e071
[   90.310699] RDX: 0000000000020000 RSI: 00007f9597269000 RDI: 0000000000000006
[   90.317823] RBP: 0000000000020000 R08: 00000000ffffffff R09: 0000000000000000
[   90.324947] R10: 00000000000008c6 R11: 0000000000000246 R12: 00007f9597269000
[   90.332071] R13: 0000000000000006 R14: 0000000000000f8e R15: 0000000000020000
[   90.339194]
[   90.340684] The buggy address belongs to the page:
[   90.345470] page:ffffea0008a00540 count:1 mapcount:0
mapping:0000000000000000 index:0x0
[   90.353461] flags: 0x200000000000000()
[   90.357215] raw: 0200000000000000 dead000000000100 dead000000000200
0000000000000000
[   90.364952] raw: 0000000000000000 0000000000000000 00000001ffffffff
0000000000000000
[   90.372681] page dumped because: kasan: bad access detected
[   90.378245]
[   90.379736] Memory state around the buggy address:
[   90.384523]  ffff888228015f00: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
[   90.391741]  ffff888228015f80: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
[   90.398951] >ffff888228016000: fb fb fb fb fb fb fb fb fb fb fb fb
fb fb fb fb
[   90.406161]                    ^
[   90.409407]  ffff888228016080: fc fc fc fc fc fc fc fc fb fb fb fb
fb fb fb fb
[   90.416665]  ffff888228016100: fb fb fb fb fb fb fb fb fc fc fc fc
fc fc fc fc
[   90.423876] ==================================================================
[   90.431095] Disabling lock debugging due to kernel taint

steps to reproduce:
- boot x86_64 with kasan enabled 4.19 stable kernel
- cd /opt/ltp
- ./runltp -f tracing

Full test log link,
https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.138-49-gb0e1bc72f7dd/testrun/3050053/suite/linux-log-parser/test/check-kernel-bug-1656536/log

kernel-config link,
https://builds.tuxbuild.com/BDfU1nbOpLG7hFIf-nv5dQ/kernel.config

Summary
------------------------------------------------------------------------

kernel: 4.19.139-rc1
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-4.19.y
git commit: b0e1bc72f7ddff40c7c5b68313d3ac76495d678d
git describe: v4.19.138-49-gb0e1bc72f7dd
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.138-49-gb0e1bc72f7dd

No fixes (compared to build v4.19.138)

Ran 34683 total tests in the following environments and test suites.

Environments
--------------
- dragonboard-410c - arm64
- hi6220-hikey - arm64
- i386
- juno-r2 - arm64
- juno-r2-compat
- juno-r2-kasan
- nxp-ls2088
- qemu_arm
- qemu_arm64
- qemu_i386
- qemu_x86_64
- x15 - arm
- x86_64
- x86-kasan

Test Suites
-----------
* build
* igt-gpu-tools
* install-android-platform-tools-r2600
* kselftest
* kselftest/drivers
* kselftest/filesystems
* kselftest/net
* kvm-unit-tests
* linux-log-parser
* ltp-cap_bounds-tests
* ltp-containers-tests
* ltp-cpuhotplug-tests
* ltp-crypto-tests
* ltp-cve-tests
* ltp-ipc-tests
* ltp-nptl-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-tracing-tests
* v4l2-compliance
* ltp-commands-tests
* ltp-controllers-tests
* ltp-dio-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-tests
* ltp-fs-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-fsx-tests
* ltp-io-tests
* ltp-math-tests
* network-basic-tests
* perf
* libhugetlbfs
* ltp-hugetlb-tests
* ltp-mm-tests
* ltp-open-posix-tests
* ssuite
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-native/drivers
* kselftest-vsyscall-mode-native/filesystems
* kselftest-vsyscall-mode-native/net
* kselftest-vsyscall-mode-none
* kselftest-vsyscall-mode-none/drivers
* kselftest-vsyscall-mode-none/filesystems
* kselftest-vsyscall-mode-none/net

-- 
Linaro LKFT
https://lkft.linaro.org