From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: shinichiro.kawasaki@wdc.com, jaegeuk@kernel.org,
yi.zhang@redhat.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: multidev: fix to recognize valid zero block address
Date: Sun, 14 Apr 2024 15:32:45 +0000 [thread overview]
Message-ID: <171310876546.3156.9489013504825208651.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240327074223.2216487-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 27 Mar 2024 15:42:23 +0800 you wrote:
> As reported by Yi Zhang in mailing list [1], kernel warning was catched
> during zbd/010 test as below:
>
> ./check zbd/010
> zbd/010 (test gap zone support with F2FS) [failed]
> runtime ... 3.752s
> something found in dmesg:
> [ 4378.146781] run blktests zbd/010 at 2024-02-18 11:31:13
> [ 4378.192349] null_blk: module loaded
> [ 4378.209860] null_blk: disk nullb0 created
> [ 4378.413285] scsi_debug:sdebug_driver_probe: scsi_debug: trim
> poll_queues to 0. poll_q/nr_hw = (0/1)
> [ 4378.422334] scsi host15: scsi_debug: version 0191 [20210520]
> dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0
> [ 4378.434922] scsi 15:0:0:0: Direct-Access-ZBC Linux
> scsi_debug 0191 PQ: 0 ANSI: 7
> [ 4378.443343] scsi 15:0:0:0: Power-on or device reset occurred
> [ 4378.449371] sd 15:0:0:0: Attached scsi generic sg5 type 20
> [ 4378.449418] sd 15:0:0:0: [sdf] Host-managed zoned block device
> ...
> (See '/mnt/tests/gitlab.com/api/v4/projects/19168116/repository/archive.zip/storage/blktests/blk/blktests/results/nodev/zbd/010.dmesg'
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: multidev: fix to recognize valid zero block address
https://git.kernel.org/jaegeuk/f2fs/c/33e62cd7b4c2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2024-04-14 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 7:42 [f2fs-dev] [PATCH v2] f2fs: multidev: fix to recognize valid zero block address Chao Yu
2024-04-14 15:32 ` patchwork-bot+f2fs [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=171310876546.3156.9489013504825208651.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=yi.zhang@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).