Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Philipp Reisner <philipp.reisner@linbit.com>,
	linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	Lars Ellenberg <lars.ellenberg@linbit.com>,
	drbd-dev@lists.linbit.com
Subject: [Drbd-dev] [PATCH 7/8] drbd: interval tree: make removing an "empty" interval a no-op
Date: Fri, 13 Jan 2023 13:35:37 +0100	[thread overview]
Message-ID: <20230113123538.144276-8-christoph.boehmwalder@linbit.com> (raw)
In-Reply-To: <20230113123538.144276-1-christoph.boehmwalder@linbit.com>

From: Lars Ellenberg <lars.ellenberg@linbit.com>

Trying to remove an "empty" (just initialized, or "cleared") interval
from the tree, this results in an endless loop.

As we typically protect the tree with a spinlock_irq,
the result is a hung system.

Be nice to error cleanup code paths, ignore removal of empty intervals.

Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>
Signed-off-by: Christoph Böhmwalder <christoph.boehmwalder@linbit.com>
---
 drivers/block/drbd/drbd_interval.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/block/drbd/drbd_interval.c b/drivers/block/drbd/drbd_interval.c
index 5024ffd6143d..b6aaf0d4d85b 100644
--- a/drivers/block/drbd/drbd_interval.c
+++ b/drivers/block/drbd/drbd_interval.c
@@ -95,6 +95,10 @@ drbd_contains_interval(struct rb_root *root, sector_t sector,
 void
 drbd_remove_interval(struct rb_root *root, struct drbd_interval *this)
 {
+	/* avoid endless loop */
+	if (drbd_interval_empty(this))
+		return;
+
 	rb_erase_augmented(&this->rb, root, &augment_callbacks);
 }
 
-- 
2.38.1


  parent reply	other threads:[~2023-01-13 12:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 12:35 [Drbd-dev] [RESEND PATCH 0/8] Miscellaneous DRBD reorganization Christoph Böhmwalder
2023-01-13 12:35 ` [Drbd-dev] [PATCH 1/8] drbd: adjust drbd_limits license header Christoph Böhmwalder
2023-01-13 12:35 ` [Drbd-dev] [PATCH 2/8] drbd: fix DRBD_VOLUME_MAX 65535 -> 65534 Christoph Böhmwalder
2023-01-13 12:35 ` [Drbd-dev] [PATCH 3/8] drbd: make limits unsigned Christoph Böhmwalder
2023-01-13 12:35 ` [Drbd-dev] [PATCH 4/8] drbd: remove unnecessary assignment in vli_encode_bits Christoph Böhmwalder
2023-01-13 12:35 ` [Drbd-dev] [PATCH 5/8] drbd: remove macros using require_context Christoph Böhmwalder
2023-01-13 12:35 ` [Drbd-dev] [PATCH 6/8] MAINTAINERS: add drbd headers Christoph Böhmwalder
2023-01-13 12:35 ` Christoph Böhmwalder [this message]
2023-01-13 12:35 ` [Drbd-dev] [PATCH 8/8] drbd: drbd_insert_interval(): Clarify comment Christoph Böhmwalder
2023-01-13 20:44 ` [Drbd-dev] [RESEND PATCH 0/8] Miscellaneous DRBD reorganization Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2022-12-09 14:53 [Drbd-dev] [PATCH " Christoph Böhmwalder
2022-12-09 14:53 ` [Drbd-dev] [PATCH 7/8] drbd: interval tree: make removing an "empty" interval a no-op Christoph Böhmwalder

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=20230113123538.144276-8-christoph.boehmwalder@linbit.com \
    --to=christoph.boehmwalder@linbit.com \
    --cc=axboe@kernel.dk \
    --cc=drbd-dev@lists.linbit.com \
    --cc=lars.ellenberg@linbit.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipp.reisner@linbit.com \
    /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