UBI Create or Update Volume

BRIJESH SINGH brij.singh at samsung.com
Wed Jun 17 09:33:15 EDT 2009

 [Sorry. I will try to take care of it in future emails.]
On Wed, Jun 17, 2009 at 3:26 PM, Artem Bityutskiy <dedekind at infradead.org> wrote:
     On Wed, 2009-06-17 at 09:33 +0000, BRIJESH SINGH wrote:
      >> Hi Artem,
      >>      Just came across the ubi_change_vtbl_record function. If first copy is written successfully and error occurs while writing second copy, this function still returns error. And hence the creation or change in Volume becomes unsuccessful. So applications consider it failure.
      >>   But if I unmount now, (clean or unclean) the first copy will become valid and second will be called corrupted (during mount time). It's not correct.
      >>    So should ubi_change_vtbl_record  call flush wl and  return success? Because 2nd copy(old) is unmapped till now.And should UBI go to read-only mode?
> Yes, sounds right. Would you send a patch?
Yes, I will send a patch once I test it properly.


More information about the linux-mtd mailing list