diff options
| author | Jan Kara <jack@suse.cz> | 2011-12-23 11:53:07 +0100 |
|---|---|---|
| committer | Jan Kara <jack@suse.cz> | 2012-01-09 13:52:10 +0100 |
| commit | 853a0c25baf96b028de1654bea1e0c8857eadf3d (patch) | |
| tree | 2b72d7cafe569583322fa132ebc8c9821e8d7bce /fs/udf | |
| parent | 33c104d415e92a51aaf638dc3d93920cfa601e5c (diff) | |
udf: Mark LVID buffer as uptodate before marking it dirty
When we hit EIO while writing LVID, the buffer uptodate bit is cleared.
This then results in an anoying warning from mark_buffer_dirty() when we
write the buffer again. So just set uptodate flag unconditionally.
Reviewed-by: Namjae Jeon <linkinjeon@gmail.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'fs/udf')
| -rw-r--r-- | fs/udf/super.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/fs/udf/super.c b/fs/udf/super.c index e185253470df..87cb24a0ee7b 100644 --- a/fs/udf/super.c +++ b/fs/udf/super.c @@ -1799,6 +1799,12 @@ static void udf_close_lvid(struct super_block *sb) le16_to_cpu(lvid->descTag.descCRCLength))); lvid->descTag.tagChecksum = udf_tag_checksum(&lvid->descTag); + /* + * We set buffer uptodate unconditionally here to avoid spurious + * warnings from mark_buffer_dirty() when previous EIO has marked + * the buffer as !uptodate + */ + set_buffer_uptodate(bh); mark_buffer_dirty(bh); sbi->s_lvid_dirty = 0; mutex_unlock(&sbi->s_alloc_mutex); |