Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 20 Aug 2015 16:26:14 +0200
From: Bastian Bittorf <>
Subject: Re: curious file access problem

* Rich Felker <> [20.08.2015 16:14]:
> > 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...

to be more exact:
'route -n' is does not see a default route (while parsing
/proc/net/route) but 'cat /proc/net/route' see's it (so the kernel is
fine). busybox is the same version (so busybox is fine).
so whats left? 8-))) at least this is something fishy.
(and i want somebody who can reproduce this e.g. on x86)

bye, bastan

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.