linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Kairui Song <ryncsn@gmail.com>
Cc: Baoquan He <bhe@redhat.com>,
	linux-mm@kvack.org, Hugh Dickins <hughd@google.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Kemeng Shi <shikemeng@huaweicloud.com>,
	Chris Li <chrisl@kernel.org>, Nhat Pham <nphamcs@gmail.com>,
	Barry Song <baohua@kernel.org>,
	Usama Arif <usamaarif642@gmail.com>,
	linux-kernel@vger.kernel.org, Colin Cross <ccross@android.com>
Subject: Re: [PATCH v3] mm/shmem, swap: fix softlockup with mTHP swapin
Date: Wed, 11 Jun 2025 18:15:31 -0700	[thread overview]
Message-ID: <20250611181531.004a7ba771393843dda5ee64@linux-foundation.org> (raw)
In-Reply-To: <CAMgjq7CHMHwCsWZnEPUTg2fq7wRdQAMD3ESGa+GBBp=U0Ld7ag@mail.gmail.com>

On Thu, 12 Jun 2025 00:06:56 +0800 Kairui Song <ryncsn@gmail.com> wrote:

> > > The reason is simple, readahead brought some order 0 folio in swap cache,
> > > and the swapin mTHP folio being allocated is in confict with it, so
> >                                                   ^^^typo, conflict
> >
> 
> Nice catch, thanks!
> 
> Hi Andrew, it's only one typo in the commit message here, will you
> help update the commit message while merging 

No probs.  

checkpatch can catch these things if the typo is in scripts/spelling.txt.

x1:/usr/src/linux-6.16-rc1> grep -r confict . | wc -l
5
x1:/usr/src/mm> git log | grep confict | wc -l
26

and it seems it should be!  I bet Colin can fix that for us.


  reply	other threads:[~2025-06-12  1:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 18:16 Kairui Song
2025-06-11  3:33 ` Baoquan He
2025-06-11 16:06   ` Kairui Song
2025-06-12  1:15     ` Andrew Morton [this message]
2025-06-11  6:19 ` Baolin Wang

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=20250611181531.004a7ba771393843dda5ee64@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=bhe@redhat.com \
    --cc=ccross@android.com \
    --cc=chrisl@kernel.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nphamcs@gmail.com \
    --cc=ryncsn@gmail.com \
    --cc=shikemeng@huaweicloud.com \
    --cc=usamaarif642@gmail.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