linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux-MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Mel Gorman <mgorman@techsingularity.net>
Subject: [GIT PULL] mm/compaction functional fixes for v5.1-rc4
Date: Fri,  5 Apr 2019 14:51:18 +0100	[thread overview]
Message-ID: <20190405135120.27532-1-mgorman@techsingularity.net> (raw)

The following changes since commit 79a3aaa7b82e3106be97842dedfd8429248896e6:

  Linux 5.1-rc3 (2019-03-31 14:39:29 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git tags/mm-compaction-5.1-rc4

for you to fetch changes up to 5b56d996dd50a9d2ca87c25ebb50c07b255b7e04:

  mm/compaction.c: abort search if isolation fails (2019-04-04 11:56:15 +0100)

----------------

Hi Linus,

The merge window for 5.1 introduced a number of compaction-related patches
authored by myself.  There are intermittent reports of corruption and
functional issues based on them due to sloppy checking of zone boundaries
and a corner case where the free lists are overrun.

Reports are not common but at least two users and 0-day have tripped over them.
There is a chance that one of the syzbot reports are related but it has not
been confirmed properly.

The normal submission path is through Andrew but it's now late on a Friday
and I do not know if a round of updates are coming your way or not and
these patches have been floating around for a while. Given the nature
of the fixes, I really would prefer to avoid another RC with corruption
issues creating duplicate reports.

All of these have been successfully tested on older RC windows. This will
make this branch look like a rebase but they've simply been cherry-picked
from Andrew's tree and placed on a fresh branch. I've no reason to
believe that this has invalidated the testing given the lack of change
in compaction and the nature of the fixes.

Note that you may still receive these from Andrew and there are other
compaction-related fixes in his tree that are less critical. I do not
expect them to conflict but there is a non-zero risk of confusion. If
you get a bunch of patches from Andrew then please ignore this entirely
so the normal submission path is preserved. Otherwise, please either git
pull this or pick up the patches directly at your discretion.

Mel Gorman (1):
  mm/compaction.c: correct zone boundary handling when resetting
    pageblock skip hints

Qian Cai (1):
  mm/compaction.c: abort search if isolation fails

 mm/compaction.c | 29 ++++++++++++++++++-----------
 1 file changed, 18 insertions(+), 11 deletions(-)

-- 
2.16.4


             reply	other threads:[~2019-04-05 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05 13:51 Mel Gorman [this message]
2019-04-05 13:51 ` [PATCH 1/2] mm/compaction.c: correct zone boundary handling when resetting pageblock skip hints Mel Gorman
2019-04-05 13:51 ` [PATCH 2/2] mm/compaction.c: abort search if isolation fails Mel Gorman
2019-04-05 16:15 ` [GIT PULL] mm/compaction functional fixes for v5.1-rc4 pr-tracker-bot

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=20190405135120.27532-1-mgorman@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@linuxfoundation.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