| 477904934945ff04029cfa26a9030a908fbdb2d2 |
|
06-Nov-2010 |
Jason Chen <jasonchen@google.com> |
Resolve conflicts from merge of b6ee08aa into gingerbread-plus-aosp
Change-Id: Iebd91e356bec8bec29e120aea9bb10bcf02bc356
|
| b6ee08aadb580341a4d80943741b80de16a88b5d |
|
04-Nov-2010 |
d.moskvitin@samsung.com <d.moskvitin@samsung.com> |
Integrate Samsung fsck_msdos fixes, including problem seeking beyond 4 gig
Change-Id: I8829a3a2c26625d7405fa0a43da1640ea5c9ffbc
Signed-off-by: Mike Lockwood <lockwood@google.com>
/external/fsck_msdos/fat.c
|
| 59ae828834dc177c74775cf36cafda4da9927bd9 |
|
21-Jul-2010 |
Ethan <ethan.too@gmail.com> |
Fix an out of boundary access in fat.c
From SD Specifications Part2 - File System
For Next Free Cluster, value FFFFFFFFh indicates that there exists
no information about the first available (free) cluster. It is a
valid value. However fat.c doesn't check the value before use it
as array index. This will cause fsck_msdos coredump with some
micro sd cards
Change-Id: Ibdec1655399d95c3ca98a4f4aaed1fd9bf459f33
Signed-off-by: Ethan <ethan.too@gmail.com>
/external/fsck_msdos/fat.c
|
| 11877c86e96c485b9632ea758b225bcacf6e7670 |
|
16-Jul-2009 |
San Mehat <san@google.com> |
fsck_msdos: Instead of bailing out when we can't reconnect a lost cluster chain, clear it.
Also, use exit code 4 when the FS has been modified in someway.
Signed-off-by: San Mehat <san@google.com>
/external/fsck_msdos/fat.c
|
| a3833718636c6bdcdf0bef2674e864e948e81d27 |
|
10-Jul-2009 |
San Mehat <san@google.com> |
fsck_msdos: Don't bail out when there are FAT differences - auto-correct
Signed-off-by: San Mehat <san@google.com>
/external/fsck_msdos/fat.c
|
| 58d4c6c35633437182289e3d226d156d31d3e801 |
|
25-Jun-2009 |
San Mehat <san@google.com> |
fsck_msdos: Initial checkin
Signed-off-by: San Mehat <san@google.com>
/external/fsck_msdos/fat.c
|