From: Jens Axboe <axboe@kernel.dk>
To: "zhangyi (F)" <yi.zhang@huawei.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-block@vger.kernel.org, jack@suse.cz
Cc: tytso@mit.edu, viro@zeniv.linux.org.uk, hch@infradead.org,
mcgrof@kernel.org, keescook@chromium.org, yzaikin@google.com
Subject: Re: [RFC PATCH 0/3] block_dump: remove block dump
Date: Mon, 10 May 2021 09:21:56 -0600 [thread overview]
Message-ID: <498fe074-709a-48d6-dfae-bb50ff69c290@kernel.dk> (raw)
In-Reply-To: <20210313030146.2882027-1-yi.zhang@huawei.com>
On 3/12/21 8:01 PM, zhangyi (F) wrote:
> Hi,
>
> block_dump is an old debugging interface and can be replaced by
> tracepoints, and we also found a deadlock issue relate to it[1]. As Jan
> suggested, this patch set delete the whole block_dump feature, we can
> use tracepoints to get the similar information. If someone still using
> this feature cannot switch to use tracepoints or any other suggestions,
> please let us know.
Applied for 5.14, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-05-10 15:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 3:01 [RFC PATCH 0/3] block_dump: remove block dump zhangyi (F)
2021-03-13 3:01 ` [RFC PATCH 1/3] block_dump: remove block_dump feature in mark_inode_dirty() zhangyi (F)
2021-03-15 9:47 ` Jan Kara
2021-03-13 3:01 ` [RFC PATCH 2/3] block_dump: remove block_dump feature zhangyi (F)
2021-03-15 9:48 ` Jan Kara
2021-03-13 3:01 ` [RFC PATCH 3/3] block_dump: remove comments in docs zhangyi (F)
2021-03-15 9:48 ` Jan Kara
2021-03-13 3:37 ` [RFC PATCH 0/3] block_dump: remove block dump Jens Axboe
2021-05-10 1:29 ` Zhang Yi
2021-03-15 9:56 ` Christoph Hellwig
2021-05-10 15:21 ` 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=498fe074-709a-48d6-dfae-bb50ff69c290@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=keescook@chromium.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=yi.zhang@huawei.com \
--cc=yzaikin@google.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).