From: Holger Freyther <holger@freyther.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: kernel miscompilation with gcc 4.8 for ARMv5
Date: Fri, 19 Jul 2013 05:39:33 +0000 (UTC) [thread overview]
Message-ID: <loom.20130719T072922-639@post.gmane.org> (raw)
In-Reply-To: ly4nc2twyk.fsf@ensc-virt.intern.sigma-chemnitz.de
Enrico Scholz <enrico.scholz@...> writes:
Good Morning,
> Applying two upstream kernel commits
> 455bd4c430b0c0a361f38e8658a0d6cb469942b5 (ARM: 7668/1: fix
> memset-related crashes caused by recent GCC (4.7.2) optimizations) and
> 418df63adac56841ef6b0f1fcf435bc64d4ed177 (ARM: 7670/1: fix the memset
> fix) seem to fix the problem for me.
I am in a similar situation with ARMv5. My 3.2.48 kernel randomly
crashed inside namei.c:do_lookup when de-referencing a bogus address
and after upgrading to 3.4.53 I do see crashes in the tcpv4 receive
path. Compiling my kernel with GCC 4.6.3 appears to produce a working
one. The output of the oops can be seen here[1], from what I see
I am entering this path[2] and besides the
if (sk2) {
sk = sk2;
goto process;
}
...
process:
if (sk->sk_state == TCP_TIME_WAIT)
goto do_time_wait;
...
will crash on the above line. Compiling tcp_ipv4.c with GCC4.6.3
and re-linking doesn't appear to fix the problem but maybe I made
another mistake.
Do you guys have an idea on how to proceed?
[1] http://paste.lisp.org/display/138095
[2]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/net/ipv
4/tcp_ipv4.c?id=v3.4#n1833
next prev parent reply other threads:[~2013-07-19 5:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 11:36 kernel miscompilation with gcc 4.8 for ARMv5 Enrico Scholz
2013-07-10 12:34 ` Enrico Scholz
2013-07-10 13:15 ` Mike Looijmans
2013-07-10 13:25 ` Mark Hatle
2013-07-11 5:38 ` Mike Looijmans
2013-07-10 13:57 ` Bruce Ashfield
2013-07-10 14:30 ` Enrico Scholz
2013-07-10 16:35 ` Bruce Ashfield
2013-07-14 4:58 ` Bruce Ashfield
2013-07-19 5:39 ` Holger Freyther [this message]
2013-07-19 11:24 ` Phil Blundell
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=loom.20130719T072922-639@post.gmane.org \
--to=holger@freyther.de \
--cc=openembedded-core@lists.openembedded.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox