From: Artem Bityutskiy <dedekind@infradead.org>
To: naveen yadav <yad.naveen@gmail.com>
Cc: Linux-MTD Mailing List <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS Crash with ubifs-v2.6.21-HEAD.tar
Date: Wed, 01 Jul 2009 13:47:07 +0300 [thread overview]
Message-ID: <1246445227.20721.17.camel@localhost.localdomain> (raw)
In-Reply-To: <9bde694e0906302031x7c0df0bbvcfe6c4e0063f9f3@mail.gmail.com>
On Wed, 2009-07-01 at 09:01 +0530, naveen yadav wrote:
> Hi all,
>
> I am using kernel 2.6.18. and i have backported from 2.6.21 to
> 2.6.18. when i add kernel command line parameter as ubi.mtd=exe
> ubi.mtd=2 .
>
> i got crash in core.c file in function int device_add(struct device
> *dev). The reason for this i found is parent =
> get_device(dev->parent); is null.
>
> can any body suggest where dev->parent value gets assigned.
Not sure, this is ancient kernel and I doubt anyone is interested
digging it. You may try luck at lkml though, but I fear you'll
have to dig this yourself.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2009-07-01 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 3:31 UBIFS Crash with ubifs-v2.6.21-HEAD.tar naveen yadav
2009-07-01 10:47 ` Artem Bityutskiy [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=1246445227.20721.17.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=yad.naveen@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox