From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: block: potential bug on linux-block/for-next
Date: Wed, 23 Feb 2022 02:49:12 +0000 [thread overview]
Message-ID: <ecc72e5f-dd71-d940-d50d-0347631a7933@nvidia.com> (raw)
Hi,
After today's pull on linux-block/for-next test QEMU is not able to
boot, any information about how to solve this will be helpful as
it is blocking blktest testing, here is dmsg :-
[ 1.304698] ata1.00: Read log 0x00 page 0x00 failed, Emask 0x1
[ 1.305587] ata1.01: Read log 0x00 page 0x00 failed, Emask 0x1
[ 1.455959] systemd[1]: Cannot be run in a chroot() environment.
[ 1.456743] systemd[1]: Freezing execution.
HEAD:-
# git log -2
commit 5774f2f04654804f8e0a40cfe8ff3f8ce3c0b6c9 (HEAD -> for-next,
origin/for-next)
Merge: 7e0469db34b8 2ff4ec783f4c
Author: Jens Axboe <axboe@kernel.dk>
Date: Tue Feb 22 13:00:39 2022 -0700
Merge branch 'for-5.18/drivers' into for-next
* for-5.18/drivers:
null_blk: null_alloc_page() cleanup
null_blk: remove hardcoded null_alloc_page() param
commit 2ff4ec783f4c635289384398d14b241f21bce269 (origin/for-5.18/drivers)
Author: Chaitanya Kulkarni <kch@nvidia.com>
Date: Tue Feb 22 07:28:52 2022 -0800
null_blk: null_alloc_page() cleanup
Remove goto labels and use direct returns as error unwinding code only
needs to free t_page variable if we alloc_pages() call fails as having
two labels for one kfree() can be avoided easily.
Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Link: https://lore.kernel.org/r/20220222152852.26043-3-kch@nvidia.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
-ck
next reply other threads:[~2022-02-23 2:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 2:49 Chaitanya Kulkarni [this message]
2022-02-23 2:58 ` block: potential bug on linux-block/for-next Jens Axboe
2022-02-23 3:14 ` Chaitanya Kulkarni
2022-02-23 3:18 ` Jens Axboe
2022-02-23 4:13 ` Chaitanya Kulkarni
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=ecc72e5f-dd71-d940-d50d-0347631a7933@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=linux-block@vger.kernel.org \
/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