linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@gmail.com>
To: Dongbo Cao <cdbdyx@163.com>
Cc: colyli@suse.de, linux-bcache@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bug fix in function check_should_bypass
Date: Thu, 27 Sep 2018 04:33:13 -0400	[thread overview]
Message-ID: <20180927083313.GA29959@kmo-pixel> (raw)
In-Reply-To: <20180927082749.2243-1-cdbdyx@163.com>

On Thu, Sep 27, 2018 at 04:27:49PM +0800, Dongbo Cao wrote:
> bio->bi_iter.bi_sector is the sector index of current request, no need to be aligned.
> instead, bio->bi_iter.bi_size should be aligned to block_bytes-1, not block_size-1.
> and bio_sectors is the number of sectors of current request, also no need to be aligned, just remove it.

this isn't a bug fix, please don't label things as bug fixes that aren't.

also, it's wrong. an unaligned IO that overlaps with data already in the cache
will result in an extent in the cache with misaligned size, which will result in
misaligned IOs when reading from it.

> 
> Signed-off-by: Dongbo Cao <cdbdyx@163.com>
> ---
>  drivers/md/bcache/request.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/md/bcache/request.c b/drivers/md/bcache/request.c
> index 13d3355a..fb3502da 100644
> --- a/drivers/md/bcache/request.c
> +++ b/drivers/md/bcache/request.c
> @@ -398,8 +398,7 @@ static bool check_should_bypass(struct cached_dev *dc, struct bio *bio)
>  	    !(bio->bi_opf & REQ_PRIO))
>  		goto skip;
>  
> -	if (bio->bi_iter.bi_sector & (c->sb.block_size - 1) ||
> -	    bio_sectors(bio) & (c->sb.block_size - 1)) {
> +	if (bio->bi_iter.bi_size & (block_bytes(c) - 1)) {
>  		pr_debug("skipping unaligned io");
>  		goto skip;
>  	}
> -- 
> 2.17.1
> 
> 

      reply	other threads:[~2018-09-27  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27  8:27 [PATCH] bug fix in function check_should_bypass Dongbo Cao
2018-09-27  8:33 ` Kent Overstreet [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=20180927083313.GA29959@kmo-pixel \
    --to=kent.overstreet@gmail.com \
    --cc=cdbdyx@163.com \
    --cc=colyli@suse.de \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).