Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: Cyril Bouthors <cyb@debian.org>
Cc: Igor Genibel <igor@jexiste.org>, drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [Igor Genibel] Bug#310993: reproductible segfault when parsing the config file
Date: Mon, 30 May 2005 19:15:50 +0200	[thread overview]
Message-ID: <20050530171550.GA5280@nudl> (raw)
In-Reply-To: <87oeatrume.fsf@wide.bouthors.org>

On Mon, May 30, 2005 at 11:22:17AM +0300, Cyril Bouthors wrote:
> Igor has found a bug in 0.7.10. drbdadm fails when the config file is
> bigger than 4798 bytes, which is the default:
> 
> root@wide:~# drbdadm -d adjust all
> Segmentation fault
> root@wide:~# ls -lh /etc/drbd.conf
> -rw-r--r--  1 root root 11K 2005-05-30 11:18 /etc/drbd.conf
> root@wide:~#
> 
> I've marked this Debian bug as "forwarded to upstream".  Please notice
> me when it's fixed.

thanks for the heads up,
quoting from a recent commit message:

* fixed flex input buffer overflow:
  drbdadm_scanner.fl produced tokens of arbitrary length due to excessive use
  of "+" and "*" modifiers. Now these are replaced with "{x,y}" modifiers, so
  it should no longer segfault.
  Though it may now produce parse errors where it suceeded before, if you
  happen to use 90 character long resource names or the like.


drbd-0.7.11 is about to be officially released within the next two days.
(unless we find some other stopper bug).

cheers,

: Lars Ellenberg                                  Tel +43-1-8178292-0  :
: LINBIT Information Technologies GmbH            Fax +43-1-8178292-82 :
: Schoenbrunner Str. 244, A-1120 Vienna/Europe   http://www.linbit.com :

      reply	other threads:[~2005-05-30 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30  8:22 [Drbd-dev] [Igor Genibel] Bug#310993: reproductible segfault when parsing the config file Cyril Bouthors
2005-05-30 17:15 ` Lars Ellenberg [this message]

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=20050530171550.GA5280@nudl \
    --to=lars.ellenberg@linbit.com \
    --cc=cyb@debian.org \
    --cc=drbd-dev@lists.linbit.com \
    --cc=igor@jexiste.org \
    /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