From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
Mike Snitzer <snitzer@redhat.com>,
dm-devel@redhat.com
Cc: NeilBrown <neilb@suse.com>,
stable@vger.kernel.org, Ming Lei <ming.lei@redhat.com>
Subject: Re: [PATCH 3/4] dm: fix missing bio_split() pattern code in __split_and_process_bio()
Date: Tue, 22 Jan 2019 15:56:00 +0000 [thread overview]
Message-ID: <20190122155601.0D5FA217F5@mail.kernel.org> (raw)
In-Reply-To: <20190119180506.1300-4-snitzer@redhat.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 18a25da84354 dm: ensure bio submission follows a depth-first tree walk.
The bot has tested the following trees: v4.20.3, v4.19.16.
v4.20.3: Failed to apply! Possible dependencies:
7ed15898163a ("dm: fix redundant IO accounting for bios that need splitting")
v4.19.16: Failed to apply! Possible dependencies:
7ed15898163a ("dm: fix redundant IO accounting for bios that need splitting")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-01-22 15:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 18:05 [PATCH 0/4] dm: fix various issues with bio splitting code Mike Snitzer
2019-01-19 18:05 ` [PATCH 1/4] dm: fix clone_bio() to trigger blk_recount_segments() Mike Snitzer
2019-01-21 3:25 ` Ming Lei
2019-01-19 18:05 ` [PATCH 2/4] dm: fix redundant IO accounting for bios that need splitting Mike Snitzer
2019-01-21 3:52 ` Ming Lei
2019-01-22 15:55 ` Sasha Levin
2019-01-19 18:05 ` [PATCH 3/4] dm: fix missing bio_split() pattern code in __split_and_process_bio() Mike Snitzer
2019-01-21 3:21 ` Ming Lei
2019-01-21 16:02 ` Mike Snitzer
2019-01-22 2:46 ` Ming Lei
2019-01-22 3:17 ` Mike Snitzer
2019-01-22 3:35 ` Mike Snitzer
2019-01-22 3:49 ` Ming Lei
2019-01-21 4:39 ` NeilBrown
2019-01-22 15:56 ` Sasha Levin [this message]
2019-01-19 18:05 ` [PATCH 4/4] dm: fix dm_wq_work() to only use __split_and_process_bio() if appropriate Mike Snitzer
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=20190122155601.0D5FA217F5@mail.kernel.org \
--to=sashal@kernel.org \
--cc=dm-devel@redhat.com \
--cc=ming.lei@redhat.com \
--cc=neilb@suse.com \
--cc=snitzer@redhat.com \
--cc=stable@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