From: Greg KH <gregkh@linuxfoundation.org>
To: vinmenon@codeaurora.org, akpm@linux-foundation.org,
hughd@google.com, mhocko@suse.com, minchan@google.com,
minchan@kernel.org, stable@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: FAILED: patch "[PATCH] mm/page_io.c: do not free shared swap slots" failed to apply to 4.19-stable tree
Date: Mon, 18 Nov 2019 17:40:38 +0100 [thread overview]
Message-ID: <20191118164038.GA595410@kroah.com> (raw)
In-Reply-To: <1574095036140231@kroah.com>
On Mon, Nov 18, 2019 at 05:37:16PM +0100, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 4.19-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
Note, this applies, but just breaks the build, so it needs a backport
for 4.19 if people want to see it there.
thanks,
greg k-h
> ------------------ original commit in Linus's tree ------------------
>
> >From 5df373e95689b9519b8557da7c5bd0db0856d776 Mon Sep 17 00:00:00 2001
> From: Vinayak Menon <vinmenon@codeaurora.org>
> Date: Fri, 15 Nov 2019 17:35:00 -0800
> Subject: [PATCH] mm/page_io.c: do not free shared swap slots
>
> 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.
>
> Link: http://lkml.kernel.org/r/1571743294-14285-1-git-send-email-vinmenon@codeaurora.org
> Fixes: aa8d22a11da9 ("mm: swap: SWP_SYNCHRONOUS_IO: skip swapcache only if swapped page has no other reference")
> Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
> Suggested-by: Minchan Kim <minchan@google.com>
> Acked-by: Minchan Kim <minchan@kernel.org>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Hugh Dickins <hughd@google.com>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
>
> diff --git a/mm/page_io.c b/mm/page_io.c
> index 24ee600f9131..60a66a58b9bf 100644
> --- a/mm/page_io.c
> +++ b/mm/page_io.c
> @@ -73,6 +73,7 @@ static void swap_slot_free_notify(struct page *page)
> {
> struct swap_info_struct *sis;
> struct gendisk *disk;
> + swp_entry_t entry;
>
> /*
> * There is no guarantee that the page is in swap cache - the software
> @@ -104,11 +105,10 @@ static void swap_slot_free_notify(struct page *page)
> * we again wish to reclaim it.
> */
> disk = sis->bdev->bd_disk;
> - if (disk->fops->swap_slot_free_notify) {
> - swp_entry_t entry;
> + entry.val = page_private(page);
> + if (disk->fops->swap_slot_free_notify && __swap_count(entry) == 1) {
> unsigned long offset;
>
> - entry.val = page_private(page);
> offset = swp_offset(entry);
>
> SetPageDirty(page);
>
next prev parent reply other threads:[~2019-11-18 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 16:37 FAILED: patch "[PATCH] mm/page_io.c: do not free shared swap slots" failed to apply to 4.19-stable tree gregkh
2019-11-18 16:40 ` Greg KH [this message]
2019-11-19 10:57 ` Vinayak Menon
2019-11-21 20:34 ` Greg KH
2019-11-25 16:43 ` Sasha Levin
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=20191118164038.GA595410@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=mhocko@suse.com \
--cc=minchan@google.com \
--cc=minchan@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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