public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Alexander Belyakov <abelyako@googlemail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [JFFS2] Non-contiguous write bug fix (Sibley)
Date: Wed, 18 Apr 2007 10:06:44 -0500	[thread overview]
Message-ID: <1176908804.21611.37.camel@shinybook.infradead.org> (raw)
In-Reply-To: <fe810cf0704170414r59900903rc8ed2e52d22eb833@mail.gmail.com>

On Tue, 2007-04-17 at 15:14 +0400, Alexander Belyakov wrote:
> Yes, the bug still exists. The patch fixes JFFS2 non-contiguous write
> error on Sibley.

Sorry, I missed (or have forgotten) this. Can you explain in a little
more detail?

The following condition (SECTOR_ADDR(to) != SECTOR_ADDR(wbuf_ofs)) is
supposed to handle this, surely? In what circumstances is it
insufficient?

As far as I can tell, your new check allows us to write anywhere _after_
writing the first wbuf-load in a new eraseblock.

Hm, is this because the cleanmarker size in Sibley is also the wbuf
size? So you were hitting the BUG() after writing the cleanmarker to a
newly-erased block (hence setting wbuf_ofs to point there), but then
moving on to actually _write_ elsewhere?

If that's the case, perhaps the code which writes the cleanmarker
shouldn't be using jffs2_flash_writev() to write it -- perhaps it should
be bypassing the wbuf handling altogether?

-- 
dwmw2

  reply	other threads:[~2007-04-18 15:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 11:14 [PATCH] [JFFS2] Non-contiguous write bug fix (Sibley) Alexander Belyakov
2007-04-18 15:06 ` David Woodhouse [this message]
2007-04-19 13:59   ` Alexander Belyakov
2007-05-02 13:49   ` Alexander Belyakov
2007-05-02 13:58     ` David Woodhouse
2007-05-02 14:53       ` Alexander Belyakov
2007-05-02 17:10         ` David Woodhouse
2007-05-03  9:31           ` Alexander Belyakov
2007-05-04 11:52             ` Alexander Belyakov

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=1176908804.21611.37.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=abelyako@googlemail.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