From: Ben Greear <greearb@candelatech.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Kernel 3.5.0 and user-space crash in closedir
Date: Thu, 09 Aug 2012 09:18:00 -0700 [thread overview]
Message-ID: <5023E2B8.4060307@candelatech.com> (raw)
Hello!
I've a strange issue...on the 3.5 kernel (patched with my own hacks, including
some nfs stuff), I see user-space crashes in closedir(). Apparently due to
memory corruption in glibc.
I ran under valgrind and detect no errors.
I cannot reproduce the bug on 3.3.x kernels (with similar hacks applied).
I am curious if anyone has seen anything similar.
Program terminated with signal 11, Segmentation fault.
#0 0x0000003c5ea7ea64 in _int_free (av=0x3c5edb1700, p=0x374e4b0, have_lock=0)
at malloc.c:4097
4097 unlink(av, nextchunk, bck, fwd);
(gdb) bt
#0 0x0000003c5ea7ea64 in _int_free (av=0x3c5edb1700, p=0x374e4b0, have_lock=0)
at malloc.c:4097
#1 0x0000003c5eab957d in __closedir (dirp=<optimized out>)
at ../sysdeps/unix/closedir.c:52
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2012-08-09 16:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5023E2B8.4060307@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-nfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).