]> git.ipfire.org Git - thirdparty/kernel/stable-queue.git/commitdiff
drop broken dm patch from 3.18, 4.4, and 4.9 queues.
authorGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 15 Apr 2019 16:55:26 +0000 (18:55 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 15 Apr 2019 16:55:26 +0000 (18:55 +0200)
queue-3.18/dm-table-propagate-bdi_cap_stable_writes-to-fix-sporadic-checksum-errors.patch [deleted file]
queue-3.18/series
queue-4.4/dm-table-propagate-bdi_cap_stable_writes-to-fix-sporadic-checksum-errors.patch [deleted file]
queue-4.4/series
queue-4.9/dm-table-propagate-bdi_cap_stable_writes-to-fix-sporadic-checksum-errors.patch [deleted file]
queue-4.9/series

diff --git a/queue-3.18/dm-table-propagate-bdi_cap_stable_writes-to-fix-sporadic-checksum-errors.patch b/queue-3.18/dm-table-propagate-bdi_cap_stable_writes-to-fix-sporadic-checksum-errors.patch
deleted file mode 100644 (file)
index ac765ab..0000000
+++ /dev/null
@@ -1,80 +0,0 @@
-From eb40c0acdc342b815d4d03ae6abb09e80c0f2988 Mon Sep 17 00:00:00 2001
-From: Ilya Dryomov <idryomov@gmail.com>
-Date: Tue, 26 Mar 2019 20:20:58 +0100
-Subject: dm table: propagate BDI_CAP_STABLE_WRITES to fix sporadic checksum errors
-
-From: Ilya Dryomov <idryomov@gmail.com>
-
-commit eb40c0acdc342b815d4d03ae6abb09e80c0f2988 upstream.
-
-Some devices don't use blk_integrity but still want stable pages
-because they do their own checksumming.  Examples include rbd and iSCSI
-when data digests are negotiated.  Stacking DM (and thus LVM) on top of
-these devices results in sporadic checksum errors.
-
-Set BDI_CAP_STABLE_WRITES if any underlying device has it set.
-
-Cc: stable@vger.kernel.org
-Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
-Signed-off-by: Mike Snitzer <snitzer@redhat.com>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
----
- drivers/md/dm-table.c |   39 +++++++++++++++++++++++++++++++++++++++
- 1 file changed, 39 insertions(+)
-
---- a/drivers/md/dm-table.c
-+++ b/drivers/md/dm-table.c
-@@ -1435,6 +1435,36 @@ static bool dm_table_supports_discards(s
-       return 0;
- }
-+static int device_requires_stable_pages(struct dm_target *ti,
-+                                      struct dm_dev *dev, sector_t start,
-+                                      sector_t len, void *data)
-+{
-+      struct request_queue *q = bdev_get_queue(dev->bdev);
-+
-+      return q && bdi_cap_stable_pages_required(q->backing_dev_info);
-+}
-+
-+/*
-+ * If any underlying device requires stable pages, a table must require
-+ * them as well.  Only targets that support iterate_devices are considered:
-+ * don't want error, zero, etc to require stable pages.
-+ */
-+static bool dm_table_requires_stable_pages(struct dm_table *t)
-+{
-+      struct dm_target *ti;
-+      unsigned i;
-+
-+      for (i = 0; i < dm_table_get_num_targets(t); i++) {
-+              ti = dm_table_get_target(t, i);
-+
-+              if (ti->type->iterate_devices &&
-+                  ti->type->iterate_devices(ti, device_requires_stable_pages, NULL))
-+                      return true;
-+      }
-+
-+      return false;
-+}
-+
- void dm_table_set_restrictions(struct dm_table *t, struct request_queue *q,
-                              struct queue_limits *limits)
- {
-@@ -1486,6 +1516,15 @@ void dm_table_set_restrictions(struct dm
-               queue_flag_clear_unlocked(QUEUE_FLAG_ADD_RANDOM, q);
-       /*
-+       * Some devices don't use blk_integrity but still want stable pages
-+       * because they do their own checksumming.
-+       */
-+      if (dm_table_requires_stable_pages(t))
-+              q->backing_dev_info->capabilities |= BDI_CAP_STABLE_WRITES;
-+      else
-+              q->backing_dev_info->capabilities &= ~BDI_CAP_STABLE_WRITES;
-+
-+      /*
-        * QUEUE_FLAG_STACKABLE must be set after all queue settings are
-        * visible to other CPUs because, once the flag is set, incoming bios
-        * are processed by request-based dm, which refers to the queue
index 359aaa4702c1a468191215e54d0d5434f80147ee..1f69af5afae514d277fc72f4c20879fe45e84f2a 100644 (file)
@@ -57,4 +57,3 @@ xen-prevent-buffer-overflow-in-privcmd-ioctl.patch
 sched-fair-do-not-re-read-h_load_next-during-hierarchical-load-calculation.patch
 xtensa-fix-return_address.patch
 pci-add-function-1-dma-alias-quirk-for-marvell-9170-sata-controller.patch
-dm-table-propagate-bdi_cap_stable_writes-to-fix-sporadic-checksum-errors.patch
diff --git a/queue-4.4/dm-table-propagate-bdi_cap_stable_writes-to-fix-sporadic-checksum-errors.patch b/queue-4.4/dm-table-propagate-bdi_cap_stable_writes-to-fix-sporadic-checksum-errors.patch
deleted file mode 100644 (file)
index 6b7ee07..0000000
+++ /dev/null
@@ -1,80 +0,0 @@
-From eb40c0acdc342b815d4d03ae6abb09e80c0f2988 Mon Sep 17 00:00:00 2001
-From: Ilya Dryomov <idryomov@gmail.com>
-Date: Tue, 26 Mar 2019 20:20:58 +0100
-Subject: dm table: propagate BDI_CAP_STABLE_WRITES to fix sporadic checksum errors
-
-From: Ilya Dryomov <idryomov@gmail.com>
-
-commit eb40c0acdc342b815d4d03ae6abb09e80c0f2988 upstream.
-
-Some devices don't use blk_integrity but still want stable pages
-because they do their own checksumming.  Examples include rbd and iSCSI
-when data digests are negotiated.  Stacking DM (and thus LVM) on top of
-these devices results in sporadic checksum errors.
-
-Set BDI_CAP_STABLE_WRITES if any underlying device has it set.
-
-Cc: stable@vger.kernel.org
-Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
-Signed-off-by: Mike Snitzer <snitzer@redhat.com>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
----
- drivers/md/dm-table.c |   39 +++++++++++++++++++++++++++++++++++++++
- 1 file changed, 39 insertions(+)
-
---- a/drivers/md/dm-table.c
-+++ b/drivers/md/dm-table.c
-@@ -1479,6 +1479,36 @@ static bool dm_table_supports_discards(s
-       return false;
- }
-+static int device_requires_stable_pages(struct dm_target *ti,
-+                                      struct dm_dev *dev, sector_t start,
-+                                      sector_t len, void *data)
-+{
-+      struct request_queue *q = bdev_get_queue(dev->bdev);
-+
-+      return q && bdi_cap_stable_pages_required(q->backing_dev_info);
-+}
-+
-+/*
-+ * If any underlying device requires stable pages, a table must require
-+ * them as well.  Only targets that support iterate_devices are considered:
-+ * don't want error, zero, etc to require stable pages.
-+ */
-+static bool dm_table_requires_stable_pages(struct dm_table *t)
-+{
-+      struct dm_target *ti;
-+      unsigned i;
-+
-+      for (i = 0; i < dm_table_get_num_targets(t); i++) {
-+              ti = dm_table_get_target(t, i);
-+
-+              if (ti->type->iterate_devices &&
-+                  ti->type->iterate_devices(ti, device_requires_stable_pages, NULL))
-+                      return true;
-+      }
-+
-+      return false;
-+}
-+
- void dm_table_set_restrictions(struct dm_table *t, struct request_queue *q,
-                              struct queue_limits *limits)
- {
-@@ -1521,6 +1551,15 @@ void dm_table_set_restrictions(struct dm
-       dm_table_verify_integrity(t);
-       /*
-+       * Some devices don't use blk_integrity but still want stable pages
-+       * because they do their own checksumming.
-+       */
-+      if (dm_table_requires_stable_pages(t))
-+              q->backing_dev_info->capabilities |= BDI_CAP_STABLE_WRITES;
-+      else
-+              q->backing_dev_info->capabilities &= ~BDI_CAP_STABLE_WRITES;
-+
-+      /*
-        * Determine whether or not this queue's I/O timings contribute
-        * to the entropy pool, Only request-based targets use this.
-        * Clear QUEUE_FLAG_ADD_RANDOM if any underlying device does not
index b6f3c54034d88517d74c631aa4cc0fa2c5f9c4d5..ee6d2476aee4de3038bc37391253003dc36e72f8 100644 (file)
@@ -95,4 +95,3 @@ xen-prevent-buffer-overflow-in-privcmd-ioctl.patch
 sched-fair-do-not-re-read-h_load_next-during-hierarchical-load-calculation.patch
 xtensa-fix-return_address.patch
 pci-add-function-1-dma-alias-quirk-for-marvell-9170-sata-controller.patch
-dm-table-propagate-bdi_cap_stable_writes-to-fix-sporadic-checksum-errors.patch
diff --git a/queue-4.9/dm-table-propagate-bdi_cap_stable_writes-to-fix-sporadic-checksum-errors.patch b/queue-4.9/dm-table-propagate-bdi_cap_stable_writes-to-fix-sporadic-checksum-errors.patch
deleted file mode 100644 (file)
index ab0fd9d..0000000
+++ /dev/null
@@ -1,80 +0,0 @@
-From eb40c0acdc342b815d4d03ae6abb09e80c0f2988 Mon Sep 17 00:00:00 2001
-From: Ilya Dryomov <idryomov@gmail.com>
-Date: Tue, 26 Mar 2019 20:20:58 +0100
-Subject: dm table: propagate BDI_CAP_STABLE_WRITES to fix sporadic checksum errors
-
-From: Ilya Dryomov <idryomov@gmail.com>
-
-commit eb40c0acdc342b815d4d03ae6abb09e80c0f2988 upstream.
-
-Some devices don't use blk_integrity but still want stable pages
-because they do their own checksumming.  Examples include rbd and iSCSI
-when data digests are negotiated.  Stacking DM (and thus LVM) on top of
-these devices results in sporadic checksum errors.
-
-Set BDI_CAP_STABLE_WRITES if any underlying device has it set.
-
-Cc: stable@vger.kernel.org
-Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
-Signed-off-by: Mike Snitzer <snitzer@redhat.com>
-Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
----
- drivers/md/dm-table.c |   39 +++++++++++++++++++++++++++++++++++++++
- 1 file changed, 39 insertions(+)
-
---- a/drivers/md/dm-table.c
-+++ b/drivers/md/dm-table.c
-@@ -1575,6 +1575,36 @@ static bool dm_table_supports_discards(s
-       return false;
- }
-+static int device_requires_stable_pages(struct dm_target *ti,
-+                                      struct dm_dev *dev, sector_t start,
-+                                      sector_t len, void *data)
-+{
-+      struct request_queue *q = bdev_get_queue(dev->bdev);
-+
-+      return q && bdi_cap_stable_pages_required(q->backing_dev_info);
-+}
-+
-+/*
-+ * If any underlying device requires stable pages, a table must require
-+ * them as well.  Only targets that support iterate_devices are considered:
-+ * don't want error, zero, etc to require stable pages.
-+ */
-+static bool dm_table_requires_stable_pages(struct dm_table *t)
-+{
-+      struct dm_target *ti;
-+      unsigned i;
-+
-+      for (i = 0; i < dm_table_get_num_targets(t); i++) {
-+              ti = dm_table_get_target(t, i);
-+
-+              if (ti->type->iterate_devices &&
-+                  ti->type->iterate_devices(ti, device_requires_stable_pages, NULL))
-+                      return true;
-+      }
-+
-+      return false;
-+}
-+
- void dm_table_set_restrictions(struct dm_table *t, struct request_queue *q,
-                              struct queue_limits *limits)
- {
-@@ -1617,6 +1647,15 @@ void dm_table_set_restrictions(struct dm
-       dm_table_verify_integrity(t);
-       /*
-+       * Some devices don't use blk_integrity but still want stable pages
-+       * because they do their own checksumming.
-+       */
-+      if (dm_table_requires_stable_pages(t))
-+              q->backing_dev_info->capabilities |= BDI_CAP_STABLE_WRITES;
-+      else
-+              q->backing_dev_info->capabilities &= ~BDI_CAP_STABLE_WRITES;
-+
-+      /*
-        * Determine whether or not this queue's I/O timings contribute
-        * to the entropy pool, Only request-based targets use this.
-        * Clear QUEUE_FLAG_ADD_RANDOM if any underlying device does not
index fdc60f4a96810405def293a2d6947f1499040f66..77e5175467a1eaae009ebe0fc0c9304229c0a21c 100644 (file)
@@ -74,4 +74,3 @@ xen-prevent-buffer-overflow-in-privcmd-ioctl.patch
 sched-fair-do-not-re-read-h_load_next-during-hierarchical-load-calculation.patch
 xtensa-fix-return_address.patch
 pci-add-function-1-dma-alias-quirk-for-marvell-9170-sata-controller.patch
-dm-table-propagate-bdi_cap_stable_writes-to-fix-sporadic-checksum-errors.patch