* [LTP] [PATCH 4.14 00/46] 4.14.169-stable review
[not found] <20200128135749.822297911@linuxfoundation.org>
@ 2020-01-29 4:53 ` Naresh Kamboju
2020-01-29 9:16 ` Jan Stancek
0 siblings, 1 reply; 4+ messages in thread
From: Naresh Kamboju @ 2020-01-29 4:53 UTC (permalink / raw)
To: ltp
On Tue, 28 Jan 2020 at 19:28, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 4.14.169 release.
> There are 46 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 Thu, 30 Jan 2020 13:57:09 +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.14.169-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.14.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Results from Linaro?s test farm.
No regressions on arm64, arm, x86_64, and i386.
NOTE:
LTP fs test read_all_proc fails intermittently on 4.9 and 4.14 branches.
Summary
------------------------------------------------------------------------
kernel: 4.14.169-rc1
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-4.14.y
git commit: 5986a79ae28421d7027cb4ab78fba7d787a9f06e
git describe: v4.14.168-47-g5986a79ae284
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.168-47-g5986a79ae284
No regressions (compared to build v4.14.168)
No fixes (compared to build v4.14.168)
Ran 24221 total tests in the following environments and test suites.
Environments
--------------
- dragonboard-410c - arm64
- hi6220-hikey - arm64
- i386
- juno-r2 - arm64
- qemu_arm
- qemu_arm64
- qemu_i386
- qemu_x86_64
- x15 - arm
- x86_64
Test Suites
-----------
* build
* install-android-platform-tools-r2600
* kselftest
* libhugetlbfs
* linux-log-parser
* ltp-cap_bounds-tests
* ltp-commands-tests
* ltp-containers-tests
* ltp-cpuhotplug-tests
* ltp-cve-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-hugetlb-tests
* ltp-io-tests
* ltp-ipc-tests
* ltp-math-tests
* ltp-mm-tests
* ltp-nptl-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* perf
* spectre-meltdown-checker-test
* v4l2-compliance
* network-basic-tests
* ltp-open-posix-tests
* kvm-unit-tests
* ssuite
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-none
--
Linaro LKFT
https://lkft.linaro.org
^ permalink raw reply [flat|nested] 4+ messages in thread
* [LTP] [PATCH 4.14 00/46] 4.14.169-stable review
2020-01-29 4:53 ` [LTP] [PATCH 4.14 00/46] 4.14.169-stable review Naresh Kamboju
@ 2020-01-29 9:16 ` Jan Stancek
2020-01-29 10:27 ` Naresh Kamboju
0 siblings, 1 reply; 4+ messages in thread
From: Jan Stancek @ 2020-01-29 9:16 UTC (permalink / raw)
To: ltp
----- Original Message -----
> NOTE:
> LTP fs test read_all_proc fails intermittently on 4.9 and 4.14 branches.
[trim CC list to LTP]
Naresh, do you have some examples of these failures?
Has it started recently or do you see it long-term?
Is test timing out on some specific /proc entries?
If yes, is it possible to run test with strace or with "-v" so we can
see where it's getting stuck?
Thanks,
Jan
^ permalink raw reply [flat|nested] 4+ messages in thread
* [LTP] [PATCH 4.14 00/46] 4.14.169-stable review
2020-01-29 9:16 ` Jan Stancek
@ 2020-01-29 10:27 ` Naresh Kamboju
2020-01-31 9:45 ` Jan Stancek
0 siblings, 1 reply; 4+ messages in thread
From: Naresh Kamboju @ 2020-01-29 10:27 UTC (permalink / raw)
To: ltp
On Wed, 29 Jan 2020 at 14:46, Jan Stancek <jstancek@redhat.com> wrote:
>
>
>
> ----- Original Message -----
> > NOTE:
> > LTP fs test read_all_proc fails intermittently on 4.9 and 4.14 branches.
>
> [trim CC list to LTP]
>
> Naresh, do you have some examples of these failures?
Yes.
I have posted the links below.
> Has it started recently or do you see it long-term?
We have seen this from a this test is introduced.
Not specific to any branch. This failure is intermittent and found on
multiple trees and branches.
> Is test timing out on some specific /proc entries?
Yes. When running on qemu devices it is getting timedout.
> If yes, is it possible to run test with strace or with "-v" so we can
> see where it's getting stuck?
Test failed links,
https://lkft.validation.linaro.org/scheduler/job/1143332#L1271
https://lkft.validation.linaro.org/scheduler/job/1143281#L3969
https://lkft.validation.linaro.org/scheduler/job/1142547#L1719
https://lkft.validation.linaro.org/scheduler/job/1145024#L677
https://lkft.validation.linaro.org/scheduler/job/1142037#L4225
Test results comparison link,
https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/tests/ltp-fs-tests/read_all_proc
https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/tests/ltp-fs-tests/read_all_proc
example crash output:
------------------------------
tst_test.c:1118: INFO: Timeout per run is 0h 15m 00s
[ 1136.978957] BUG: unable to handle kernel NULL pointer dereference at 00000004
[ 1136.979046] IP: [<c125da77>] path_openat+0xd7/0x16d0
[ 1136.979046] *pde = 00000000 [ 1136.979046]
[ 1136.979046] Oops: 0000 [#1] SMP
[ 1136.979046] Modules linked in: tun fuse
[ 1136.979046] CPU: 1 PID: 6535 Comm: read_all Not tainted 4.9.212-rc2 #1
[ 1136.979046] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.12.0-1 04/01/2014
[ 1136.979046] task: f56e6300 task.stack: f3ada000
[ 1136.979046] EIP: 0060:[<c125da77>] EFLAGS: 00010246 CPU: 1
[ 1136.979046] EIP is at path_openat+0xd7/0x16d0
[ 1136.979046] EAX: 00000000 EBX: f3fb6210 ECX: f3adbf54 EDX: 0000000d
[ 1136.979046] ESI: 00000800 EDI: f3adbea4 EBP: f3adbe98 ESP: f3adbddc
[ 1136.979046] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[ 1136.979046] CR0: 80050033 CR2: 00000004 CR3: 33a72000 CR4: 003406d0
[ 1136.979046] Stack:
[ 1136.979046] f3adbe38 00000246 f56e6300 f56e6300 00000001 f56e6300
00000001 f56e6300
[ 1136.979046] f3adbeac f56e6300 00000001 00000041 f56e68a8 f3a7e500
00000046 f56e6300
[ 1136.979046] 00000000 f3adbf54 00000000 00000000 f56e68a8 f3adbeb8
c111fcde c26cd460
[ 1136.979046] Call Trace:
[ 1136.979046] [<c111fcde>] ? __lock_acquire+0x24e/0x12e0
[ 1136.979046] [<c113c87a>] ? debug_lockdep_rcu_enabled+0x1a/0x30
[ 1136.979046] [<c126009e>] do_filp_open+0x5e/0xb0
[ 1136.979046] [<c1af1b72>] ? _raw_spin_unlock+0x22/0x30
[ 1136.979046] [<c1270eed>] ? __alloc_fd+0xbd/0x1d0
[ 1136.979046] [<c124ce1c>] do_sys_open+0x19c/0x240
[ 1136.979046] [<c1214e11>] ? __might_fault+0x41/0xa0
[ 1136.979046] [<c124cf10>] SyS_openat+0x20/0x30
[ 1136.979046] [<c1001cd8>] do_fast_syscall_32+0xa8/0x240
[ 1136.979046] [<c1af2330>] sysenter_past_esp+0x45/0x74
[ 1136.979046] Code: 20 f2 ff ff 3d 00 f0 ff ff 0f 87 85 05 00 00 89
fa e8 5e ec ff ff 85 c0 89 c6 0f 85 76 05 00 00 8b 5f 04 8b 4d 88 8b
43 30 8b 31 <8b> 50 04 0f b7 00 89 75 8c 81 e6 00 02 00 00 89 75 80 89
95 74
[ 1136.979046] EIP: [<c125da77>] [ 1136.979046] path_openat+0xd7/0x16d0
[ 1136.979046] SS:ESP 0068:f3adbddc
[ 1136.979046] CR2: 0000000000000004
[ 1136.979046] ---[ end trace 01501609579dce3c ]---
[ 1136.979046] BUG: sleeping function called from invalid context at
/usr/src/kernel/include/linux/sched.h:3154
[ 1136.979046] in_atomic(): 1, irqs_disabled(): 1, pid: 6535, name: read_all
[ 1136.979046] INFO: lockdep is turned off.
[ 1136.979046] irq event stamp: 14908
[ 1136.979046] hardirqs last enabled at (14907): [<c125c084>]
lookup_fast+0x1f4/0x330
[ 1136.979046] hardirqs last disabled at (14908): [<c1af327f>]
error_code+0x5b/0x7c
[ 1136.979046] softirqs last enabled at (13428): [<c1af5695>]
__do_softirq+0x2e5/0x457
[ 1136.979046] softirqs last disabled at (13421): [<c108b835>]
call_on_stack+0x45/0x50
[ 1136.979046] CPU: 1 PID: 6535 Comm: read_all Tainted: G D
4.9.212-rc2 #1
[ 1136.979046] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.12.0-1 04/01/2014
[ 1136.979046] f3adbee4 c142af02 f56e6300 f56e6788 f3adbf0c c10f6598
c1db2154 00000001
[ 1136.979046] 00000001 00001987 f56e6788 f56e6300 00000000 f56e6300
f3adbf40 c10f66d3
[ 1136.979046] 00000000 00000800 00000002 ffffff9c f57d4000 00000006
ffffff9c f3adbf74
[ 1136.979046] Call Trace:
[ 1136.979046] [<c142af02>] dump_stack+0x6e/0x9c
[ 1136.979046] [<c10f6598>] ___might_sleep+0x138/0x240
[ 1136.979046] [<c10f66d3>] __might_sleep+0x33/0xa0
[ 1136.979046] [<c124ce1c>] ? do_sys_open+0x19c/0x240
[ 1136.979046] [<c10de76f>] exit_signals+0x1f/0x220
[ 1136.979046] [<c10d098b>] do_exit+0x8b/0xbd0
[ 1136.979046] [<c124cf10>] ? SyS_openat+0x20/0x30
[ 1136.979046] [<c1001cd8>] ? do_fast_syscall_32+0xa8/0x240
[ 1136.979046] [<c1af342d>] rewind_stack_do_exit+0x11/0x13
[ 1136.979046] note: read_all[6535] exited with preempt_count 1
read_all.c:313: BROK: queue_push(workers[j].q, path) timed out
- Naresh
^ permalink raw reply [flat|nested] 4+ messages in thread
* [LTP] [PATCH 4.14 00/46] 4.14.169-stable review
2020-01-29 10:27 ` Naresh Kamboju
@ 2020-01-31 9:45 ` Jan Stancek
0 siblings, 0 replies; 4+ messages in thread
From: Jan Stancek @ 2020-01-31 9:45 UTC (permalink / raw)
To: ltp
----- Original Message -----
> On Wed, 29 Jan 2020 at 14:46, Jan Stancek <jstancek@redhat.com> wrote:
> >
> >
> >
> > ----- Original Message -----
> > > NOTE:
> > > LTP fs test read_all_proc fails intermittently on 4.9 and 4.14 branches.
> >
> > [trim CC list to LTP]
> >
> > Naresh, do you have some examples of these failures?
>
> Yes.
> I have posted the links below.
>
> > Has it started recently or do you see it long-term?
>
> We have seen this from a this test is introduced.
> Not specific to any branch. This failure is intermittent and found on
> multiple trees and branches.
Those look like kernel bugs, but it's hard to see what /proc entries
trigger it.
I've been running v5.5 and read_all_proc for ~24 hours on aarch64,
but so far no crashes.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-01-31 9:45 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20200128135749.822297911@linuxfoundation.org>
2020-01-29 4:53 ` [LTP] [PATCH 4.14 00/46] 4.14.169-stable review Naresh Kamboju
2020-01-29 9:16 ` Jan Stancek
2020-01-29 10:27 ` Naresh Kamboju
2020-01-31 9:45 ` Jan Stancek
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox