From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org,
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, stable@vger.kernel.org,
Cc: stable@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>
Cc: Alasdair Kergon <agk@redhat.com>
Cc: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] dm: give req_size precisely given by user
Date: Tue, 18 Dec 2018 23:47:59 +0000 [thread overview]
Message-ID: <20181218234800.1587C218A2@mail.kernel.org> (raw)
In-Reply-To: <20181218172537.12300-1-jaegeuk@kernel.org>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 9491ae4aade6 mm: don't cap request size based on read-ahead setting.
The bot has tested the following trees: v4.19.10, v4.14.89,
v4.19.10: Failed to apply! Possible dependencies:
5f832a395859 ("scsi: sd_zbc: Fix sd_zbc_check_zones() error checks")
a2d6b3a2d390 ("block: Improve zone reset execution")
a91e138022bc ("block: Introduce blkdev_nr_zones() helper")
bf5054569653 ("block: Introduce blk_revalidate_disk_zones()")
d2e428e49eec ("scsi: sd_zbc: Reduce boot device scan and revalidate time")
e76239a3748c ("block: add a report_zones method")
v4.14.89: Failed to apply! Possible dependencies:
08e18eab0c57 ("block: add bi_blkg to the bio for cgroups")
30e5e929c7bf ("nvme: don't pass struct nvme_ns to nvme_config_discard")
5238dcf4136f ("block: replace bio->bi_issue_stat with bio-specific type")
53cfdc10a95d ("blk-throttle: fix null pointer dereference while throttling writeback IOs")
5d47c89f29ea ("dm: clear all discard attributes in queue_limits when discards are disabled")
8b904b5b6b58 ("block: Use blk_queue_flag_*() in drivers instead of queue_flag_*()")
a2d6b3a2d390 ("block: Improve zone reset execution")
b889bf66d001 ("blk-throttle: track read and write request individually")
bf5054569653 ("block: Introduce blk_revalidate_disk_zones()")
c8b5fd031a30 ("mmc: block: Factor out mmc_setup_queue()")
d70675121546 ("block: introduce blk-iolatency io controller")
e447a0151f7c ("zram: set BDI_CAP_STABLE_WRITES once")
ed754e5deeb1 ("nvme: track shared namespaces")
How should we proceed with this patch?
--
Thanks,
Sasha
prev parent reply other threads:[~2018-12-18 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 17:25 [PATCH] dm: give req_size precisely given by user Jaegeuk Kim
2018-12-18 17:45 ` Jens Axboe
2018-12-18 19:47 ` Mike Snitzer
2018-12-18 21:40 ` Jaegeuk Kim
2018-12-18 23:47 ` 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=20181218234800.1587C218A2@mail.kernel.org \
--to=sashal@kernel.org \
--cc=jaegeuk@kernel.org \
--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).