On Wed, Sep 26, 2018 at 11:31 AM Linaro QA qa-reports@linaro.org wrote:
Summary
kernel: 4.14.72 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: 2cc4d365363b1fb681b8231adcf4a8f80082506c git describe: v4.14.71-170-g2cc4d365363b Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.71-17...
Regressions (compared to build v4.14.71-171-ga514b8f4ac33)
x15 - arm: kselftest: * proc_read
* test src: https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.18.tar.xz
looks like kselftest, while checking "/proc/self/fd" (most likely, if this has happened on fd-001-lookup.c test), tried to read the file descriptors being used by "self" (running task) and the conversion from a string (the filename, representing a file descriptor) to unsigned long long has overflowed OR no digits were seen. This would suggest that STDOUT file descriptor wasn't represented at proc/self/fd/ directory yet.
OR
if testing proc-uptime-001 or proc-uptime-002, the proc_uptime logic, which also calls xstrtoull(), faced similar issue when trying to read /proc/uptime (format: ull ull) and could not convert string to unsigned long long.