From: Vitaly Wool <vitalywool@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Markus Linnala <markus.linnala@gmail.com>,
stable@kernel.org, Dan Streetman <ddstreet@ieee.org>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] z3fold: claim page in the beginning of free
Date: Fri, 27 Sep 2019 09:19:02 +0200 [thread overview]
Message-ID: <CAMJBoFMGx5Boj_FBKGzG9Xa3jBNwMaGkHztKpMX9rQfG0VN7+w@mail.gmail.com> (raw)
In-Reply-To: <20190926154834.132f40363f5805a7a5cb347a@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
Den fre 27 sep. 2019 00:48Andrew Morton <akpm@linux-foundation.org> skrev:
> On Thu, 26 Sep 2019 10:48:44 +0200 Vitaly Wool <vitalywool@gmail.com>
> wrote:
>
> > There's a really hard to reproduce race in z3fold between
> > z3fold_free() and z3fold_reclaim_page(). z3fold_reclaim_page()
> > can claim the page after z3fold_free() has checked if the page
> > was claimed and z3fold_free() will then schedule this page for
> > compaction which may in turn lead to random page faults (since
> > that page would have been reclaimed by then). Fix that by
> > claiming page in the beginning of z3fold_free().
> >
>
> I take it from the email headers that a
>
> Cc: <stable@vger.kernel.org>
>
> was intended?
>
Oh yes, thanks!
~Vitaly
>
[-- Attachment #2: Type: text/html, Size: 1520 bytes --]
prev parent reply other threads:[~2019-09-27 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 8:48 Vitaly Wool
2019-09-26 22:48 ` Andrew Morton
2019-09-27 7:19 ` Vitaly Wool [this message]
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=CAMJBoFMGx5Boj_FBKGzG9Xa3jBNwMaGkHztKpMX9rQfG0VN7+w@mail.gmail.com \
--to=vitalywool@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=markus.linnala@gmail.com \
--cc=stable@kernel.org \
--cc=vbabka@suse.cz \
/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