02 Aug, 2011
1 commit
-
This fixes a race during unmount. We need to not only make sure that
the journal is completely written, but that the metadata changes make
it to disk before releasing ipimap and ipbmap.Signed-off-by: Dave Kleikamp
04 Jan, 2008
1 commit
-
This patch makes sure that data that we tried to flush before the journal
was completely written actually gets pushed to disk.To avoid duplicating code, moved common code to write_special_inodes().
Signed-off-by: Dave Kleikamp
07 Jun, 2007
1 commit
-
Signed-off-by: Dave Kleikamp
02 Oct, 2006
1 commit
-
Removed trailing spaces & tabs, and spaces preceding tabs.
Also a couple very minor comment cleanups.Signed-off-by: Dave Kleikamp
(cherry picked from f74156539964d7b3d5164fdf8848e6a682f75b97 commit)
09 Jan, 2006
1 commit
-
This patch add EXPORT_SYMBOL(filemap_write_and_wait) and use it.
See mm/filemap.c:
And changes the filemap_write_and_wait() and filemap_write_and_wait_range().
Current filemap_write_and_wait() doesn't wait if filemap_fdatawrite()
returns error. However, even if filemap_fdatawrite() returned an
error, it may have submitted the partially data pages to the device.
(e.g. in the case of -ENOSPC)Andrew Morton writes,
If filemap_fdatawrite() returns an error, this might be due to some
I/O problem: dead disk, unplugged cable, etc. Given the generally
crappy quality of the kernel's handling of such exceptions, there's a
good chance that the filemap_fdatawait() will get stuck in D state
forever.So, this patch doesn't wait if filemap_fdatawrite() returns the -EIO.
Trond, could you please review the nfs part? Especially I'm not sure,
nfs must use the "filemap_fdatawrite(inode->i_mapping) == 0", or not.Acked-by: Trond Myklebust
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
03 May, 2005
1 commit
-
jfs has never worked on architecutures where the page size was not 4K.
Signed-off-by: Dave Kleikamp
Signed-off-by: Linus Torvalds
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!
