From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: why would i get "Out of memory" error in a sandbox build?
Date: Fri, 4 Jul 2014 07:30:14 +0200 [thread overview]
Message-ID: <20140704053014.GA26384@pengutronix.de> (raw)
In-Reply-To: <alpine.LFD.2.11.1407030722210.21206@localhost>
On Thu, Jul 03, 2014 at 07:23:07AM -0400, Robert P. J. Day wrote:
> On Thu, 3 Jul 2014, Sascha Hauer wrote:
>
> > On Wed, Jul 02, 2014 at 03:50:36PM -0400, Robert P. J. Day wrote:
> > >
> > > barebox@barebox sandbox:/
> > >
> > > i'm actually good with this, it's about what i expected since i set
> > > no environment or networking, etc. but just for fun, i "cd"ed down
> > > into /mnt/tftp, knowing this shouldn't work, and here's what happened:
> > >
> > > barebox@barebox sandbox:/ cd /mnt/tftp
> > > ifup: Cannot find device eth0
> > > ifup: No such file or directory
> > > running automount command 'ifup eth0 && mount -t tftp $eth0.serverip
> > > /mnt/tftp' failed
> > > barebox@barebox sandbox:/mnt/tftp cd /
> > > ERROR: out of memory
> > >
> > > no stack data available
> > > [rpjday@localhost barebox_build]$
> > >
> > > in short, "cd"ing into /mnt/tftp failed as it should have, but just
> > > trying to "cd" back to the root caused the "out of memory" error. it
> > > seems entirely reproducible. should i have expected this?
> >
> > This is an interesting bug you triggered. by changing the cwd to an
> > automount directory you found a way to trigger the automount function
> > from the automount function resulting in an endless loop. This loop
> > gets interrupted when we are out of memory.
> >
> > I sent a fix to the list which fixes this.
>
> i *swear*, i'm not *trying* to find the most obscure bugs
> imaginable. :-)
Well I have no problem with that. Go out and find more bugs, it can only
be good for the project ;)
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-07-04 5:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 19:50 why would i get "Out of memory" error in a sandbox build? Robert P. J. Day
2014-07-03 6:26 ` Sascha Hauer
2014-07-03 11:23 ` Robert P. J. Day
2014-07-04 5:30 ` Sascha Hauer [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=20140704053014.GA26384@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/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.