From: Christoph Hellwig <hch@infradead.org>
To: "jianchao.wang" <jianchao.w.wang@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block: move sanity checking ahead of bi_front/back_seg_size updating
Date: Tue, 19 Sep 2017 07:36:44 -0700 [thread overview]
Message-ID: <20170919143644.GA15944@infradead.org> (raw)
In-Reply-To: <043c8787-1056-c16d-a38d-a421920742de@oracle.com>
On Tue, Sep 19, 2017 at 08:55:59AM +0800, jianchao.wang wrote:
> > But can you elaborate a little more on how this found and if there
> > is a way to easily reproduce it, say for a blktests test case?
> >
> It is found when I made the patch of
> 'block: consider merge of segments when merge bio into rq' , not from an actual
> issue or test case.
Same question applies to that one, I just haven't finished understanding
all the changes in it yet.
next prev parent reply other threads:[~2017-09-19 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 23:10 [PATCH] block: move sanity checking ahead of bi_front/back_seg_size updating Jianchao Wang
2017-09-18 23:51 ` Christoph Hellwig
2017-09-19 0:55 ` jianchao.wang
2017-09-19 14:36 ` Christoph Hellwig [this message]
2017-09-20 1:38 ` jianchao.wang
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=20170919143644.GA15944@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=jianchao.w.wang@oracle.com \
--cc=linux-block@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).