From: Jens Axboe <axboe@kernel.dk>
To: "Xu, Yanfei" <yanfei.xu@windriver.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org,
"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: BUG:loop:blk_update_request: I/O error, dev loop6, sector 49674 op 0x9:(WRITE_ZEROES)
Date: Tue, 12 May 2020 20:22:08 -0600 [thread overview]
Message-ID: <8f3eeb22-2e85-aa3f-6287-b3c467d39a8e@kernel.dk> (raw)
In-Reply-To: <c51460e0-1abb-799d-9ee9-de9c39315eda@windriver.com>
On 5/12/20 8:14 PM, Xu, Yanfei wrote:
> 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]
Please CC the author of that commit too. Leaving the rest quoted below.
> Kernrel version: Linux version 5.6.0
>
> Frequency: everytime
>
> 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/TO/image
>
> 6.mkfs.ext2 /dev/loop6
>
>
> Any comments will be appreciated.
>
>
> Thanks,
>
> Yanfei
>
>
>
>
>
--
Jens Axboe
next parent reply other threads:[~2020-05-13 2:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dac81506-0065-ee64-fcd1-c9f1d002b4fb@windriver.com>
[not found] ` <c51460e0-1abb-799d-9ee9-de9c39315eda@windriver.com>
2020-05-13 2:22 ` Jens Axboe [this message]
2020-05-13 16:41 ` BUG:loop:blk_update_request: I/O error, dev loop6, sector 49674 op 0x9:(WRITE_ZEROES) Darrick J. Wong
2020-05-14 16:10 ` Xu, Yanfei
2020-05-13 13:10 Xu, Yanfei
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=8f3eeb22-2e85-aa3f-6287-b3c467d39a8e@kernel.dk \
--to=axboe@kernel.dk \
--cc=darrick.wong@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yanfei.xu@windriver.com \
/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).