diff options
author | Kyungmin Park <kyungmin.park@samsung.com> | 2007-03-23 02:19:52 +0100 |
---|---|---|
committer | David Woodhouse <dwmw2@infradead.org> | 2007-04-25 12:09:23 +0200 |
commit | ad286343665cad2135792bcf53117d8344f64b03 (patch) | |
tree | b318886702e697d7f1fbd476851ee03e28ebebc9 /fs/jffs2/README.Locking | |
parent | [MTD] [OneNAND] Update Samsung OneNAND official URL (diff) | |
download | linux-ad286343665cad2135792bcf53117d8344f64b03.tar.xz linux-ad286343665cad2135792bcf53117d8344f64b03.zip |
[MTD] [OneNAND] Fix access the past of the real oobfree array
Here it's not the case: all the entries are occupied by
OOB chunks. Therefore, once we get into a loop like
for (free = this->ecclayout->oobfree; free->length; ++free) {
}
we might end up scanning past the real oobfree array.
Probably the best way out, as the same thing might happen for common NAND
as well, is to check index against MTD_MAX_OOBFREE_ENTRIES.
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
Diffstat (limited to 'fs/jffs2/README.Locking')
0 files changed, 0 insertions, 0 deletions