From: Artem Bityutskiy <dedekind1@gmail.com>
To: Leo Barnes <barnes.leo@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: CRC error when mounting UBIFS
Date: Fri, 04 Jun 2010 21:01:53 +0300 [thread overview]
Message-ID: <1275674513.9729.22.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimUrdHmrf5hblunbpI3J24A6tMQj1tIIXbSQoIy@mail.gmail.com>
On Fri, 2010-06-04 at 19:35 +0200, Leo Barnes wrote:
> > The way to fix this is to make UBI/UBIFS use arrays of pages instead. Or
> > array of 2, 4, 8, etc pages, or it may be flexible and contain a field
> > which describes the allocation order. And then UBI/UBIFS code should be
> > amended correspondingly.
> >
> > This will need some effort, but I think a skilled engineer would do this
> > relatively quickly. We are not actively working on UBI/UBIFS now, so we
> > will unlikely implement this, but I'd be happy to help someone else to
> > do this.
> >
> > Many people ask about small features like security xattrs, or NFS
> > support, or DMA friendliness, but it is strange that people want ready
> > solutions instead of investing a bit of time and just implementing this.
>
> Sounds good, I might take a crack at it, I have been looking for some
> way to contribute to the linux kernel.
>
> Have I understood the UBI code correctly in that only the
> ubi->peb_buf1, ubi->peb_buf2 and ubi->dbg_peb_buf are ever sent to the
> mtd->read/write functions? Currently at home and dont really have
> anything to test code in.
Yes, AFAIR. If you really will try to do this, let's discuss the
strategy.
> Does UBIFS ever access the mtd-layer directly?
No. In UBIFS getting rid of vmalloc will be more difficult because it'll
need to modify algorithms like GC which walks uses the buffers.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-06-04 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 14:02 CRC error when mounting UBIFS Leo Barnes
2010-06-03 14:25 ` Artem Bityutskiy
2010-06-03 15:14 ` Leo Barnes
2010-06-03 15:32 ` Artem Bityutskiy
2010-06-04 16:18 ` Leo Barnes
2010-06-04 17:03 ` Artem Bityutskiy
2010-06-04 17:35 ` Leo Barnes
2010-06-04 18:01 ` Artem Bityutskiy [this message]
2010-06-18 18:02 ` Artem Bityutskiy
2010-06-03 15:41 ` 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=1275674513.9729.22.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=barnes.leo@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.