Messages in this thread | | | Date | Sun, 29 Mar 2009 21:51:06 -0400 | From | Jeff Garzik <> | Subject | Re: [PATCH 2/5] ext3: call blkdev_issue_flush on fsync() |
| |
Fernando Luis Vázquez Cao wrote: > To ensure that bits are truly on-disk after an fsync or fdatasync, we > should force a disk flush explicitly when there is dirty data/metadata > and the journal didn't emit a write barrier (either because metadata is > not being synched or barriers are disabled). > > Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
Your patches do not seem to propagate the issue-flush error code, even when it is easily available.
Jeff
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |