Fix bugs and possible data corruption if blocksize < pagesize
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | ext3: Fix false EIO errorsfs/ | +1 | 0 replies | |
| 2/4 | ext3: Avoid false EIO errorsfs/ | +5 | 0 replies | |
| 3/4 | fs: Avoid data corruption with blocksize < pagesizefs/ | +6 | 5 replies | |
| 4/4 | fs: Warn about writing !uptodate buffersfs/ | +2 | 1 reply |
Reviews trailers per patch
1 of 4 patches has a Reviewed-by or Acked-by.
| Patch | Nick Piggin |
|---|---|
| 1/4 | |
| 2/4 | |
| 3/4 | |
| 4/4 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/4] Fix bugs and possible data corruption if blocksize < pagesize
Hi,
lately, I've been tracking some problems with ext3 reported by HP on ia64 and
this is what I came with. The first three patches fix real bugs - the first two fix bugs in ext3 leading to false reports of EIO errors from JBD and aborted journal, the third patch fixes a bug in block_write_full_page() which can possibly lead to data corruption.
With these patches, don't see the data corruption I was able to reproduce
with fsx-linux under UML. I'm not yet sure whether all the problems HP reported are gone (they're testing now) but since this seems to be a nasty problem I'm posting earlier rather than later. Please someone have a look whether my fix and analysis looks sane. Thanks.
Honza