From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/8346 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: curious file access problem Date: Thu, 20 Aug 2015 10:32:21 -0400 Message-ID: <20150820143221.GV32742@brightrain.aerifal.cx> References: <5769061.FLTLqujSyv@debian64> <55D5274D.2020903@dd-wrt.com> <20150820064804.GM19496@medion.lan> <55D5B21B.1010503@dd-wrt.com> <20150820132539.GO19496@medion.lan> <20150820134834.GU32742@brightrain.aerifal.cx> <20150820142614.GR19496@medion.lan> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1440081164 30592 80.91.229.3 (20 Aug 2015 14:32:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Aug 2015 14:32:44 +0000 (UTC) Cc: musl@lists.openwall.com To: Bastian Bittorf Original-X-From: musl-return-8358-gllmg-musl=m.gmane.org@lists.openwall.com Thu Aug 20 16:32:43 2015 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1ZSQtR-0007Jf-D6 for gllmg-musl@m.gmane.org; Thu, 20 Aug 2015 16:32:37 +0200 Original-Received: (qmail 31763 invoked by uid 550); 20 Aug 2015 14:32:35 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 30717 invoked from network); 20 Aug 2015 14:32:35 -0000 Content-Disposition: inline In-Reply-To: <20150820142614.GR19496@medion.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:8346 Archived-At: On Thu, Aug 20, 2015 at 04:26:14PM +0200, Bastian Bittorf wrote: > * 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). That doesn't follow. This is almost certainly a kernel bug where different sequences of read syscalls see different contents in the /proc-bsed pseudo-file due to some sort of state corruption or other bug in the 'file position' state the kernel keeps for it. Stuff like this has happened before in /proc and it wouldn't surprise me at all if someone broke it again. Rich