mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: m.szyprowski@samsung.com, qcai@redhat.com, dchinner@redhat.com,
	hannes@cmpxchg.org, hch@lst.de, hughd@google.com, jack@suse.cz,
	kirill.shutemov@linux.intel.com, mm-commits@vger.kernel.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, william.kucharski@oracle.com,
	willy@infradead.org, yang.shi@linux.alibaba.com
Subject: Re: + mm-truncateshmem-handle-truncates-that-split-thps-fix-fix.patch added to -mm tree
Date: Thu, 3 Dec 2020 14:04:18 -0800 (PST)	[thread overview]
Message-ID: <alpine.LSU.2.11.2012031348120.12944@eggly.anvils> (raw)
In-Reply-To: <20201126054713.GmEiU5MZ_%akpm@linux-foundation.org>

On Wed, 25 Nov 2020, akpm@linux-foundation.org wrote:
> 
> The patch titled
>      Subject: mm-truncateshmem-handle-truncates-that-split-thps-fix-fix
> has been added to the -mm tree.  Its filename is
>      mm-truncateshmem-handle-truncates-that-split-thps-fix-fix.patch

Andrew, Stephen,

This lot is proving to be a work in progress,
the current state breaks booting on 32-bit, livelocks trinity,
and breaks shmem in more ways than I can quickly explain.
Please revert (in reverse order):

mm-truncateshmem-handle-truncates-that-split-thps.patch
mm-truncateshmem-handle-truncates-that-split-thps-fix.patch
mm-truncateshmem-handle-truncates-that-split-thps-fix-fix.patch
mm-filemap-return-only-head-pages-from-find_get_entries.patch

(I don't think there's any problem with that last patch, but
assume that it relies on ..split-thpfs.patch being in already.)

Thanks,
Hugh

       reply	other threads:[~2020-12-03 22:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201126054713.GmEiU5MZ_%akpm@linux-foundation.org>
2020-12-03 22:04 ` Hugh Dickins [this message]
2020-12-03 22:34   ` Stephen Rothwell

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=alpine.LSU.2.11.2012031348120.12944@eggly.anvils \
    --to=hughd@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=dchinner@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=qcai@redhat.com \
    --cc=sfr@canb.auug.org.au \
    --cc=william.kucharski@oracle.com \
    --cc=willy@infradead.org \
    --cc=yang.shi@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®