From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: Timo Teras <timo.teras@iki.fi>, Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: curious file access problem
Date: Thu, 20 Aug 2015 23:03:48 +0200 [thread overview]
Message-ID: <55D640B4.7090201@dd-wrt.com> (raw)
In-Reply-To: <20150820213039.25089e69@vostro>
Am 20.08.2015 um 20:30 schrieb Timo Teras:
> On Thu, 20 Aug 2015 11:00:20 -0400
> Rich Felker <dalias@libc.org> wrote:
>
>> On Thu, Aug 20, 2015 at 04:51:56PM +0200, Sebastian Gottschall wrote:
>>> 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@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...)
>>>> 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?
>> Again, if the bug is in the kernel's tracking of the pseudo-file
>> position state (which seems clear now), then whether it manifests or
>> not is almost certainly a matter of _how_ the reading takes place
>> (small chunks, big chunks, read vs readv vs pread, whether or not
>> seeking is involved, etc.). And this is going to vary between
>> applications, and if stdio is used by the application to perform the
>> reading, then it's also going to vary between stdio implementations
>> (and thus libcs).
> DaveM's net -stable queue has:
> http://patchwork.ozlabs.org/patch/507167/
>
> Sounds like this is the fix for a kernel regression.
>
> /Timo
>
absolutelly. i will try it and give feedback
next prev parent reply other threads:[~2015-08-20 21:03 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
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 [this message]
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=55D640B4.7090201@dd-wrt.com \
--to=s.gottschall@dd-wrt.com \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=timo.teras@iki.fi \
/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).