aboutsummaryrefslogtreecommitdiffstats
path: root/fs/nls/nls_koi8-ru.c
diff options
context:
space:
mode:
authorAdam Greenblatt <adam.greenblatt@gmail.com>2008-07-25 01:46:32 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2008-07-25 10:53:33 -0700
commitc0a1633b6201ef79e31b7da464d44fdf5953054d (patch)
treef379e3541e56aa805c5e3b15b2e5eadd3ca8cc28 /fs/nls/nls_koi8-ru.c
parent275c0a8f1253a7542ad9726956c918d8a1f694c4 (diff)
downloadkernel_samsung_aries-c0a1633b6201ef79e31b7da464d44fdf5953054d.zip
kernel_samsung_aries-c0a1633b6201ef79e31b7da464d44fdf5953054d.tar.gz
kernel_samsung_aries-c0a1633b6201ef79e31b7da464d44fdf5953054d.tar.bz2
isofs: fix minor filesystem corruption
Some iso9660 images contain files with rockridge data that is either incorrect or incompletely parsed. Prior to commit f2966632a134e865db3c819346a1dc7d96e05309 ("[PATCH] rock: handle directory overflows") (included with kernel 2.6.13) the kernel ignored the rockridge data for these files, while still allowing the files to be accessed under their non-rockridge names. That commit inadvertently changed things so that files with invalid rockridge data could not be accessed at all. (I ran across the problem when comparing some old CDs with hard disk copies I had made long ago under kernel 2.4: a few of the files on the hard disk copies were no longer visible on the CDs.) This change reverts to the pre-2.6.13 behavior. Signed-off-by: Adam Greenblatt <adam.greenblatt@gmail.com> Reviewed-by: Pekka Enberg <penberg@cs.helsinki.fi> Cc: <stable@kernel.org> [2.6.25.x, 2.6.26.x] Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/nls/nls_koi8-ru.c')
0 files changed, 0 insertions, 0 deletions