From: "Xu, Yanfei" <yanfei.xu@windriver.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-block@vger.kernel.org
Subject: [loop]efcfec579: BUG:blk_update_request: I/O error, dev loop6, sector 49674 op 0x9:(WRITE_ZEROES)
Date: Wed, 13 May 2020 10:42:07 +0800 [thread overview]
Message-ID: <3df7e30a-2495-544e-1ac2-3b0afd3e7324@windriver.com> (raw)
Hi,
After operating the /dev/loop which losetup with an image placed in tmpfs,
I got the following ERROR messages:
----------------[cut here]---------------------
[ 183.110770] blk_update_request: I/O error, dev loop6, sector 524160
op 0x9:(WRITE_ZEROES) flags 0x1000800 phys_seg 0 prio class 0
[ 183.123949] blk_update_request: I/O error, dev loop6, sector 522 op
0x9:(WRITE_ZEROES) flags 0x1000800 phys_seg 0 prio class 0
[ 183.137123] blk_update_request: I/O error, dev loop6, sector 16906 op
0x9:(WRITE_ZEROES) flags 0x1000800 phys_seg 0 prio class 0
[ 183.150314] blk_update_request: I/O error, dev loop6, sector 32774 op
0x9:(WRITE_ZEROES) flags 0x1000800 phys_seg 0 prio class 0
[ 183.163551] blk_update_request: I/O error, dev loop6, sector 49674 op
0x9:(WRITE_ZEROES) flags 0x1000800 phys_seg 0 prio class 0
[ 183.176824] blk_update_request: I/O error, dev loop6, sector 65542 op
0x9:(WRITE_ZEROES) flags 0x1000800 phys_seg 0 prio class 0
[ 183.190029] blk_update_request: I/O error, dev loop6, sector 82442 op
0x9:(WRITE_ZEROES) flags 0x1000800 phys_seg 0 prio class 0
[ 183.203281] blk_update_request: I/O error, dev loop6, sector 98310 op
0x9:(WRITE_ZEROES) flags 0x1000800 phys_seg 0 prio class 0
[ 183.216531] blk_update_request: I/O error, dev loop6, sector 115210
op 0x9:(WRITE_ZEROES) flags 0x1000800 phys_seg 0 prio class 0
[ 183.229914] blk_update_request: I/O error, dev loop6, sector 131078
op 0x9:(WRITE_ZEROES) flags 0x1000800 phys_seg 0 prio class 0
I have found the commit which introduce this issue by git bisect :
commit :efcfec57[loop: fix no-unmap write-zeroes request behavior]
Kernrel version: Linux version 5.6.0
Frequency: every time
steps to reproduce:
1.git clone mainline kernel
2.compile kernel with ARCH=x86_64, and then boot the system with it
(seems other arch also can reproduce it )
3.make an image by "dd of=/tmp/image if=/dev/zero bs=1M count=256"
4.place the image in tmpfs directory
5.losetup /dev/loop6 /PATH/image
6.mkfs.ext2 /dev/loop6
Any comments will be appreciated.
Thanks,
Yanfei
reply other threads:[~2020-05-13 2:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3df7e30a-2495-544e-1ac2-3b0afd3e7324@windriver.com \
--to=yanfei.xu@windriver.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).