From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Fix FAT block caching
Date: Wed, 15 Feb 2012 09:10:47 +0100 [thread overview]
Message-ID: <1329293450-10234-1-git-send-email-s.hauer@pengutronix.de> (raw)
The FAT driver has to access the file allocation table and also the
data on the device. This case hasn't been covered by the current
block caching mechanism. For this reason the FAT driver cached the
file allocation table itself. Due to some bugs the file allocation
table in the cache and on the device can get out of sync. A quite
simple way to trigger this is to create a directory and unmount
the filesystem afterwards. The directory will not be written to
disk. This series fixes this by reverting the FAT internal caching
mechanism and instead extend the block caching layer to cover
this case.
Sascha Hauer (3):
list: add list_last_entry function
fat: revert fat caching mechanism
block: reimplement caching
common/block.c | 274 ++++++++++++++++++++++++++++++++++++-------------
fs/fat/ff.c | 93 ++++-------------
include/block.h | 16 ++--
include/linux/list.h | 11 ++
4 files changed, 241 insertions(+), 153 deletions(-)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2012-02-15 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 8:10 Sascha Hauer [this message]
2012-02-15 8:10 ` [PATCH 1/3] list: add list_last_entry function Sascha Hauer
2012-02-15 8:10 ` [PATCH 2/3] fat: revert fat caching mechanism Sascha Hauer
2012-02-15 8:10 ` [PATCH 3/3] block: reimplement caching Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1329293450-10234-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox