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 (local)
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