From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Cc: Dave Jiang <djiang@mvista.com>
Subject: Re: [Drbd-dev] drbdadm segfaults with incorrect drbd.conf
Date: Wed, 20 Jun 2007 19:32:29 +0200 [thread overview]
Message-ID: <200706201932.29361.philipp.reisner@linbit.com> (raw)
In-Reply-To: <467956FB.5060507@mvista.com>
On Wednesday 20 June 2007 18:34:03 Dave Jiang wrote:
> It seems that when the resources aren't setup exactly right in drbd.conf
> drbdadm can segfault due to using a pointer that is NULL. Attached is a
> patch that fixes the issue.
Could you provide such an drbd.conf file as well, so that we can see
the issue, that gets fixed by the patch ?
Thanks!
-Phil
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria http://www.linbit.com :
next prev parent reply other threads:[~2007-06-20 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 16:34 [Drbd-dev] drbdadm segfaults with incorrect drbd.conf Dave Jiang
2007-06-20 17:32 ` Philipp Reisner [this message]
[not found] ` <46796D1E.5090105@mvista.com>
2007-06-25 14:07 ` Philipp Reisner
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=200706201932.29361.philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=djiang@mvista.com \
--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