public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS on-media format changed to version 3
Date: Fri, 30 May 2008 17:30:25 +1000	[thread overview]
Message-ID: <20080530073025.GB20369@cloud.net.au> (raw)
In-Reply-To: <1212047442.31023.64.camel@sauron>

On Thu, May 29, 2008 at 10:50:42AM +0300, Artem Bityutskiy wrote:
> we have found a bug in UBIFS and the fix changes the on-media format.
> Namely, the direntry hash function changed. We've always assumed it to
> be 29 bits wide, but because of incorrect bitmask it has been only 25
> bits wide.
> 
> Please, update UBIFS and mkfs.ubifs to version 0.7. We have changed
> media format version from 2 to 3 as well. We support compatibility with
> older JFFS2 format (version 2) for now, but we would like to drop the
> support, unless someone really needs this and asks us not to do this. We
> are not in mainline so far, so we probably have luxury of changing
> on-flash format so far.
> 
> I've CCed people who may be using UBIFS and should be aware of the
> change.

Hi Artem,

Thanks for the notification.

What's the impact of the bug? Does it only affect particularly large
volumes or directories with a particularly large number of files or
something else?

As I understand your comments, the new source will currently work with 
existing file systems but you want to drop that ability?

We're just about to deploy devices with 2.6.24 + ubifs from GIT a month
or two back, though we're probably not going to upgrade the kernel on
existing devices in the future anyway.

Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  reply	other threads:[~2008-05-30  7:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29  7:50 UBIFS on-media format changed to version 3 Artem Bityutskiy
2008-05-30  7:30 ` Hamish Moffatt [this message]
2008-05-30  9:20   ` 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=20080530073025.GB20369@cloud.net.au \
    --to=hamish@cloud.net.au \
    --cc=dedekind@infradead.org \
    --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