> dirty pagecache error recoverable under some conditions. Consider that > if there is a copy of the corrupted dirty pagecache on user buffer and > you write() over the error page with the copy data, then we can ignore > the effect of the error because no one consumes the corrupted data.
This sounds like a quite rare corner case. If the page is already dirty, it is most likely because someone recently did a write(2) (or touched it via mmap(2)). Now you are hoping that some process is going to write the same page again. Do you have an application in mind where this would be common. Remember that the write(2), memory-error, new write(2) have to happen close together (before Linux decides to write out the dirty page). -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
