From: Miaohe Lin <linmiaohe@huawei.com>
To: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"willy@infradead.org" <willy@infradead.org>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"dhowells@redhat.com" <dhowells@redhat.com>,
"neilb@suse.de" <neilb@suse.de>,
"david@redhat.com" <david@redhat.com>,
"apopple@nvidia.com" <apopple@nvidia.com>,
"surenb@google.com" <surenb@google.com>,
"minchan@kernel.org" <minchan@kernel.org>,
"peterx@redhat.com" <peterx@redhat.com>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] mm/swapfile: unuse_pte can map random data if swap read fails
Date: Tue, 10 May 2022 14:58:05 +0800 [thread overview]
Message-ID: <2a95aebe-3a00-4699-12d4-fc5d934dde2c@huawei.com> (raw)
In-Reply-To: <20220510061712.GA162496@hori.linux.bs1.fc.nec.co.jp>
On 2022/5/10 14:17, HORIGUCHI NAOYA(堀口 直也) wrote:
> On Sun, Apr 24, 2022 at 05:11:03PM +0800, Miaohe Lin wrote:
>> There is a bug in unuse_pte(): when swap page happens to be unreadable,
>> page filled with random data is mapped into user address space. In case
>> of error, a special swap entry indicating swap read fails is set to the
>> page table. So the swapcache page can be freed and the user won't end up
>> with a permanently mounted swap because a sector is bad. And if the page
>> is accessed later, the user process will be killed so that corrupted data
>> is never consumed. On the other hand, if the page is never accessed, the
>> user won't even notice it.
>>
>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>> Acked-by: David Hildenbrand <david@redhat.com>
>
> When I reproduced the issue (generated read error with dm-dust), I saw
> infinite loop in the while loop in shmem_unuse_inode() (and this happens
> even with this patch). I confirmed that shmem_swapin_page() returns -EIO,
> but shmem_unuse_swap_entries() does not return the error to the callers,
> so the while loop in shmem_unuse_inode() seems not break.
>
Many thanks for your report! I didn't test the shmem case because I saw -EIO
is returned. So I just focus on the normal page case. Sorry about it. :(
> So maybe you need more code around shmem_unuse_inode() to handle the error?
I will try to reproduce it and come up a fixup patch asap! And if you like, you
can kindly solve this issue too. ;)
Thanks a lot!
>
> Thanks,
> Naoya Horiguchi
>
next prev parent reply other threads:[~2022-05-10 6:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 9:11 [PATCH v3 0/3] A few fixup patches for mm Miaohe Lin
2022-04-24 9:11 ` [PATCH v3 1/3] mm/swapfile: unuse_pte can map random data if swap read fails Miaohe Lin
2022-04-25 1:08 ` HORIGUCHI NAOYA(堀口 直也)
2022-04-25 2:20 ` Miaohe Lin
2022-04-25 2:51 ` HORIGUCHI NAOYA(堀口 直也)
2022-04-25 3:10 ` Miaohe Lin
2022-04-25 7:45 ` David Hildenbrand
2022-04-25 8:47 ` Miaohe Lin
2022-04-26 0:31 ` HORIGUCHI NAOYA(堀口 直也)
2022-04-26 7:06 ` Miaohe Lin
2022-04-25 7:41 ` ying.huang
2022-04-25 7:49 ` David Hildenbrand
2022-04-25 7:55 ` ying.huang
2022-04-25 8:01 ` David Hildenbrand
2022-04-25 8:51 ` Miaohe Lin
2022-05-10 6:17 ` HORIGUCHI NAOYA(堀口 直也)
2022-05-10 6:58 ` Miaohe Lin [this message]
2022-05-13 0:42 ` Andrew Morton
2022-05-13 3:14 ` Miaohe Lin
2022-05-10 12:46 ` Miaohe Lin
2022-04-24 9:11 ` [PATCH v3 2/3] mm/swapfile: Fix lost swap bits in unuse_pte() Miaohe Lin
2022-04-25 7:39 ` David Hildenbrand
2022-04-24 9:11 ` [PATCH v3 3/3] mm/madvise: free hwpoison and swapin error entry in madvise_free_pte_range Miaohe Lin
2022-04-24 23:41 ` HORIGUCHI NAOYA(堀口 直也)
2022-04-25 1:59 ` Miaohe Lin
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=2a95aebe-3a00-4699-12d4-fc5d934dde2c@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=naoya.horiguchi@nec.com \
--cc=neilb@suse.de \
--cc=peterx@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox