public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2_flash_writev(): Non-contiguous write to 00825300 with mtd_dataflash
Date: Mon, 13 Nov 2006 09:46:49 +0200	[thread overview]
Message-ID: <1163404009.3925.26.camel@sauron> (raw)
In-Reply-To: <20061101115252.26000d78@cad-250-152.norway.atmel.com>

Hello Haavard,

On Wed, 2006-11-01 at 11:52 +0100, Haavard Skinnemoen wrote:
> I've seen a couple of other people reporting this bug before, so I'm
> just going to offer some observations I've made when trying to debug
> this (I'm not a filesystem developer, so I don't fully understand the
> code).
> 
> I can successfully mount a jffs2 filesystem on a freshly erased
> AT45DB642x DataFlash chip through the mtd_dataflash driver. However,
> when trying to write something to a file on that filesystem, I get a
> BUG and the messages
> 
> jffs2_flash_writev(): Non-contiguous write to 00825300
> wbuf was previously 00825300-008253b8
> 
> Just creating a file without trying to write anything to it works fine.
> 
> I've inserted a call to dump_stack() and a few debugging printks in
> jffs2_flash_writev() to see what's going on, and I see the following:

So all it seems that you need to to make jffs2_can_mark_obsokete()
return 0 in case of dataflash.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2006-11-13  7:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01 10:52 jffs2_flash_writev(): Non-contiguous write to 00825300 with mtd_dataflash Haavard Skinnemoen
2006-11-13  7:46 ` Artem Bityutskiy [this message]
2006-11-28 11:58   ` Haavard Skinnemoen
2006-11-28 12:36     ` Artem Bityutskiy
2006-11-29 13:26       ` Haavard Skinnemoen
2006-11-29 17:21         ` David Brownell
2006-11-30  6:29           ` Andrew Victor
2006-11-30  7:54             ` [Bulk] " David Brownell
2006-12-01  8:21           ` Artem Bityutskiy

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=1163404009.3925.26.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=hskinnemoen@atmel.com \
    --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