From: Jens Axboe <axboe@kernel.dk>
To: linux-btrace@vger.kernel.org, 303146950@qq.com
Cc: Kou Wenqi <kouwenqi@kylinos.cn>
Subject: Re: [PATCH v3] blkparse: Fix a potential coredump issue
Date: Thu, 20 Mar 2025 05:07:29 -0600 [thread overview]
Message-ID: <174246884926.141685.16632673075725802151.b4-ty@kernel.dk> (raw)
In-Reply-To: <tencent_DE806EEE1852F9E79115172254B8A2789207@qq.com>
On Wed, 19 Mar 2025 21:02:49 +0800, 303146950@qq.com wrote:
> Executing "blkparse -t" may cause coredump due to
> accessing uninitialized memory.
>
> 8,16 0 6092 1.436280373 20685 Q W 15356912 + 4096 [kworker/u256:2]
> 8,16 0 6093 1.436282093 20685 X W 15356912 / 15357936 [kworker/u256:2]
> 8,16 0 6094 1.436282735 20685 G W 15356912 + 1024 [kworker/u256:2]
> 8,16 0 6099 1.436358617 20685 X W 15357936 / 15358960 [kworker/u256:2]
> 8,16 0 6100 1.436359418 20685 G W 15357936 + 1024 [kworker/u256:2]
> 8,16 0 6102 1.436359931 20685 I W 15356912 + 1024 [kworker/u256:2]
> 8,16 0 6103 1.436360874 20685 D W 15356912 + 1024 [kworker/u256:2]
> 8,16 0 6105 1.436436572 20685 X W 15358960 / 15359984 [kworker/u256:2]
> 8,16 0 6106 1.436437679 20685 G W 15358960 + 1024 [kworker/u256:2]
> 8,16 0 6108 1.436438205 20685 I W 15357936 + 1024 [kworker/u256:2]
> 8,16 0 6109 1.436439368 20685 D W 15357936 + 1024 [kworker/u256:2]
> 8,16 0 6111 1.436530404 20685 G W 15359984 + 1024 [kworker/u256:2]
> 8,16 0 6113 1.436530842 20685 I W 15358960 + 1024 [kworker/u256:2]
> 8,16 0 6114 1.436531748 20685 D W 15358960 + 1024 [kworker/u256:2]
> 8,16 0 6120 1.436755261 20685 I W 15359984 + 1024 [kworker/u256:2]
> 8,16 0 6121 1.436756476 20685 D W 15359984 + 1024 [kworker/u256:2]
> 8,16 0 6128 1.437120354 0 C W 15356912 + 1024 [0]
> 8,16 0 6129 1.437121875 0 C W 15356912 + 2048 [0]
>
> [...]
Applied, thanks!
[1/1] blkparse: Fix a potential coredump issue
commit: f9bd00dfbd67ce62ca6df6f55d6275b523cd0b39
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-03-20 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 13:02 [PATCH v3] blkparse: Fix a potential coredump issue 303146950
2025-03-19 13:10 ` Jens Axboe
2025-03-20 1:49 ` 303146950
2025-03-20 11:07 ` Jens Axboe
2025-03-20 11:07 ` Jens Axboe [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=174246884926.141685.16632673075725802151.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=303146950@qq.com \
--cc=kouwenqi@kylinos.cn \
--cc=linux-btrace@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.