From: Doug Nazar <nazard@nazar.ca>
To: Ian Kent <raven@themaw.net>
Cc: Leonardo Chiquitto <leonardo.lists@gmail.com>, autofs@vger.kernel.org
Subject: Re: get_proximity() crashes on interfaces with no addresses
Date: Tue, 14 May 2013 05:15:48 -0400 [thread overview]
Message-ID: <519200C4.5050909@nazar.ca> (raw)
In-Reply-To: <1368504805.2464.13.camel@perseus.fritz.box>
On 5/14/2013 12:13 AM, Ian Kent wrote:
> Indeed that's probably good to do too. I'd be interested to hear if
> this patch functions OK with the IFF_UP check in place. In the mean
> time I'll add the patch to my queue for the next commit.
I've been running it for a day on a few boxes with no problems. The only
additional line is a logging line I had when originally testing.
May 14 04:58:47 cockatrice automount[365]: get_proximity:168:
getifaddrs: ifa_name lo, ifa_flags 0x00010049
May 14 04:58:47 cockatrice automount[365]: get_proximity:168:
getifaddrs: ifa_name eql, ifa_flags 0x00000400
May 14 04:58:47 cockatrice automount[365]: get_proximity:168:
getifaddrs: ifa_name eth0, ifa_flags 0x00011043
May 14 04:58:47 cockatrice automount[365]: get_proximity:168:
getifaddrs: ifa_name wlan0, ifa_flags 0x00001002
May 14 04:58:47 cockatrice automount[365]: get_proximity:168:
getifaddrs: ifa_name wmon0, ifa_flags 0x00011043
IFF_UP is 0x01 so that looks correct. eql was the one that it was
crashing on with no ifa_addr.
Doug
next prev parent reply other threads:[~2013-05-14 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 15:48 get_proximity() crashes on interfaces with no addresses Doug Nazar
2013-05-12 18:26 ` Leonardo Chiquitto
2013-05-12 20:31 ` Doug Nazar
2013-05-14 4:13 ` Ian Kent
2013-05-14 9:15 ` Doug Nazar [this message]
2013-05-16 0:45 ` Ian Kent
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=519200C4.5050909@nazar.ca \
--to=nazard@nazar.ca \
--cc=autofs@vger.kernel.org \
--cc=leonardo.lists@gmail.com \
--cc=raven@themaw.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.