stable-rc 5.3.7-rc1/973b124921fc: regressions detected in project stable v5.3.y on OE - sanity
Summary ------------------------------------------------------------------------
kernel: 5.3.7-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.3.y git commit: 973b124921fc639825ae455aa91ed9ce15167584 git describe: v5.3.6-84-g973b124921fc Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.3-oe-sanity/build/v5.3....
Regressions (compared to build v5.3.6) ------------------------------------------------------------------------
dragonboard-410c: build: * build_process
i386: build: * build_process
x86: build: * build_process
hi6220-hikey: build: * build_process
x15: build: * build_process
No fixes (compared to build v5.3.6)
Boards, architectures and test suites: -------------------------------------
dragonboard-410c * build - fail: 1,
hi6220-hikey * build - fail: 1,
i386 * build - fail: 1,
juno-r2 * build - fail: 1,
x15 * build - fail: 1,
x86 * build - fail: 1,
On Tue, Oct 15, 2019 at 08:46:56AM +0000, Linaro QA wrote:
Summary
kernel: 5.3.7-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.3.y git commit: 973b124921fc639825ae455aa91ed9ce15167584 git describe: v5.3.6-84-g973b124921fc Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.3-oe-sanity/build/v5.3....
Regressions (compared to build v5.3.6)
dragonboard-410c: build: * build_process
What does this mean?
On Tue, 15 Oct 2019 at 15:21, Greg KH gregkh@linuxfoundation.org wrote:
On Tue, Oct 15, 2019 at 08:46:56AM +0000, Linaro QA wrote:
Summary
kernel: 5.3.7-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.3.y git commit: 973b124921fc639825ae455aa91ed9ce15167584 git describe: v5.3.6-84-g973b124921fc Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.3-oe-sanity/build/v5.3....
Regressions (compared to build v5.3.6)
dragonboard-410c: build: * build_process
What does this mean?
All 5.3 branch build failed.
Build log from x86_64 ------------------------------
In file included from fs/io_uring.c:42:0: fs/io_uring.c: In function 'io_destruct_skb': include/linux/kernel.h:47:52: error: invalid use of undefined type 'struct workqueue_struct' #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + __must_be_array(arr)) ^ fs/io_uring.c:2570:18: note: in expansion of macro 'ARRAY_SIZE' for (i = 0; i < ARRAY_SIZE(ctx->sqo_wq); i++) ^~~~~~~~~~ include/linux/kernel.h:47:52: error: dereferencing pointer to incomplete type 'struct workqueue_struct' #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + __must_be_array(arr)) ^ fs/io_uring.c:2570:18: note: in expansion of macro 'ARRAY_SIZE' for (i = 0; i < ARRAY_SIZE(ctx->sqo_wq); i++) ^~~~~~~~~~ In file included from include/linux/kernel.h:16:0, from fs/io_uring.c:42: include/linux/compiler.h:357:67: error: invalid use of undefined type 'struct workqueue_struct' #define __must_be_array(a) BUILD_BUG_ON_ZERO(__same_type((a), &(a)[0])) ^ include/linux/build_bug.h:16:56: note: in definition of macro 'BUILD_BUG_ON_ZERO' #define BUILD_BUG_ON_ZERO(e) (sizeof(struct { int:(-!!(e)); })) ^ include/linux/compiler.h:357:46: note: in expansion of macro '__same_type' #define __must_be_array(a) BUILD_BUG_ON_ZERO(__same_type((a), &(a)[0])) ^~~~~~~~~~~ include/linux/kernel.h:47:59: note: in expansion of macro '__must_be_array' #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + __must_be_array(arr)) ^~~~~~~~~~~~~~~ fs/io_uring.c:2570:18: note: in expansion of macro 'ARRAY_SIZE' for (i = 0; i < ARRAY_SIZE(ctx->sqo_wq); i++) ^~~~~~~~~~ include/linux/build_bug.h:16:45: error: bit-field '<anonymous>' width not an integer constant #define BUILD_BUG_ON_ZERO(e) (sizeof(struct { int:(-!!(e)); })) ^ include/linux/compiler.h:357:28: note: in expansion of macro 'BUILD_BUG_ON_ZERO' #define __must_be_array(a) BUILD_BUG_ON_ZERO(__same_type((a), &(a)[0])) ^~~~~~~~~~~~~~~~~ include/linux/kernel.h:47:59: note: in expansion of macro '__must_be_array' #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + __must_be_array(arr)) ^~~~~~~~~~~~~~~ fs/io_uring.c:2570:18: note: in expansion of macro 'ARRAY_SIZE' for (i = 0; i < ARRAY_SIZE(ctx->sqo_wq); i++) ^~~~~~~~~~ fs/io_uring.c:2571:18: error: invalid use of undefined type 'struct workqueue_struct' if (ctx->sqo_wq[i]) ^ fs/io_uring.c:2572:31: error: invalid use of undefined type 'struct workqueue_struct' flush_workqueue(ctx->sqo_wq[i]); ^ CC net/wireless/nl80211.o
Full build log, https://ci.linaro.org/view/lkft/job/openembedded-lkft-linux-stable-rc-5.3/DI...
- Naresh
On Tue, 15 Oct 2019 at 15:21, Greg KH gregkh@linuxfoundation.org wrote:
On Tue, Oct 15, 2019 at 08:46:56AM +0000, Linaro QA wrote:
Summary
kernel: 5.3.7-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.3.y git commit: 973b124921fc639825ae455aa91ed9ce15167584 git describe: v5.3.6-84-g973b124921fc Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.3-oe-sanity/build/v5.3....
Regressions (compared to build v5.3.6)
dragonboard-410c: build: * build_process
What does this mean?
5.3 branch build failed for x86_64, i386, arm and arm64.
$ git bisect good 642ac0f454dad9a68150e4bd37975cee0126f258 is the first bad commit commit 642ac0f454dad9a68150e4bd37975cee0126f258 Author: Jens Axboe axboe@kernel.dk Date: Wed Oct 9 14:40:13 2019 -0600
io_uring: only flush workqueues on fileset removal
commit 8a99734081775c012a4a6c442fdef0379fe52bdf upstream.
We should not remove the workqueue, we just need to ensure that the workqueues are synced. The workqueues are torn down on ctx removal.
Cc: stable@vger.kernel.org Fixes: 6b06314c47e1 ("io_uring: add file set registration") Reported-by: Stefan Hajnoczi stefanha@redhat.com Signed-off-by: Jens Axboe axboe@kernel.dk Signed-off-by: Greg Kroah-Hartman gregkh@linuxfoundation.org
:040000 040000 e4f50c640ef3a2235cd540b1d67b0aad97a087ac 1bc7d774ce0be0e8def5504c840d0f6ccc8d0695 M fs
- Naresh
On Wed, Oct 16, 2019 at 01:20:17PM +0530, Naresh Kamboju wrote:
On Tue, 15 Oct 2019 at 15:21, Greg KH gregkh@linuxfoundation.org wrote:
On Tue, Oct 15, 2019 at 08:46:56AM +0000, Linaro QA wrote:
Summary
kernel: 5.3.7-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.3.y git commit: 973b124921fc639825ae455aa91ed9ce15167584 git describe: v5.3.6-84-g973b124921fc Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.3-oe-sanity/build/v5.3....
Regressions (compared to build v5.3.6)
dragonboard-410c: build: * build_process
What does this mean?
5.3 branch build failed for x86_64, i386, arm and arm64.
$ git bisect good 642ac0f454dad9a68150e4bd37975cee0126f258 is the first bad commit commit 642ac0f454dad9a68150e4bd37975cee0126f258 Author: Jens Axboe axboe@kernel.dk Date: Wed Oct 9 14:40:13 2019 -0600
io_uring: only flush workqueues on fileset removal commit 8a99734081775c012a4a6c442fdef0379fe52bdf upstream. We should not remove the workqueue, we just need to ensure that the workqueues are synced. The workqueues are torn down on ctx removal. Cc: stable@vger.kernel.org Fixes: 6b06314c47e1 ("io_uring: add file set registration") Reported-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Jens Axboe <axboe@kernel.dk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>:040000 040000 e4f50c640ef3a2235cd540b1d67b0aad97a087ac 1bc7d774ce0be0e8def5504c840d0f6ccc8d0695 M fs
Odd that this doesn't fail on x86. Anyway, the backport needs more work, I've dropped the patch now.
thanks,
greg k-h
-
Greg KH -
Linaro QA -
Naresh Kamboju