mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Bastian Bittorf <bittorf@bluebottle.com>
To: musl@lists.openwall.com
Subject: Re: curious file access problem
Date: Thu, 20 Aug 2015 15:25:39 +0200	[thread overview]
Message-ID: <20150820132539.GO19496@medion.lan> (raw)
In-Reply-To: <55D5B21B.1010503@dd-wrt.com>

* Sebastian Gottschall <s.gottschall@dd-wrt.com> [20.08.2015 13:21]:
> >i cannot see this prob on openwrt.
> >what is your arch and your exact musl version?
> same es openwrt. but it seems to be related only to kernel 4.1 (or newer)
> in 3.18 it does not happen in openwrt

i can see it too - not on 3.18 but with kernel 4.1.5
you are right, busybox 'route -n' is affected and does not
see a default route (the same for hexdump, strings...)

e.g. this does *not* work on the affected router (ar71xx/mips):
hexdump -C /proc/net/route | grep wlan0.00000000
(empty output - but works with kernel 3.18 on the same box)

ofcourse 'ip route' is working (does not parse '/proc/net/route')

bye, bastian


  reply	other threads:[~2015-08-20 13:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20  0:44 SuperH conflict of arch/sh/__set_thread_area vs thread/__set_thread_area Christian Lamparter
2015-08-20  1:03 ` curious file access problem Sebastian Gottschall
2015-08-20  2:56   ` Rich Felker
2015-08-20  6:48   ` Bastian Bittorf
2015-08-20 10:55     ` Sebastian Gottschall
2015-08-20 13:25       ` Bastian Bittorf [this message]
2015-08-20 13:48         ` Rich Felker
2015-08-20 14:26           ` Bastian Bittorf
2015-08-20 14:32             ` Rich Felker
2015-08-20 14:51           ` Sebastian Gottschall
2015-08-20 15:00             ` Rich Felker
2015-08-20 18:30               ` Timo Teras
2015-08-20 21:03                 ` Sebastian Gottschall
2015-08-20 21:46                 ` Sebastian Gottschall
2015-08-20 14:14   ` Bastian Bittorf
2015-08-20  1:34 ` SuperH conflict of arch/sh/__set_thread_area vs thread/__set_thread_area Bobby Bingham
2015-08-20  3:04 ` Rich Felker
2015-08-20 10:21   ` Christian Lamparter
2015-08-21 14:07     ` Christian Lamparter
2015-08-21 14:23       ` Rich Felker
2015-08-25  7:48         ` Felix Fietkau

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=20150820132539.GO19496@medion.lan \
    --to=bittorf@bluebottle.com \
    --cc=musl@lists.openwall.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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).