From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: linux-arm-kernel@lists.arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org, rpurdie@rpsys.net
Subject: [ARM] Corrupted .got section with 2.6.18 and JFFS2 (solved)
Date: Fri, 03 Nov 2006 11:09:35 +0100 [thread overview]
Message-ID: <lywt6cc04g.fsf_-_@ensc-pc.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <1162497112.12781.51.camel@localhost.localdomain> (Richard Purdie's message of "Thu, 02 Nov 2006 19:51:51 +0000")
[-- Attachment #1: Type: text/plain, Size: 3775 bytes --]
[CC lkml; original issue at
http://article.gmane.org/gmane.linux.ports.arm.kernel/28068]
rpurdie@rpsys.net (Richard Purdie) writes:
>> > I have a problem with JFFS2 filesystem and kernel 2.6.18. When
>> > starting a program which uses a certain library (libutil.so.1 in
>> > my case), the .got section of the library can be initialized
>> > wrongly when the used memory is uninitialized.
>>
>> Problem seems to be caused by
>>
>> | [PATCH] zlib_inflate: Upgrade library code to a recent version
>>
>> (4f3865fb57a04db7cca068fed1c15badc064a302)
>>
>> After reverting this (and related patches), things seem to work.
>>
>> I don't have an idea yet, which changes in this complex patch are
>> really responsible....
>
> I'm the author of the above change. I just ran your test program
> on a device (ARM PXA255 with 2.6.19-rc4 kernel, 2.3.5ish glibc,
> gcc 3.4.4, libraries on jffs2) and I can't reproduce the
> problem.
I can reproduce it 100% with:
$ git checkout -b test v2.6.17.14
$ git-am -3 tmp/000[1-8]*
(see https://www.cvg.de/people/ensc/libutil/ for patches and
used .config (config.txt); the physmap patches are from 2.6.18)
$ make tftp
--> 'fillmem ; test' sequences work without errors
$ git-cherry-pick 4f3865fb57a04db7cca068fed1c15badc064a302
$ make tftp
--> 'fillmem ; test' sequences stop with a segfault
I compiled kernel both with gcc-3.4.6 and gcc-4.1.1 and got same
results.
Same results when using recent 2.6.18.1 kernel and reverting all
patches which modified lib/zlib_*.
I see segfaults too with 2.6.19-rc4 but did not checked yet
whether removal of zlib patch solved them.
Things are getting yet more strange when using the glibc-2.5
dynamic loader:
| # ... copying ld-2.5.so and libc-2.5.so ...
| # LD_LIBRARY_PATH=`pwd` ./ld-2.5.so /bin/test2
| Inconsistency detected by ld.so: dynamic-link.h: 169: elf_get_dynamic_info: Assertion `info[19]->d_un.d_val == sizeof (Elf32_Rel)' failed!
| # LD_LIBRARY_PATH=`pwd` ./ld-2.5.so /bin/test2
| Segmentation fault
| # LD_LIBRARY_PATH=`pwd` ./ld-2.5.so /bin/test2
| #
> You mentioned elsewhere that reading the lib from flash gives
> consistent md5sums. There is only one inflation code path and
> if the md5sum is always consistent, I can't see how the the
> inflation code is at fault. I therefore strongly suspect this
> is some userspace issue when handling the got.
Issue:
* seems to be triggered by the zlib kernel patch
* seems to be triggered by my 'libutil.so' (I can not see it with
other libraries)
* can be reproduced on two different PXA270 platforms (same
userspace, but different module vendors and different memory
timing setups)
I see the following reasons:
* new zlib code has sideeffects (overflows?)
* new zlib code is so fast that it triggers a race somewhere else
* libutil.so's .init section is buggy (likely, but why does the
error not occur when libutil.so is on tmpfs or NFS?)
* new zlib code requires more/less memory bandwidth, changes
power consumption of CPU/memory which is causing random errors
(unlikely because only same part of .got table is affected and
it happens on two different platforms)
* some DCACHE issue
> Which other related patches did you remove?
For 2.6.18 tests, I reverted only the patches which changed
lib/zlib_* after 2.6.17:
| 31925c8857ba17c11129b766a980ff7c87780301 [PATCH] Fix ppc32 zImage inflate
| b762450e84e20a179ee5993b065caaad99a65fbf [PATCH] zlib inflate: fix function definitions
| 0ecbf4b5fc38479ba29149455d56c11a23b131c0 move acknowledgment for Mark Adler to CREDITS
| 4f3865fb57a04db7cca068fed1c15badc064a302 [PATCH] zlib_inflate: Upgrade library code to a recent version
Enrico
[-- Attachment #2: Type: application/pgp-signature, Size: 480 bytes --]
next parent reply other threads:[~2006-11-03 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ly1wozcr1d.fsf@ensc-pc.intern.sigma-chemnitz.de>
[not found] ` <ly64dyt7de.fsf@ensc-pc.intern.sigma-chemnitz.de>
[not found] ` <1162497112.12781.51.camel@localhost.localdomain>
2006-11-03 10:09 ` Enrico Scholz [this message]
2006-11-13 21:56 ` [ARM] Corrupted .got section with 2.6.18 and JFFS2 (solved) Anton Vorontsov
2006-11-14 22:15 ` Anton Vorontsov
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=lywt6cc04g.fsf_-_@ensc-pc.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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