Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7166] New: hostapd: segfault when using RT5370
Date: Wed,  4 Jun 2014 03:00:22 +0000 (UTC)	[thread overview]
Message-ID: <bug-7166-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=7166

           Summary: hostapd: segfault when using RT5370
           Product: buildroot
           Version: 2014.05
          Platform: Macintosh
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: jmavermeulen at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


hostapd crashes with segfault when using RT5370. This is because the driver
reports Beacon RX prior to hostapd having completed the AP mode setup. This bug
is reported and fixed here:
http://hostap.epitest.fi/cgit/hostap/commit/?id=334ec001bbd31c5bc83d6593e58dfbbf6b8785a2

I changed the source and version in the hostapd package to the mentioned commit
on the git repository and everything works again. I don't think however that
this is the right way of fixing this. Should I make a patch and file this or
something? At least until hostapd is updated?

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2014-06-04  3:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  3:00 bugzilla at busybox.net [this message]
2014-06-04  6:45 ` [Buildroot] [Bug 7166] hostapd: segfault when using RT5370 bugzilla at busybox.net
2014-06-04  9:11 ` bugzilla at busybox.net
2014-06-04 21:10 ` bugzilla at busybox.net
2014-06-05 20:00 ` bugzilla at busybox.net
2014-06-05 20:15 ` bugzilla at busybox.net

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=bug-7166-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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