From: David Hildenbrand <david@redhat.com>
To: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>,
"Miaohe Lin" <linmiaohe@huawei.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>,
"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: Mon, 25 Apr 2022 09:45:31 +0200 [thread overview]
Message-ID: <febd6309-b2a5-ef79-daa2-8000af09e291@redhat.com> (raw)
In-Reply-To: <20220425010804.GA3746096@hori.linux.bs1.fc.nec.co.jp>
On 25.04.22 03:08, 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>
>
> Hi Miaohe,
>
> This bug sounds relatively serious to me, and it seems old, so is it worth
> sending to -stable?
I'm not sure if this is worth -stable, but no strong opinion.
The do_swap_page() part was added in 2005:
commit b81074800b98ac50b64d4c8d34e8abf0fda5e3d1
Author: Kirill Korotaev <dev@sw.ru>
Date: Mon May 16 21:53:50 2005 -0700
[PATCH] do_swap_page() can map random data if swap read fails
There is a bug in do_swap_page(): when swap page happens to be unreadable,
page filled with random data is mapped into user address space. The fix is
to check for PageUptodate and send SIGBUS in case of error.
Signed-Off-By: Kirill Korotaev <dev@sw.ru>
Signed-Off-By: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Acked-by: Hugh Dickins <hugh@veritas.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
So the do_swap_page() part has been fixed for quite a while already.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-04-25 7:46 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 [this message]
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
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=febd6309-b2a5-ef79-daa2-8000af09e291@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=dhowells@redhat.com \
--cc=linmiaohe@huawei.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
all inboxes | Powered by JetHome®