Naoya Horiguchi <n-horigu...@ah.jp.nec.com> writes: > Current memory error handling on dirty pagecache has a bug that user > processes who use corrupted pages via read() or write() can't be aware > of the memory error and result in discarding dirty data silently. > > The following patch is to improve handling/reporting memory errors on > this case, but as a short term solution I suggest that we should undo > the present error handling code and just leave errors for such cases > (which expect the 2nd MCE to panic the system) to ensure data consistency.
Not sure that's the right approach. It's not worse than any other IO errors isn't it? -Andi -- a...@linux.intel.com -- Speaking for myself only -- 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/
