public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kduda at arastra dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug ports/4353] New: interfaces going away crashes sudo with SIGABRT in ifaddr stuff
Date: Fri, 13 Apr 2007 06:24:00 -0000	[thread overview]
Message-ID: <20070413072354.4353.kduda@arastra.com> (raw)

If you run "sudo true" over and over, while in the background you create and
delete tap interfaces as fast as you can, sudo will crash about 30% of the time
with SIGABRT.  This is on a Linux-x86-fc6 system, glibc 2.5-10.fc6.  I assume it
is crashing somewhere in sysdeps/unix/sysv/linux/ifaddrs.c but it is a little
hard to tell because I can't convince sudo (being setuid) to leave a core file.

Sorry this isn't really very well isolated and the reproduction path isn't
really that specific.

-- 
           Summary: interfaces going away crashes sudo with SIGABRT in
                    ifaddr stuff
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ports
        AssignedTo: roland at gnu dot org
        ReportedBy: kduda at arastra dot com
                CC: glibc-bugs at sources dot redhat dot com


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

------- 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-04-13  6:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13  6:24 kduda at arastra dot com [this message]
2007-04-13 18:46 ` [Bug ports/4353] " jakub at redhat dot com
2007-04-13 20:10 ` kduda at arastra dot com

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=20070413072354.4353.kduda@arastra.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).