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

Hi,

On Fri, 2008-05-30 at 17:30 +1000, Hamish Moffatt wrote:
> 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?

Right. It is basically harmless, it's just that the hash function will
collide more often which may result in poorer performance in case of
large directories.

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

Right. But we may keep the support if you need this of course.

> 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.

Oh. We fixed many bugs since that time :-) Of course you may never hit
them, everything depends on the use-case. But I would update the kernel.

Anyway, if you want, we may keep backward compatibility so that new
kernel will work fine with older (version 2) images.

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

      reply	other threads:[~2008-05-30  9:19 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
2008-05-30  9:20   ` 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=1212139250.31023.114.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=hamish@cloud.net.au \
    --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