summaryrefslogtreecommitdiffstats
path: root/fs/udf/udf_sb.h
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2009-03-19 16:21:38 +0100
committerJan Kara <jack@suse.cz>2009-04-02 12:29:56 +0200
commit40346005166329bc4b53e0c564aff3968c1ddaa0 (patch)
treeaf6440a2aeff69ed6cccd93c663eb564e7cf6411 /fs/udf/udf_sb.h
parent225feded89d447c2ab76e38e67ef56860c5bb60f (diff)
downloadlinux-40346005166329bc4b53e0c564aff3968c1ddaa0.tar.bz2
udf: Try anchor in block 256 first
Anchor block can be located at several places on the medium. Two of the locations are relative to media end which is problematic to detect. Also some drives report some block as last but are not able to read it or any block nearby before it. So let's first try block 256 and if it is all fine, don't look at other possible locations of anchor blocks to avoid IO errors. This change required a larger reorganization of code but the new code is hopefully more readable and definitely shorter. Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'fs/udf/udf_sb.h')
-rw-r--r--fs/udf/udf_sb.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/udf/udf_sb.h b/fs/udf/udf_sb.h
index 2dd921928338..46fea3ea70a9 100644
--- a/fs/udf/udf_sb.h
+++ b/fs/udf/udf_sb.h
@@ -117,7 +117,7 @@ struct udf_sb_info {
/* Sector headers */
__s32 s_session;
- __u32 s_anchor[3];
+ __u32 s_anchor;
__u32 s_last_block;
struct buffer_head *s_lvid_bh;