From: Eric Biggers <ebiggers@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-block <linux-block@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
lkft-triage@lists.linaro.org, Jens Axboe <axboe@kernel.dk>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Ming Lei <ming.lei@redhat.com>
Subject: Re: next: BUG: sleeping function called from invalid context at block/blk-sysfs.c:766
Date: Fri, 25 Mar 2022 20:21:17 +0000 [thread overview]
Message-ID: <Yj4kPcW0Zw2Xv+jY@gmail.com> (raw)
In-Reply-To: <CA+G9fYtZpazsDTQo9N-4U=T5QvEKTu_xDi=W+1_7ng51306LYg@mail.gmail.com>
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@redhat.com>
Date: Wed Mar 23 09:13:08 2022 +0800
block: avoid calling blkg_free() in atomic context
prev parent reply other threads:[~2022-03-25 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 8:34 next: BUG: sleeping function called from invalid context at block/blk-sysfs.c:766 Naresh Kamboju
2022-03-25 20:21 ` Eric Biggers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yj4kPcW0Zw2Xv+jY@gmail.com \
--to=ebiggers@kernel.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=ming.lei@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).