All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: glibc detected *** groupadd: malloc(): memory corruption
Date: Sat, 23 Jun 2012 11:09:50 +0800	[thread overview]
Message-ID: <4FE5337E.2030400@windriver.com> (raw)
In-Reply-To: <4FE341CF.5060406@linux.intel.com>



On 06/21/2012 11:46 PM, Saul Wold wrote:
> On 06/19/2012 11:07 PM, Robert Yang wrote:
>>
>> Thanks Mark, the rpm.real also has the same problem when the length of
>> tmpdir
>> is 210, it seems that this is because of the glibc.
>>
>>
>> And also other problems found:
>> When use PACKAGE_CLASSES = "package_deb", and the length of tmpdir is 177,
>> the error is:
>>
>> /too/long/path/totmp/sysroots/x86_64-linux/usr/bin/dpkg-scanpackages:
>> bad interpreter: No such file or directory
>>
>> The interpreter is perl, and it does exist, it seems that we should limit
>> the length of tmpdir to a smaller value then 177 rather than fix these
>> strange
>> problems. I will go on working on it.
>>
> Robert,
>
> A path length of 175 or short is not ideal, we should file bugs against these

Thanks Saul, the bug is:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=2639

I'd like to try to fix it next week, I will send a patch to show the WARNING
as you suggested if I can't fix it, but the value maybe shorter than 175,
I've realised that even 175 is a very short value, so this should be fixed:-)

// Robert

> issues. We should also add the sanity check you suggested as a WARNING for
> lenghts over 175. That should not be the final solution though, we need to
> address the issues and get them fixed up stream.
>
> The groupadd one sounds like it might be a buffer overflow issue which could
> have larger ramifications
>
> Thanks
>
> Sau!
>
>> // Robert
>>
>> On 06/19/2012 01:47 AM, Mark Hatle wrote:
>>> We're not away of any size limitations within pseudo, other then
>>> PATH_MAX which
>>> is typically 4096...
>>>
>>> --Mark
>>>
>>> On 6/18/12 4:17 AM, Robert Yang wrote:
>>>>
>>>> Hi Experts:
>>>>
>>>> I've met a strange issue, when set the length of builddir to
>>>> 266 (Why I did this is that I need to know how long the tmpdir
>>>> that oe-core can support):
>>>>
>>>> NOTE: package dbus-1.4.20-r3.0: task do_install: Started
>>>> *** glibc detected *** groupadd: malloc(): memory corruption:
>>>> 0x000000000101da70 ***
>>>> *** glibc detected *** groupadd: malloc(): memory corruption:
>>>> 0x000000000101da70 ***
>>>>
>>>> Then the build would hang, this is caused by the command:
>>>>
>>>> PSEUDO_PREFIX=/too/long/path/tmp/sysroots/x86_64-linux/usr
>>>> PSEUDO_LOCALSTATEDIR=... PSEUDO_PASSWD=...
>>>> PSEUDO_NOSYMLINKEXP=1 PSEUDO_DISABLED=0 PSEUDO_LOCALSTATEDIR
>>>> ... /too/long/path/to/tmp/sysroots/x86_64-linux/usr/bin/pseudo
>>>> groupadd --root /too/long/path/to/tmp/sysroots/qemux86 -r netdev -f
>>>>
>>>> 1) I had looked into the code of groupadd, and found that this would
>>>> happen when it used the glibc function which needs malloc(for example,
>>>> the access()), so it seemed this was caused by the glibc or pseudo,
>>>> but I didn't know why it only happened to groupadd/useradd.
>>>>
>>>> 2) I had tried not to use pseudo, it worked well:
>>>>
>>>> sudo groupadd --root /too/long/path/to/tmp/sysroots/qemux86 -r netdev -f
>>>>
>>>> From this, it seemed that the glibc was ok
>>>>
>>>> 3) I had tried to write a small piece of code which used the
>>>> access(), and
>>>> used pseudo to run it, it worked well:
>>>>
>>>> /too/long/path/for/pseudo/settings/and/then/run/pseudo my_app
>>>>
>>>> From this, it seemed that both pseudo and glibc were OK.
>>>>
>>>> These 3 steps make me puzzle, maybe we can think that the tmpdir can not
>>>> be too long, and limit it to a proper length, please see this:
>>>>
>>>> http://lists.linuxtogo.org/pipermail/openembedded-core/2012-May/022112.html
>>>>
>>>>
>>>> BTW. the "argument list too long" error has been fixed.
>>>>
>>>> Any suggestion is appreciated.
>>>>
>>>
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>>
>
>



      parent reply	other threads:[~2012-06-23  3:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18  9:17 glibc detected *** groupadd: malloc(): memory corruption Robert Yang
2012-06-18 17:47 ` Mark Hatle
2012-06-20  6:07   ` Robert Yang
2012-06-21 15:46     ` Saul Wold
2012-06-21 15:57       ` Mark Hatle
2012-06-23  3:09       ` Robert Yang [this message]

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=4FE5337E.2030400@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.