linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kairui Song <ryncsn@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Minchan Kim <minchan@kernel.org>,
	David Hildenbrand <david@redhat.com>,
	linux-mm@kvack.org,  "Huang, Ying" <ying.huang@intel.com>,
	Chris Li <chrisl@kernel.org>, Yu Zhao <yuzhao@google.com>,
	 Barry Song <v-songbaohua@oppo.com>,
	SeongJae Park <sj@kernel.org>, Hugh Dickins <hughd@google.com>,
	 Johannes Weiner <hannes@cmpxchg.org>,
	Matthew Wilcox <willy@infradead.org>,
	Michal Hocko <mhocko@suse.com>,
	 Yosry Ahmed <yosryahmed@google.com>,
	stable@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/swap: fix race when skipping swapcache
Date: Fri, 16 Feb 2024 18:01:53 +0800	[thread overview]
Message-ID: <CAMgjq7DhRu0qAgLY_cw-WuWmx9vchOAN0MeumRtCLFtoD3Kz8Q@mail.gmail.com> (raw)
In-Reply-To: <20240215145836.6db8f62824e1547f0608591c@linux-foundation.org>

On Fri, Feb 16, 2024 at 6:58 AM Andrew Morton <akpm@linux-foundation.org> wrote:
> On Thu, 15 Feb 2024 12:55:11 -0800 Minchan Kim <minchan@kernel.org> wrote:
> > Only concern of the approach is that it would be harder to have the fix
> > in the stable tree. If there isn't strong objection, I prefer the
> > Kairui's orginal solution(with some tweak of scheduler if it's
> > necessary) first and then pursue your idea on latest tree.
>
> Do we agree that this fix is needed in -stable?  For some reason I
> don't have a cc:stable in the changelog.
>
> I'd like to move this patch into mm-hotfixes-stable in order to get it
> upstream very soon.  Are we all agreeable with that?  I don't have an
> Acked-by: David?
>
> I have a note (which dates back to an earlier version) that Barry would
> be performing runtime testing.  Has that occurred?
>
> Thanks.
>

Hi Andrew,

I think this fix is needed for stable, I've sent V3, if we agree on
that, please consider V3 which includes changes we have discussed so
far, thanks!


  reply	other threads:[~2024-02-16 10:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 18:25 Kairui Song
2024-02-06 18:44 ` SeongJae Park
2024-02-06 23:02 ` Minchan Kim
2024-02-07  3:22   ` Kairui Song
2024-02-06 23:10 ` Chris Li
2024-02-06 23:40   ` Barry Song
2024-02-07  2:03     ` Chris Li
2024-02-07  2:20       ` Kairui Song
2024-02-07  1:52         ` Barry Song
2024-02-07  3:21           ` Kairui Song
2024-02-07  4:01         ` Chris Li
2024-02-07  4:06           ` Kairui Song
2024-02-07 18:31             ` Minchan Kim
2024-02-08  6:04               ` Kairui Song
2024-02-08  6:34                 ` Huang, Ying
2024-02-08 19:01                   ` Kairui Song
2024-02-08 19:42                     ` Chris Li
2024-02-09  5:30                       ` Kairui Song
2024-02-12 19:53                         ` Kairui Song
2024-02-15  0:44                           ` Minchan Kim
2024-02-15 19:07                             ` Kairui Song
2024-02-19  5:42                     ` Huang, Ying
2024-02-08  7:16                 ` Barry Song
2024-02-07  2:08     ` Huang, Ying
2024-02-07  2:28       ` Kairui Song
2024-02-07  3:44         ` Huang, Ying
2024-02-07  3:45         ` Barry Song
2024-02-07  4:16           ` Huang, Ying
2024-02-07  4:24             ` Barry Song
2024-02-15 15:36 ` David Hildenbrand
2024-02-15 18:49   ` Kairui Song
2024-02-15 20:03     ` David Hildenbrand
2024-02-15 20:55       ` Minchan Kim
2024-02-15 22:58         ` Andrew Morton
2024-02-16 10:01           ` Kairui Song [this message]
2024-02-16  7:11       ` Kairui Song
2024-02-16 16:16         ` David Hildenbrand

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=CAMgjq7DhRu0qAgLY_cw-WuWmx9vchOAN0MeumRtCLFtoD3Kz8Q@mail.gmail.com \
    --to=ryncsn@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=chrisl@kernel.org \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=minchan@kernel.org \
    --cc=sj@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=v-songbaohua@oppo.com \
    --cc=willy@infradead.org \
    --cc=ying.huang@intel.com \
    --cc=yosryahmed@google.com \
    --cc=yuzhao@google.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