All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-announce@lists.linbit.com
Subject: [DRBD-announce] drbd-0.7.18.tar.gz
Date: Wed, 26 Apr 2006 15:00:12 +0200	[thread overview]
Message-ID: <200604261500.13036.philipp.reisner@linbit.com> (raw)

Although drbd-8.0preX comes along nicely, we also maintain drbd-0.7...

0.7.18 (api:78/proto:74)
-----
 * Under high memory pressure it was possible to hit a deadlock 
   on a kmalloc(). Changed the GFP mask, it is no longer possible to
   deadlock it with memory pressure.
 * With very unlucky network timing during connect DRBD falls into 
   a connect / drop-connection loop, that as soon as DRBD is in this 
   loop is very stable. This is fixed now, DRBD detects this situation
   an breaks out of it.
 * Fix to the init-script. Now it waits until udev has created
   the device nodes of _all_ resources.
 * A small fix for the 32bit userland 64bit kernel people, running
   older kernels.
 * Improved handling of IO errors during initial read in of the
   activity log.

Nothing ground shaking but gets the latest bug fixes out of SVN
into an official release.

http://oss.linbit.com/drbd/0.7/drbd-0.7.18.tar.gz
http://svn.drbd.org/drbd/tags/drbd-0.7.18/
http://www.linbit.com/support/drbd-0.7.18/

-philipp
-- 
: Dipl-Ing Philipp Reisner                      Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH          Fax +43-1-8178292-82 :
: Schönbrunnerstr 244, 1120 Vienna, Austria    http://www.linbit.com :

                 reply	other threads:[~2006-04-26 12:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200604261500.13036.philipp.reisner@linbit.com \
    --to=philipp.reisner@linbit.com \
    --cc=drbd-announce@lists.linbit.com \
    --cc=drbd-user@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.