From: Artem Bityutskiy Date: Sun, 8 Aug 2010 09:32:00 +0000 (+0300) Subject: UBIFS: do not write rubbish into truncation scanning node X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=5b7a3a2e1b0cbc7d5410a8da60dac266a3e19268;p=GitHub%2FLineageOS%2Fandroid_kernel_samsung_universal7580.git UBIFS: do not write rubbish into truncation scanning node In the scanning code, in 'ubifs_add_snod()', we write rubbish into 'snod->key', because we assume that on-flash truncation nodes have a key, but they do not. If the other parts of UBIFS then mistakenly try to look-up the truncation node key (they should not do this, but may do because of a bug), we can succeed and corrupt TNC. It looks like we did have such a situation in 'sort_nodes()' in gc.c. Signed-off-by: Artem Bityutskiy --- diff --git a/fs/ubifs/scan.c b/fs/ubifs/scan.c index 96c52538419..a0a305ca61a 100644 --- a/fs/ubifs/scan.c +++ b/fs/ubifs/scan.c @@ -212,7 +212,6 @@ int ubifs_add_snod(const struct ubifs_info *c, struct ubifs_scan_leb *sleb, case UBIFS_DENT_NODE: case UBIFS_XENT_NODE: case UBIFS_DATA_NODE: - case UBIFS_TRUN_NODE: /* * The key is in the same place in all keyed * nodes.