kernel.git/fs/jffs2/wbuf.c, branch linux-3.2.y

JFFS2: don't fail on bitflips in OOB

2012-10-17T02:49:15Z

commit 74d83beaa229aac7d126ac1ed9414658ff1a89d2 upstream. JFFS2 was designed without thought for OOB bitflips, it seems, but they can occur and will be reported to JFFS2 via mtd_read_oob()[1]. We don't want to fail on these transactions, since the data was corrected. [1] Few drivers report bitflips for OOB-only transactions. With such drivers, this patch should have no effect. Signed-off-by: Brian Norris Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse [bwh: Backported to 3.2: adjust context] Signed-off-by: Ben Hutchings

mtd: rename MTD_OOB_* to MTD_OPS_*

2011-09-11T12:28:59Z

These modes are not necessarily for OOB only. Particularly, MTD_OOB_RAW affected operations on in-band page data as well. To clarify these options and to emphasize that their effect is applied per-operation, we change the primary prefix to MTD_OPS_. Signed-off-by: Brian Norris Signed-off-by: Artem Bityutskiy

jffs2: use mutex_is_locked() in __jffs2_flush_wbuf()

2011-09-11T12:02:14Z

Use a helper to test if a mutex is held instead of a hack with mutex_trylock(). Signed-off-by: Alexey Khoroshilov Signed-off-by: Artem Bityutskiy

Fix common misspellings

2011-03-31T14:26:23Z

Fixes generated by 'codespell' and manually reviewed. Signed-off-by: Lucas De Marchi

jffs2: Rename jffs2_erase_pending_trigger() to jffs2_dirty_trigger()

2010-05-19T16:15:36Z

Now that we do erases from GC and trigger the GC thread to do them instead of using kupdated, this function is misnamed. It's only used for triggering wbuf flush on NAND flash now. Rename it accordingly. Signed-off-by: Joakim Tjernlund Signed-off-by: David Woodhouse

jffs2: Use jffs2_garbage_collect_trigger() to trigger pending erases

2010-05-19T16:10:44Z

This is now done in a GC pass; we don't need to trigger kupdated to do it. Signed-off-by: David Woodhouse

JFFS2: add missing verify buffer allocation/deallocation

2009-09-03T14:01:34Z

The function jffs2_nor_wbuf_flash_setup() doesn't allocate the verify buffer if CONFIG_JFFS2_FS_WBUF_VERIFY is defined, so causing a kernel panic when that macro is enabled and the verify function is called. Similarly the jffs2_nor_wbuf_flash_cleanup() must free the buffer if CONFIG_JFFS2_FS_WBUF_VERIFY is enabled. The following patch fixes the problem. The following patch applies to 2.6.30 kernel. Signed-off-by: Massimo Cirillo Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse Cc: stable@kernel.org

[JFFS2] Write buffer offset adjustment for NOR-ECC (Sibley) flash

2008-10-18T10:54:09Z

After choosing new c->nextblock, don't leave the wbuf offset field occasionally pointing at the start of the next physical eraseblock. This was causing a BUG() on NOR-ECC (Sibley) flash, where we start writing after the cleanmarker. Among other this fix should cover write buffer offset adjustment after flushing the last page of an eraseblock. Signed-off-by: Alexander Belyakov Signed-off-by: David Woodhouse

[JFFS2] Track parent inode for directories (for NFS export)

2008-05-01T17:47:17Z

To support NFS export, we need to know the parent inode of directories. Rather than growing the jffs2_inode_cache structure, share space with the nlink field -- which was always set to 1 for directories anyway. Signed-off-by: David Woodhouse

[JFFS2] Invert last argument of jffs2_gc_fetch_inode(), make it boolean.

2008-05-01T16:24:28Z

We don't actually care about nlink; we only care whether the inode in question is unlinked or not. Signed-off-by: David Woodhouse