Re: [PATCH] Fix bad data from non-direct-io read after direct-io write

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Zach Brown <zach.brown@...>
Cc: Karl Schendel <kschendel@...>, Benjamin LaHaise <bcrl@...>, Andrew Morton <akpm@...>, Linux Kernel Mailing List <linux-kernel@...>, Nick Piggin <nickpiggin@...>, Leonid Ananiev <leonid.i.ananiev@...>, Chris Mason <chris.mason@...>
Date: Friday, October 26, 2007 - 6:42 pm

On Fri, 26 Oct 2007, Zach Brown wrote:

How about not testing at all? Which was what the old code did.

Just do the invalidate unconditionally for any writes, and screw the end 
result of the invalidate, since we cannot afford to overwrite the previous 
return value anyway in any realistic scenario?

		Linus
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH] Fix bad data from non-direct-io read after direc..., Linus Torvalds, (Fri Oct 26, 6:42 pm)