From: Minchan Kim <minchan@kernel.org>
To: Vinayak Menon <vinmenon@codeaurora.org>
Cc: linux-mm@kvack.org, kernel-team@android.com,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH] mm: do not free shared swap slots
Date: Tue, 29 Oct 2019 17:24:47 -0700 [thread overview]
Message-ID: <20191030002447.GB175126@google.com> (raw)
In-Reply-To: <1571743294-14285-1-git-send-email-vinmenon@codeaurora.org>
On Tue, Oct 22, 2019 at 04:51:34PM +0530, Vinayak Menon wrote:
> The following race is observed due to which a processes faulting
> on a swap entry, finds the page neither in swapcache nor swap. This
> causes zram to give a zero filled page that gets mapped to the
> process, resulting in a user space crash later.
>
> Consider parent and child processes Pa and Pb sharing the same swap
> slot with swap_count 2. Swap is on zram with SWP_SYNCHRONOUS_IO set.
> Virtual address 'VA' of Pa and Pb points to the shared swap entry.
>
> Pa Pb
>
> fault on VA fault on VA
> do_swap_page do_swap_page
> lookup_swap_cache fails lookup_swap_cache fails
> Pb scheduled out
> swapin_readahead (deletes zram entry)
> swap_free (makes swap_count 1)
> Pb scheduled in
> swap_readpage (swap_count == 1)
> Takes SWP_SYNCHRONOUS_IO path
> zram enrty absent
> zram gives a zero filled page
>
> Fix this by making sure that swap slot is freed only when swap count
> drops down to one.
>
> Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
> Suggested-by: Minchan Kim <minchan@google.com>
> Cc: Michal Hocko <mhocko@suse.com>
Acked-by: Minchan Kim <minchan@kernel.org>
-stable material from v4.15.
Thanks.
next prev parent reply other threads:[~2019-10-30 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 11:21 [PATCH] mm: do not free shared swap slots Vinayak Menon
2019-10-30 0:24 ` Minchan Kim [this message]
2019-10-30 10:24 ` Michal Hocko
2019-10-31 14:46 ` Minchan Kim
2019-10-31 17:15 ` Michal Hocko
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=20191030002447.GB175126@google.com \
--to=minchan@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=vinmenon@codeaurora.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