Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: "Graham, Simon" <Simon.Graham@stratus.com>
Cc: drbd-dev@lists.linbit.com, Valentin Vidic <Valentin.Vidic@carnet.hr>
Subject: [Drbd-dev] Xen - DRBD issue / panic in skb_copy_bits
Date: Fri, 12 Jun 2009 11:38:55 +0200	[thread overview]
Message-ID: <200906121138.55945.philipp.reisner@linbit.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 880 bytes --]

Hi Simon,

As we are currently preparing the next DRBD release, we try to
fix known issues...

I tried to reproduce, trigger the issue you described in that post:
http://lists.linbit.com/pipermail/drbd-user/2009-March/011645.html
I failed to reproduce it, probably because I tried with 
instrumented DRBD code on a recent vanilla kernel.

Howerver, attached is the patch that is intended to fix the issue.
Can you verify that it really fixes the issue?

  I thought, you have the right test environment (with Xen) around, 
  and it is probably only a little effort for you to do so.) 
  Currently I do not have Xen boxes in our testing environment 

Thanks!
 Philipp
-- 
: Dipl-Ing Philipp Reisner
: LINBIT | Your Way to High Availability
: Tel: +43-1-8178292-50, Fax: +43-1-8178292-82
: http://www.linbit.com

DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria.


[-- Attachment #2: xen-issue-fix.diff --]
[-- Type: text/x-patch, Size: 1360 bytes --]

diff --git a/drbd/drbd_main.c b/drbd/drbd_main.c
index 1a1c4f6..719a5fe 100644
--- a/drbd/drbd_receiver.c
+++ b/drbd/drbd_receiver.c
@@ -357,7 +357,7 @@ int drbd_release_ee(struct drbd_conf *mdev, struct list_head *list)
 }
 
 
-STATIC void reclaim_net_ee(struct drbd_conf *mdev)
+STATIC enum { RN_EMPTY, RN_NOT_EMPTY } reclaim_net_ee(struct drbd_conf *mdev)
 {
 	struct drbd_epoch_entry *e;
 	struct list_head *le, *tle;
@@ -370,10 +370,12 @@ STATIC void reclaim_net_ee(struct drbd_conf *mdev)
 	list_for_each_safe(le, tle, &mdev->net_ee) {
 		e = list_entry(le, struct drbd_epoch_entry, w.list);
 		if (drbd_bio_has_active_page(e->private_bio))
-			break;
+			return RN_NOT_EMPTY;
 		list_del(le);
 		drbd_free_ee(mdev, e);
 	}
+
+	return RN_EMPTY;
 }
 
 
@@ -3552,7 +3554,13 @@ STATIC void drbd_disconnect(struct drbd_conf *mdev)
 	_drbd_wait_ee_list_empty(mdev, &mdev->sync_ee);
 	_drbd_clear_done_ee(mdev);
 	_drbd_wait_ee_list_empty(mdev, &mdev->read_ee);
-	reclaim_net_ee(mdev);
+	while (reclaim_net_ee(mdev) == RN_NOT_EMPTY) {
+		spin_unlock_irq(&mdev->req_lock);
+		dev_info(DEV, "Waiting for TCP to finally give up all page references\n");
+		__set_current_state(TASK_INTERRUPTIBLE);
+		schedule_timeout(HZ / 10);
+		spin_lock_irq(&mdev->req_lock);
+	}
 	spin_unlock_irq(&mdev->req_lock);
 
 	/* We do not have data structures that would allow us to

             reply	other threads:[~2009-06-12  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  9:38 Philipp Reisner [this message]
2009-06-14  3:58 ` [Drbd-dev] possible FIX [Xen - DRBD issue / panic in skb_copy_bits] Lars Ellenberg
2009-06-15 11:58   ` Valentin Vidic
2009-06-23  8:01     ` Valentin Vidic

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=200906121138.55945.philipp.reisner@linbit.com \
    --to=philipp.reisner@linbit.com \
    --cc=Simon.Graham@stratus.com \
    --cc=Valentin.Vidic@carnet.hr \
    --cc=drbd-dev@lists.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