public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: MikeW <mw_phil@yahoo.co.uk>
To: linux-mtd@lists.infradead.org
Subject: Re: jffs2/mtd on flash Spansion S29GL064AR4
Date: Thu, 24 May 2007 07:36:42 +0000 (UTC)	[thread overview]
Message-ID: <loom.20070524T093136-704@post.gmane.org> (raw)
In-Reply-To: LOEGJDCFIFDBMCDIAOKDMEANCIAA.teun@adesys.nl

Teun Grinwis <teun <at> adesys.nl> writes:

> 
> Hello All,
> 
> After further investigation, the real problem is a NULL ptr function
> call in kernel/sched.c, see below:
>
> ...snip...
>
> I tried a patch in kernel/sched.c, __wake_up_common:
> ...
>         if( curr->func == NULL || (curr->func(curr, mode, sync, key) &&
>                                    (flags & WQ_FLAG_EXCLUSIVE) &&
>                                    !--nr_exclusive) ) {
>             break;
>         }
> ...
> 
> Now jffs2 can be initialized on our flash S29GL064AR4. Also a test file
> remains
> persistent after re-power our system.
> 
> Is this patch right? My feeling is that something should be done in mtd!
> 
> Thanks for your info,
> 
> Regards
> 
> Teun Grinwis

Well, it's right in that it avoids the crunch of a NULL ptr,
but presumably the logic of the code should never permit
this to happen, so something's wrong somewhere else !

Perhaps as a side issue, drivers ought to include a 'checked' build
setting that effectively does an assertion check on things like
pointers about to be dereferenced, to spot issues during testing.

Regards,
MikeW

      reply	other threads:[~2007-05-24  7:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14  7:02 jffs2/mtd on flash Spansion S29GL064AR4 Teun Grinwis
2007-05-22  8:02 ` Teun Grinwis
2007-05-24  7:36   ` MikeW [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=loom.20070524T093136-704@post.gmane.org \
    --to=mw_phil@yahoo.co.uk \
    --cc=linux-mtd@lists.infradead.org \
    /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