blktrace: log dropped REQ_OP_ZONE_XXX events ver1#554
Closed
blktests-ci[bot] wants to merge 1 commit intolinus-master_basefrom
Closed
blktrace: log dropped REQ_OP_ZONE_XXX events ver1#554blktests-ci[bot] wants to merge 1 commit intolinus-master_basefrom
blktests-ci[bot] wants to merge 1 commit intolinus-master_basefrom
Conversation
Author
|
Upstream branch: c22e26b |
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
519f160 to
49ecc64
Compare
Author
|
Upstream branch: 37a93dd |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
88c8705 to
13ef973
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
49ecc64 to
0525b37
Compare
Author
|
Upstream branch: 7449f86 |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
13ef973 to
24d429b
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
0525b37 to
6de2940
Compare
Author
|
Upstream branch: cee73b1 |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
24d429b to
929749d
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
6de2940 to
bbff8a4
Compare
Author
|
Upstream branch: ca4ee40 |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
929749d to
46f1adc
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
bbff8a4 to
be7af85
Compare
Author
|
Upstream branch: 26a4cfa |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
46f1adc to
8bde3bb
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
be7af85 to
bfa4f99
Compare
Author
|
Upstream branch: 0f2acd3 |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
8bde3bb to
0055b44
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
bfa4f99 to
e2350d3
Compare
Author
|
Upstream branch: 9702969 |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
0055b44 to
c14c13e
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
e2350d3 to
e1fefe2
Compare
Author
|
Upstream branch: 2961f84 |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
c14c13e to
b8ab0ff
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
e1fefe2 to
f714aad
Compare
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
128b6f1 to
1363524
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
c475e20 to
14f6b99
Compare
Author
|
Upstream branch: a75cb86 |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
1363524 to
2c4d907
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
14f6b99 to
856dc37
Compare
Author
|
Upstream branch: 4d349ee |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
2c4d907 to
80a554a
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
856dc37 to
40967f0
Compare
Author
|
Upstream branch: 11439c4 |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
80a554a to
046660e
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
40967f0 to
d4e9bad
Compare
Author
|
Upstream branch: af4e9ef |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
046660e to
2fcfc8c
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
2 times, most recently
from
ecd10e2 to
d0e1bed
Compare
Author
|
Upstream branch: af4e9ef |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
2fcfc8c to
ad78dd2
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
d0e1bed to
6b51c57
Compare
Author
|
Upstream branch: 0031c06 |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
ad78dd2 to
6a407bd
Compare
blktests-ci
Bot
force-pushed
the
linus-master_base
branch
from
6b51c57 to
78036b2
Compare
Add informational messages during blktrace setup when version 1 tools
are used on kernels with CONFIG_BLK_DEV_ZONED enabled. This alerts users
that REQ_OP_ZONE_* events will be dropped and suggests upgrading to
blktrace tools version 2 or later.
The warning is printed once during trace setup to inform users about
the limitation without spamming the logs during tracing operations.
Version 2 blktrace tools properly handle zone management operations
(zone reset, zone open, zone close, zone finish, zone append) that
were added for zoned block devices.
* With old blktrace tool and this patch :-
blktests (master) # ./check blktrace/
blktrace/001 (blktrace zone management command tracing) [passed]
runtime 3.706s ... 3.735s
blktrace/002 (blktrace ftrace corruption with sysfs trace) [passed]
runtime 0.479s ... 0.456s
blktests (master) # dmesg -c
[ 9455.610899] null_blk: disk nullb0 created
[ 9455.610916] null_blk: module loaded
[ 9455.634103] run blktests blktrace/001 at 2026-02-02 15:02:23
[ 9455.651710] null_blk: nullb1: using native zone append
[ 9455.662852] null_blk: disk nullb1 created
*[ 9455.714998] blktrace: nullb1: blktrace events for zone operations will be dropped*
*[ 9455.715065] blktrace: use blktrace tools version >= 2 to track zone operations*
[ 9459.480181] null_blk: disk nullb0 created
[ 9459.480199] null_blk: module loaded
[ 9459.514464] run blktests blktrace/002 at 2026-02-02 15:02:27
[ 9459.541772] null_blk: disk nullb1 created
blktests (master) #
* With new blktrace tools and this patch :-
blktests (master) # ./check blktrace/
blktrace/001 (blktrace zone management command tracing) [passed]
runtime 3.735s ... 3.734s
blktrace/002 (blktrace ftrace corruption with sysfs trace) [passed]
runtime 0.456s ... 0.496s
blktests (master) # dmesg -c
[ 9490.395572] null_blk: disk nullb0 created
[ 9490.395591] null_blk: module loaded
[ 9490.419467] run blktests blktrace/001 at 2026-02-02 15:02:58
[ 9490.436416] null_blk: nullb1: using native zone append
[ 9490.447806] null_blk: disk nullb1 created
[ 9494.262176] null_blk: disk nullb0 created
[ 9494.262195] null_blk: module loaded
[ 9494.296653] run blktests blktrace/002 at 2026-02-02 15:03:02
[ 9494.322261] null_blk: disk nullb1 created
blktests (master) #
This helps users understand why zone operation traces may be missing
when using older blktrace tool versions with modern kernels that
support REQ_OP_ZONE_XXX in blktrace.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
Author
|
Upstream branch: ecc64d2 |
blktests-ci
Bot
force-pushed
the
series/1053254=>linus-master
branch
from
6a407bd to
4d46f28
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull request for series with
subject: blktrace: log dropped REQ_OP_ZONE_XXX events ver1
version: 4
url: https://patchwork.kernel.org/project/linux-block/list/?series=1053254