linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "zhangyi (F)" <yi.zhang@huawei.com>
To: <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>,
	<axboe@kernel.dk>, <mcgrof@kernel.org>, <keescook@chromium.org>,
	<yzaikin@google.com>, <yi.zhang@huawei.com>
Subject: [RFC PATCH 0/3] block_dump: remove block dump
Date: Sat, 13 Mar 2021 11:01:43 +0800	[thread overview]
Message-ID: <20210313030146.2882027-1-yi.zhang@huawei.com> (raw)

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.

Thanks,
Yi.

[1]. https://lore.kernel.org/linux-fsdevel/20210305132442.GA2801131@infradead.org/T/#m385b0f84bc381d3089740e33d94f6e1b67dd06d2

zhangyi (F) (3):
  block_dump: remove block_dump feature in mark_inode_dirty()
  block_dump: remove block_dump feature
  block_dump: remove comments in docs

 .../admin-guide/laptops/laptop-mode.rst       | 11 --------
 Documentation/admin-guide/sysctl/vm.rst       |  8 ------
 block/blk-core.c                              |  9 -------
 fs/fs-writeback.c                             | 25 -------------------
 include/linux/writeback.h                     |  1 -
 kernel/sysctl.c                               |  8 ------
 mm/page-writeback.c                           |  5 ----
 7 files changed, 67 deletions(-)

-- 
2.25.4


             reply	other threads:[~2021-03-13  2:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-13  3:01 zhangyi (F) [this message]
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

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=20210313030146.2882027-1-yi.zhang@huawei.com \
    --to=yi.zhang@huawei.com \
    --cc=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=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).