From: Jerome Marchand <jmarchan@redhat.com>
To: Simon Jeons <simon.jeons@gmail.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Mel Gorman <mgorman@suse.de>
Subject: Re: [PATCH] swap: redirty page if page write fails on swap file
Date: Fri, 03 May 2013 11:12:44 +0200 [thread overview]
Message-ID: <51837F8C.4080801@redhat.com> (raw)
In-Reply-To: <5180C6C1.6010000@gmail.com>
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
>>> 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.
>>> This patch sets the page dirty when direct_IO() fails. It fixes a memory
>>
>> If swapfile has related page cache which cached swapfile in memory? It
>> is not necessary, correct?
I'm not sure I understand the question. What I can tell you is that it is
necessary if the swapfile is located on a fs that uses swap_activate (only
NFS so far). Other swap file hasn't been impacted by commit 62c230b.
>>
>>> corruption that happened while using swap-over-NFS.
>>>
>>> Signed-off-by: Jerome Marchand <jmarchan@redhat.com>
>>> ---
>>> mm/page_io.c | 2 ++
>>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/mm/page_io.c b/mm/page_io.c
>>> index 78eee32..04ca00d 100644
>>> --- a/mm/page_io.c
>>> +++ b/mm/page_io.c
>>> @@ -222,6 +222,8 @@ int swap_writepage(struct page *page, struct
>>> writeback_control *wbc)
>>> if (ret == PAGE_SIZE) {
>>> count_vm_event(PSWPOUT);
>>> ret = 0;
>>> + } else {
>>> + set_page_dirty(page);
>>> }
>>> return ret;
>>> }
>>>
>>> --
>>> To unsubscribe, send a message with 'unsubscribe linux-mm' in
>>> the body to majordomo@kvack.org. For more info on Linux MM,
>>> see: http://www.linux-mm.org/ .
>>> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Marchand <jmarchan@redhat.com>
To: Simon Jeons <simon.jeons@gmail.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Mel Gorman <mgorman@suse.de>
Subject: Re: [PATCH] swap: redirty page if page write fails on swap file
Date: Fri, 03 May 2013 11:12:44 +0200 [thread overview]
Message-ID: <51837F8C.4080801@redhat.com> (raw)
In-Reply-To: <5180C6C1.6010000@gmail.com>
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
>>> 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.
>>> This patch sets the page dirty when direct_IO() fails. It fixes a memory
>>
>> If swapfile has related page cache which cached swapfile in memory? It
>> is not necessary, correct?
I'm not sure I understand the question. What I can tell you is that it is
necessary if the swapfile is located on a fs that uses swap_activate (only
NFS so far). Other swap file hasn't been impacted by commit 62c230b.
>>
>>> corruption that happened while using swap-over-NFS.
>>>
>>> Signed-off-by: Jerome Marchand <jmarchan@redhat.com>
>>> ---
>>> mm/page_io.c | 2 ++
>>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/mm/page_io.c b/mm/page_io.c
>>> index 78eee32..04ca00d 100644
>>> --- a/mm/page_io.c
>>> +++ b/mm/page_io.c
>>> @@ -222,6 +222,8 @@ int swap_writepage(struct page *page, struct
>>> writeback_control *wbc)
>>> if (ret == PAGE_SIZE) {
>>> count_vm_event(PSWPOUT);
>>> ret = 0;
>>> + } else {
>>> + set_page_dirty(page);
>>> }
>>> return ret;
>>> }
>>>
>>> --
>>> To unsubscribe, send a message with 'unsubscribe linux-mm' in
>>> the body to majordomo@kvack.org. For more info on Linux MM,
>>> see: http://www.linux-mm.org/ .
>>> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>>
>
next prev parent reply other threads:[~2013-05-03 9:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 12:11 [PATCH] swap: redirty page if page write fails on swap file Jerome Marchand
2013-04-17 12:11 ` Jerome Marchand
2013-04-17 15:07 ` Johannes Weiner
2013-04-17 15:07 ` Johannes Weiner
2013-04-17 15:08 ` Mel Gorman
2013-04-17 15:08 ` Mel Gorman
2013-04-18 0:13 ` Simon Jeons
2013-04-18 0:13 ` Simon Jeons
2013-05-01 7:39 ` Simon Jeons
2013-05-01 7:39 ` Simon Jeons
2013-05-03 9:12 ` Jerome Marchand [this message]
2013-05-03 9:12 ` Jerome Marchand
2013-04-22 20:37 ` Andrew Morton
2013-04-22 20:37 ` Andrew Morton
2013-04-24 9:57 ` Jerome Marchand
2013-04-24 9:57 ` Jerome Marchand
2013-05-01 7:38 ` Will Huck
2013-05-01 7:38 ` Will Huck
2013-04-24 18:57 ` [PATCH] mm: swap: Mark swap pages writeback before queueing for direct IO Mel Gorman
2013-04-24 18:57 ` Mel Gorman
2013-04-24 19:23 ` Andrew Morton
2013-04-24 19:23 ` Andrew Morton
2013-04-25 8:53 ` Mel Gorman
2013-04-25 8:53 ` Mel Gorman
2013-05-01 6:58 ` Ric Mason
2013-05-01 6:58 ` Ric Mason
2013-05-01 8:20 ` Mel Gorman
2013-05-01 8:20 ` Mel Gorman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51837F8C.4080801@redhat.com \
--to=jmarchan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=simon.jeons@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.