mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: barebox@lists.infradead.org
Subject: Re: Ramfs and NULL pointer
Date: Sun, 4 Nov 2012 23:56:14 +0100	[thread overview]
Message-ID: <20121104225614.GU1641@pengutronix.de> (raw)
In-Reply-To: <87vcdlurvc.fsf@free.fr>

On Sun, Nov 04, 2012 at 07:48:07PM +0100, Robert Jarzmik wrote:
> Robert Jarzmik <robert.jarzmik@free.fr> writes:
> 
> > Hi there,
> >
> > Lately, I see null pointer dereferences in barebox.
> > I traced the culprit to ramfs ...
> 
> Ah and if I take back v2012.09.0, the problem disappears. 
> I'm not fully in the mood for a bisection of 544 commits ... any idea ?

sha@dude:~/dude/barebox/barebox git lg v2012.09.0..origin/master fs/ramfs.c
77322aa Treewide: remove address of the Free Software Foundation
ad6c28a ramfs: add symlink and readlink support

Both look harmless, so I don't think that the culprit is ramfs itself.

Sorry, no idea. The good news is that due to my compile tests all 544
commits at least should compile ;)

Do you have some specific command sequence to provoke this?

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

  reply	other threads:[~2012-11-04 22:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-04 17:53 Robert Jarzmik
2012-11-04 18:48 ` Robert Jarzmik
2012-11-04 22:56   ` Sascha Hauer [this message]
2012-11-05  8:23     ` Robert Jarzmik
2012-11-20 20:43     ` Robert Jarzmik
2012-11-20 20:50       ` Robert Jarzmik

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=20121104225614.GU1641@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=robert.jarzmik@free.fr \
    /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