On 05/01/2013 09:39 AM, Simon Jeons wrote:
> Ping, ;-)
> On 04/18/2013 08:13 AM, Simon Jeons wrote:
>> Hi Jerome,
>> On 04/17/2013 08:11 PM, Jerome Marchand wrote:
>>> Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
>>> However, in that case page isn't redirtied if I/O fails,
On 05/01/2013 09:39 AM, Simon Jeons wrote:
Ping, ;-)
On 04/18/2013 08:13 AM, Simon Jeons wrote:
Hi Jerome,
On 04/17/2013 08:11 PM, Jerome Marchand wrote:
Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
However, in that case page isn't redirtied if I/O fails, and is
Ping, ;-)
On 04/18/2013 08:13 AM, Simon Jeons wrote:
Hi Jerome,
On 04/17/2013 08:11 PM, Jerome Marchand wrote:
Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
However, in that case page isn't redirtied if I/O fails, and is
therefore
handled afterwards as if it has been
Hi Jerome,
On 04/24/2013 05:57 PM, Jerome Marchand wrote:
On 04/22/2013 10:37 PM, Andrew Morton wrote:
On Wed, 17 Apr 2013 14:11:55 +0200 Jerome Marchand wrote:
Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
However, in that case page isn't redirtied if I/O fails, and
Hi Jerome,
On 04/24/2013 05:57 PM, Jerome Marchand wrote:
On 04/22/2013 10:37 PM, Andrew Morton wrote:
On Wed, 17 Apr 2013 14:11:55 +0200 Jerome Marchand jmarc...@redhat.com wrote:
Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
However, in that case page isn't redirtied
Ping, ;-)
On 04/18/2013 08:13 AM, Simon Jeons wrote:
Hi Jerome,
On 04/17/2013 08:11 PM, Jerome Marchand wrote:
Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
However, in that case page isn't redirtied if I/O fails, and is
therefore
handled afterwards as if it has been
On 04/22/2013 10:37 PM, Andrew Morton wrote:
> On Wed, 17 Apr 2013 14:11:55 +0200 Jerome Marchand
> wrote:
>
>>
>> Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
>> However, in that case page isn't redirtied if I/O fails, and is therefore
>> handled afterwards as if it
On 04/22/2013 10:37 PM, Andrew Morton wrote:
On Wed, 17 Apr 2013 14:11:55 +0200 Jerome Marchand jmarc...@redhat.com
wrote:
Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
However, in that case page isn't redirtied if I/O fails, and is therefore
handled afterwards as
On Wed, 17 Apr 2013 14:11:55 +0200 Jerome Marchand wrote:
>
> Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
> However, in that case page isn't redirtied if I/O fails, and is therefore
> handled afterwards as if it has been successfully written to the swap
> file, leading
On Wed, 17 Apr 2013 14:11:55 +0200 Jerome Marchand jmarc...@redhat.com wrote:
Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
However, in that case page isn't redirtied if I/O fails, and is therefore
handled afterwards as if it has been successfully written to the swap
Hi Jerome,
On 04/17/2013 08:11 PM, Jerome Marchand wrote:
Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
However, in that case page isn't redirtied if I/O fails, and is therefore
handled afterwards as if it has been successfully written to the swap
file, leading to memory
On Wed, Apr 17, 2013 at 02:11:55PM +0200, Jerome Marchand wrote:
>
> Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
> However, in that case page isn't redirtied if I/O fails, and is therefore
> handled afterwards as if it has been successfully written to the swap
> file,
On Wed, Apr 17, 2013 at 02:11:55PM +0200, Jerome Marchand wrote:
>
> Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
> However, in that case page isn't redirtied if I/O fails, and is therefore
> handled afterwards as if it has been successfully written to the swap
> file,
Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
However, in that case page isn't redirtied if I/O fails, and is therefore
handled afterwards as if it has been successfully written to the swap
file, leading to memory corruption when the page is eventually swapped
back in.
Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
However, in that case page isn't redirtied if I/O fails, and is therefore
handled afterwards as if it has been successfully written to the swap
file, leading to memory corruption when the page is eventually swapped
back in.
On Wed, Apr 17, 2013 at 02:11:55PM +0200, Jerome Marchand wrote:
Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
However, in that case page isn't redirtied if I/O fails, and is therefore
handled afterwards as if it has been successfully written to the swap
file, leading
On Wed, Apr 17, 2013 at 02:11:55PM +0200, Jerome Marchand wrote:
Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
However, in that case page isn't redirtied if I/O fails, and is therefore
handled afterwards as if it has been successfully written to the swap
file, leading
Hi Jerome,
On 04/17/2013 08:11 PM, Jerome Marchand wrote:
Since commit 62c230b, swap_writepage() calls direct_IO on swap files.
However, in that case page isn't redirtied if I/O fails, and is therefore
handled afterwards as if it has been successfully written to the swap
file, leading to memory
18 matches
Mail list logo