From: Dongsheng Yang <dongsheng.yang@easystack.cn>
To: Christoph Hellwig <hch@infradead.org>
Cc: colyli@suse.de, linux-bcache@vger.kernel.org,
linux-kernel@vger.kernel.org, mchristi@redhat.com
Subject: Re: [PATCH] bcache: dont reset bio opf in bch_data_insert_start
Date: Thu, 28 Jan 2021 17:10:18 +0800 [thread overview]
Message-ID: <e360e24b-7c6e-f7b3-ee59-e4f9d7dd3576@easystack.cn> (raw)
In-Reply-To: <20210127173726.GA1738577@infradead.org>
Hi Christop:
在 2021/1/28 星期四 上午 1:37, Christoph Hellwig 写道:
> But the old code is also completely broken. We can't just OR in
> the op, as that implicitly assumes the old op was 0 (REQ_OP_READ).
Yes, indeed, there is an assume that the op is just possible to be 0
(REQ_OP_READ) or 1 (REQ_OP_WRITE).
REQ_OP_WRITE is from cached_dev_submit_bio() which would be submitted by
upper user.
REQ_OP_READ is from bcache itself, such as cached_dev_read_done() (when
we found cache miss, we will read
data from backing and then we want to insert it into cache device. then
there is a read bio with data reach here, we
need to set the bio_op to REQ_OP_WRITE, and send this bio to cache device).
> Please fix this to explicitly set the exact op and flags that you want
> instead of this fragile magic.blk_rq_map_kern
This commit only want to fix the logic bug introduced in ad0d9e76a412
("bcache: use bio op accessors"),
that's more likely a partial revert.
I agree that we can make it more clearly and explicitly.
But I found there is no accessor to set op only, besides, the
bio_set_op_attrs() was marked as obsolete.
There are some others doing similar things as below:
blk_rq_map_kern():
bio->bi_opf &= ~REQ_OP_MASK;
bio->bi_opf |= req_op(rq);
So what about below:
diff --git a/drivers/md/bcache/request.c b/drivers/md/bcache/request.c
index c7cadaafa947..bacc7366002f 100644
--- a/drivers/md/bcache/request.c
+++ b/drivers/md/bcache/request.c
@@ -244,7 +244,14 @@ static void bch_data_insert_start(struct closure *cl)
trace_bcache_cache_insert(k);
bch_keylist_push(&op->insert_keys);
- bio_set_op_attrs(n, REQ_OP_WRITE, 0);
+ /*
+ * n here would be REQ_OP_READ, if
+ * we are inserting data read from
+ * backing device in cache miss or
+ * inserting data in movinggc.
+ */
+ n->bi_opf &= ~REQ_OP_MASK;
+ n->bi_opf |= REQ_OP_WRITE;
bch_submit_bbio(n, op->c, k, 0);
} while (n != bio);
Thanx
Yang
next prev parent reply other threads:[~2021-01-28 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 4:29 Dongsheng Yang
2021-01-25 4:53 ` Coly Li
2021-01-26 4:32 ` Dongsheng Yang
2021-01-26 4:34 ` Coly Li
2021-01-26 4:41 ` Dongsheng Yang
2021-01-27 17:37 ` Christoph Hellwig
2021-01-28 9:10 ` Dongsheng Yang [this message]
2021-01-28 10:45 ` Dongsheng Yang
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=e360e24b-7c6e-f7b3-ee59-e4f9d7dd3576@easystack.cn \
--to=dongsheng.yang@easystack.cn \
--cc=colyli@suse.de \
--cc=hch@infradead.org \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchristi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®