dm vdo block-map: use uds_log_ratelimit() rather than open code it

Signed-off-by: Mike Snitzer <snitzer@kernel.org>
Signed-off-by: Matthew Sakai <msakai@redhat.com>

diff --git a/drivers/md/dm-vdo/block-map.c b/drivers/md/dm-vdo/block-map.c
index 64f893b0721a99daf87662f7fe67b6558a58c334..eb838e6ae3e630ab87c4afcb3c711c5a1ddc9253 100644 (file)
--- a/drivers/md/dm-vdo/block-map.c
+++ b/drivers/md/dm-vdo/block-map.c
@@ -1014,13 +1014,9 @@ static void handle_page_write_error(struct vdo_completion *completion)
 
        /* If we're already read-only, write failures are to be expected. */
        if (result != VDO_READ_ONLY) {
-               static DEFINE_RATELIMIT_STATE(error_limiter, DEFAULT_RATELIMIT_INTERVAL,
-                                             DEFAULT_RATELIMIT_BURST);
-
-               if (__ratelimit(&error_limiter)) {
-                       uds_log_error("failed to write block map page %llu",
-                                     (unsigned long long) info->pbn);
-               }
+               uds_log_ratelimit(uds_log_error,
+                                 "failed to write block map page %llu",
+                                 (unsigned long long) info->pbn);
        }
 
        set_info_state(info, PS_DIRTY);