why would i get "Out of memory" error in a sandbox build?
Sascha Hauer
s.hauer at pengutronix.de
Thu Jul 3 22:30:14 PDT 2014
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 at 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 at 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 at barebox sandbox:/mnt/tftp cd /
> > > ERROR: out of memory
> > >
> > > no stack data available
> > > [rpjday at 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 |
More information about the barebox
mailing list