Since .message support report results to user directly. We can change some type of message(queryblock/countbadblocks/removebadblock) to return results to user. Besides, we add a interface 'listbadblocks' to list all bad block. If no bad block exists, we will return 'null', or we will list them multi line which each line means one bad block. v2->v3: Realize this logical in .message, change logical for some type message to report results to user too. yangerkun (4): dm dust: report some message results back to user directly dm dust: update doc after message results report to user directly dm dust: add interface to list all badblocks dm dust: introduce listbadblocks in the rst .../admin-guide/device-mapper/dm-dust.rst | 31 +++++++--- drivers/md/dm-dust.c | 58 ++++++++++++++----- 2 files changed, 69 insertions(+), 20 deletions(-) -- 2.25.4 -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
