From: Mike Snitzer <snitzer@redhat.com>
To: Bryan Gurney <bgurney@redhat.com>
Cc: dm-devel@redhat.com, agk@redhat.com
Subject: Re: dm dust: use dust blksz for badblocklist index
Date: Fri, 16 Aug 2019 10:45:26 -0400 [thread overview]
Message-ID: <20190816144526.GA2468@redhat.com> (raw)
In-Reply-To: <1565964593-13195-1-git-send-email-bgurney@redhat.com>
On Fri, Aug 16 2019 at 10:09am -0400,
Bryan Gurney <bgurney@redhat.com> wrote:
> Change the "frontend" dust_remove_block, dust_add_block, and
> dust_query_block functions to store the "dust block number", instead
> of the sector number corresponding to the "dust block number"
>
> For the "backend" functions dust_map_read and dust_map_write,
> right-shift by sect_per_block_shift. This fixes the inability
> to emulate failure beyond the first sector of each "dust block",
> for devices with a "dust block size" larger than 512 bytes.
>
> Signed-off-by: Bryan Gurney <bgurney@redhat.com>
Thanks, I tweaked the header very slightly and staged it in linux-next
for 5.4 via linux-dm.git.
Mike
prev parent reply other threads:[~2019-08-16 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 14:09 [PATCH] dm dust: use dust blksz for badblocklist index Bryan Gurney
2019-08-16 14:45 ` Mike Snitzer [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=20190816144526.GA2468@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=bgurney@redhat.com \
--cc=dm-devel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.