From: Miaohe Lin <linmiaohe@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <vitaly.wool@konsulko.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/9] A few fixup patches for z3fold
Date: Wed, 18 May 2022 10:01:41 +0800 [thread overview]
Message-ID: <6f42e812-ab51-9b24-13f2-2493b917cb98@huawei.com> (raw)
In-Reply-To: <20220517164553.29d6b76eb0cc656556916372@linux-foundation.org>
On 2022/5/18 7:45, Andrew Morton wrote:
> On Fri, 29 Apr 2022 14:40:42 +0800 Miaohe Lin <linmiaohe@huawei.com> wrote:
>
>> This series contains a few fixup patches to fix sheduling while atomic,
>> fix possible null pointer dereferencing, fix various race conditions and
>> so on. More details can be found in the respective changelogs.
>
> We haven't heard from Vitaly but this series has been in mm-unstable
I will be really grateful if Vitaly has the time to review. :)
> and linux-next for three weeks, so I plan to move it into mm-stable
> later this week.
Thanks!
> .
>
next prev parent reply other threads:[~2022-05-18 2:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 6:40 [PATCH 0/9] A few fixup patches for z3fold Miaohe Lin
2022-04-29 6:40 ` [PATCH 1/9] mm/z3fold: fix sheduling while atomic Miaohe Lin
2022-05-19 7:00 ` Vitaly Wool
2022-04-29 6:40 ` [PATCH 2/9] mm/z3fold: fix possible null pointer dereferencing Miaohe Lin
2022-05-19 7:04 ` Vitaly Wool
2022-04-29 6:40 ` [PATCH 3/9] mm/z3fold: remove buggy use of stale list for allocation Miaohe Lin
2022-05-19 7:06 ` Vitaly Wool
2022-04-29 6:40 ` [PATCH 4/9] mm/z3fold: throw warning on failure of trylock_page in z3fold_alloc Miaohe Lin
2022-05-19 7:10 ` Vitaly Wool
2022-05-19 11:10 ` Miaohe Lin
2022-04-29 6:40 ` [PATCH 5/9] revert "mm/z3fold.c: allow __GFP_HIGHMEM in z3fold_alloc" Miaohe Lin
2022-05-19 7:12 ` Vitaly Wool
2022-05-19 11:34 ` Miaohe Lin
2022-05-19 18:31 ` Andrew Morton
2022-05-20 2:30 ` Miaohe Lin
2022-04-29 6:40 ` [PATCH 6/9] mm/z3fold: put z3fold page back into unbuddied list when reclaim or migration fails Miaohe Lin
2022-05-19 7:13 ` Vitaly Wool
2022-04-29 6:40 ` [PATCH 7/9] mm/z3fold: always clear PAGE_CLAIMED under z3fold page lock Miaohe Lin
2022-05-19 7:14 ` Vitaly Wool
2022-04-29 6:40 ` [PATCH 8/9] mm/z3fold: fix z3fold_reclaim_page races with z3fold_free Miaohe Lin
2022-05-19 7:24 ` Vitaly Wool
2022-04-29 6:40 ` [PATCH 9/9] mm/z3fold: fix z3fold_page_migrate races with z3fold_map Miaohe Lin
2022-05-19 7:28 ` Vitaly Wool
2022-05-17 23:45 ` [PATCH 0/9] A few fixup patches for z3fold Andrew Morton
2022-05-18 2:01 ` Miaohe Lin [this message]
2022-05-18 10:39 ` Vitaly Wool
2022-05-19 1:54 ` 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=6f42e812-ab51-9b24-13f2-2493b917cb98@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vitaly.wool@konsulko.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.