linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "ying.huang@intel.com" <ying.huang@intel.com>
To: Miaohe Lin <linmiaohe@huawei.com>, akpm@linux-foundation.org
Cc: willy@infradead.org, vbabka@suse.cz, dhowells@redhat.com,
	neilb@suse.de, david@redhat.com, apopple@nvidia.com,
	surenb@google.com, minchan@kernel.org,  peterx@redhat.com,
	sfr@canb.auug.org.au, naoya.horiguchi@nec.com,
	 linux-mm@kvack.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 15:41:25 +0800	[thread overview]
Message-ID: <8aeebc2f0b2a251d3d70402cd0edf063ba911013.camel@intel.com> (raw)
In-Reply-To: <20220424091105.48374-2-linmiaohe@huawei.com>

Hi, Miaohe,

On Sun, 2022-04-24 at 17:11 +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>
> ---
>  include/linux/swap.h    |  7 ++++++-
>  include/linux/swapops.h | 10 ++++++++++
>  mm/memory.c             |  5 ++++-
>  mm/swapfile.c           | 11 +++++++++++
>  4 files changed, 31 insertions(+), 2 deletions(-)
> 
> diff --git a/include/linux/swap.h b/include/linux/swap.h
> index 5553189d0215..b82c196d8867 100644
> --- a/include/linux/swap.h
> +++ b/include/linux/swap.h
> @@ -55,6 +55,10 @@ static inline int current_is_kswapd(void)
>   * actions on faults.
>   */
> 
> +#define SWP_SWAPIN_ERROR_NUM 1
> +#define SWP_SWAPIN_ERROR     (MAX_SWAPFILES + SWP_HWPOISON_NUM + \
> +			     SWP_MIGRATION_NUM + SWP_DEVICE_NUM + \
> +			     SWP_PTE_MARKER_NUM)
> 
> 

It appears wasteful to use another swap device number.  Is it possible
to use a special swap offset?  For example, 0 or -1?

Best Regards,
Huang, Ying


[snip]




  parent reply	other threads:[~2022-04-25  7:41 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 [this message]
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=8aeebc2f0b2a251d3d70402cd0edf063ba911013.camel@intel.com \
    --to=ying.huang@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=apopple@nvidia.com \
    --cc=david@redhat.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