[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Yj4kPcW0Zw2Xv+jY@gmail.com>
Date: Fri, 25 Mar 2022 20:21:17 +0000
From: Eric Biggers <ebiggers@...nel.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: linux-block <linux-block@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
lkft-triage@...ts.linaro.org, Jens Axboe <axboe@...nel.dk>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Ming Lei <ming.lei@...hat.com>
Subject: Re: next: BUG: sleeping function called from invalid context at
block/blk-sysfs.c:766
On Thu, Mar 24, 2022 at 02:04:23PM +0530, Naresh Kamboju wrote:
> While running kselftest zram test cases on Linux next-20220324 the kernel BUG
> reported on arm64 Qcom db845 development board.
>
> metadata:
> git_ref: master
> git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
> git_sha: b61581ae229d8eb9f21f8753be3f4011f7692384
> git_describe: next-20220323
> kernel_version: 5.17.0
> kernel-config: https://builds.tuxbuild.com/26mKdspULB326eo6s22cXZzYhmt/config
next-20220323 or next-20220324? Your report is inconsistent. If it's the
former, I'd guess this was already fixed by:
commit d578c770c85233af592e54537f93f3831bde7e9a (linux-block/for-5.18/block)
Author: Ming Lei <ming.lei@...hat.com>
Date: Wed Mar 23 09:13:08 2022 +0800
block: avoid calling blkg_free() in atomic context
Powered by blists - more mailing lists