[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55D5E98C.1030406@dd-wrt.com>
Date: Thu, 20 Aug 2015 16:51:56 +0200
From: Sebastian Gottschall <s.gottschall@...wrt.com>
To: musl@...ts.openwall.com
Subject: Re: curious file access problem
Am 20.08.2015 um 15:48 schrieb Rich Felker:
> On Thu, Aug 20, 2015 at 03:25:39PM +0200, Bastian Bittorf wrote:
>> * Sebastian Gottschall <s.gottschall@...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...)
> In that case, it sounds like somebody broke the kernel. This is rather
> unfortunate, and it would be great if someone could look into the bug
> and get it fixed before these broken kernels are too widespread...
there are some fib tree enhancements. i nailed it down to a patchset
which i can apply and revert to let the problem show up
the interesting thing is that uclibc doesnt show that behaviour. but i
dont know why. maybe its some sort of application based routing table?
>
> Rich
>
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
