From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Ming Lei <ming.lei@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>, dm-devel@redhat.com
Cc: Ming Lei <ming.lei@redhat.com>, stable@vger.kernel.org
Cc: <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] dm-raid: fix updating of max_discard_sectors limit
Date: Thu, 12 Sep 2019 07:30:41 +0000 [thread overview]
Message-ID: <20190912073042.AD65A2075C@mail.kernel.org> (raw)
In-Reply-To: <20190911111249.19772-1-ming.lei@redhat.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.2.14, v4.19.72, v4.14.143, v4.9.192, v4.4.192.
v5.2.14: Build OK!
v4.19.72: Failed to apply! Possible dependencies:
53b471687012 ("dm: remove indirect calls from __send_changing_extent_only()")
61697a6abd24 ("dm: eliminate 'split_discard_bios' flag from DM target interface")
v4.14.143: Failed to apply! Possible dependencies:
00716545c894 ("dm: add support for secure erase forwarding")
0519c71e8d46 ("dm: backfill abnormal IO support to non-splitting IO submission")
0776aa0e30aa ("dm: ensure bio-based DM's bioset and io_pool support targets' maximum IOs")
18a25da84354 ("dm: ensure bio submission follows a depth-first tree walk")
318716ddea08 ("dm: safely allocate multiple bioset bios")
3d7f45625a84 ("dm: fix __send_changing_extent_only() to send first bio and chain remainder")
53b471687012 ("dm: remove indirect calls from __send_changing_extent_only()")
552aa679f265 ("dm raid: use rs_is_raid*()")
61697a6abd24 ("dm: eliminate 'split_discard_bios' flag from DM target interface")
64f52b0e3148 ("dm: improve performance by moving dm_io structure to per-bio-data")
745dc570b2c3 ("dm: rename 'bio' member of dm_io structure to 'orig_bio'")
978e51ba38e0 ("dm: optimize bio-based NVMe IO submission")
f31c21e4365c ("dm: remove unused 'num_write_bios' target interface")
v4.9.192: Failed to apply! Possible dependencies:
124d6db07c3b ("nbd: use our own workqueue for recv threads")
19372e276917 ("loop: implement REQ_OP_WRITE_ZEROES")
3b1a94c88b79 ("dm zoned: drive-managed zoned block device target")
48920ff2a5a9 ("block: remove the discard_zeroes_data flag")
552aa679f265 ("dm raid: use rs_is_raid*()")
61697a6abd24 ("dm: eliminate 'split_discard_bios' flag from DM target interface")
7ab84db64f11 ("dm integrity: improve the Kconfig help text for DM_INTEGRITY")
9561a7ade0c2 ("nbd: add multi-connection support")
b0d9111a2d53 ("nbd: use an idr to keep track of nbd devices")
v4.4.192: Failed to apply! Possible dependencies:
33e53f06850f ("dm raid: introduce extended superblock and new raid types to support takeover/reshaping")
4c9971ca6a17 ("dm raid: make sure no feature flags are set in metadata")
552aa679f265 ("dm raid: use rs_is_raid*()")
61697a6abd24 ("dm: eliminate 'split_discard_bios' flag from DM target interface")
676fa5ad6e96 ("dm raid: use rt_is_raid*() in all appropriate checks")
702108d194e3 ("dm raid: cleanup / provide infrastructure")
73c6f239a862 ("dm raid: rename variable 'ret' to 'r' to conform to other dm code")
92c83d79b07e ("dm raid: use dm_arg_set API in constructor")
f090279eaff8 ("dm raid: check constructor arguments for invalid raid level/argument combinations")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
prev parent reply other threads:[~2019-09-12 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 11:12 [PATCH] dm-raid: fix updating of max_discard_sectors limit Ming Lei
2019-09-12 7:30 ` Sasha Levin [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=20190912073042.AD65A2075C@mail.kernel.org \
--to=sashal@kernel.org \
--cc=ming.lei@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;
as well as URLs for NNTP newsgroup(s).