public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hugosantos at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/4181] New: inet6_opt_append is broken
Date: Tue, 13 Mar 2007 06:34:00 -0000	[thread overview]
Message-ID: <20070313063435.4181.hugosantos@gmail.com> (raw)

inet6_opt_append is broken and does not work with RFC 3542 supplied examples.

The problem is the following code:

  /* Now we can check whether the buffer is large enough.  */
  if (data_offset + npad + len > extlen)
    return -1;

Which should only be called if extbuf isn't NULL as any extlen is valid if
extbuf == NULL.

x = inet6_opt_init(NULL, 0);
x = inet6_opt_append(NULL, 0, x, OPT_FOO, size, align, NULL); /* should work but
fails */

-- 
           Summary: inet6_opt_append is broken
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: hugosantos at gmail dot com
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: pc-linux-gnu
  GCC host triplet: pc-linux-gnu
GCC target triplet: pc-linux-gnu


http://sourceware.org/bugzilla/show_bug.cgi?id=4181

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2007-03-13  6:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-13  6:34 hugosantos at gmail dot com [this message]
2007-03-13  6:36 ` [Bug libc/4181] " hugosantos at gmail dot com
2007-03-15 11:33 ` jakub at redhat dot com
2007-03-15 12:11 ` jakub at redhat dot com
2007-03-15 20:11 ` drepper at redhat dot com
2007-07-12 15:01 ` cvs-commit at gcc dot gnu dot org

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=20070313063435.4181.hugosantos@gmail.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).