From: Sasha Levin <sashal@kernel.org>
To: Hugh Dickins <hughd@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Matthew Wilcox <willy@infradead.org>,
Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
Jerome Glisse <jglisse@redhat.com>,
Mike Rapoport <rppt@linux.ibm.com>,
stable@vger.kernel.org
Subject: Re: stable backports of 4.20-rc5 huge_memory,khugepaged fixes
Date: Sun, 2 Dec 2018 03:30:18 -0500 [thread overview]
Message-ID: <20181202083018.GB221015@sasha-vm> (raw)
In-Reply-To: <alpine.LSU.2.11.1812010758160.4515@eggly.anvils>
On Sat, Dec 01, 2018 at 08:36:54AM -0800, Hugh Dickins wrote:
>Hi Greg,
>
>As promised, attached are three tarfiles of patches for stable,
>spliced together from the final messages that went into Linus's tree
>yesterday, and the patches I had prepared earlier against 4.19, 4.14
>and 4.9 stable trees (no clashes have come in since): required since
>most of the the upstream commits involve intervening XArray changes
>(particularly the "stop if punched or truncated" one).
>
>FYI Konstantin, the 4.14 and 4.9 also add your old
>commit 605ca5ede7643a01f4c4a15913f9714ac297f8a6 upstream,
>mm/huge_memory.c: reorder operations in __split_huge_page_tail()
>which I needed before one of mine, and wanted to have in stable anyway.
>
>FYI Mike, the 4.9 also adds your old
>commit b1cc94ab2f2ba31fcb2c59df0b9cf03f6d720553 upstream,
>shmem: shmem_charge: verify max_block is not exceeded before inode update
>and
>commit 0f0796945614b7523987f7eea32407421af4b1ee upstream,
>shmem: introduce shmem_inode_acct_block
>which I needed before one of mine (but I cut out the userfaultfd hunks).
>
>Thanks,
>Hugh
I've queued them up, thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2018-12-02 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 16:36 stable backports of 4.20-rc5 huge_memory,khugepaged fixes Hugh Dickins
2018-12-02 8:30 ` Sasha Levin [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=20181202083018.GB221015@sasha-vm \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=jglisse@redhat.com \
--cc=khlebnikov@yandex-team.ru \
--cc=kirill.shutemov@linux.intel.com \
--cc=rppt@linux.ibm.com \
--cc=stable@vger.kernel.org \
--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