Hi,
XFS and ext4 in 11.3 are vulnerable to a possible temporary data
corruption when using aio+dio (basically there is a window in which
zeros are read back from a file even though AIO write to that location
is already reported as completed). The fix is already available upstream
but it changes prototype of ->end_io callback and thus it changes KABI.
It's impossible to fix the problem without changing the ->end_io callback
(more information has to be passed into the callback).
For SLES 11 SP1, we'll have a terrible hack so that KABI is preserved
but what should we do for 11.3? Do we take KABI issues there seriously
enough that it warranties doing the same hack or can we afford to change
the KABI?
Honza
--
Jan Kara