From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Hugh Dickins <hughd@google.com>,
stable@vger.kernel.org, stable-commits@vger.kernel.org,
baolin.wang@linux.alibaba.com, linux-mm@kvack.org
Subject: Re: Patch "mm: shmem: skip swapcache for swapin of synchronous swap device" has been added to the 6.13-stable tree
Date: Wed, 19 Mar 2025 06:57:56 -0700 [thread overview]
Message-ID: <2025031959-dense-surely-6975@gregkh> (raw)
In-Reply-To: <20250318165340.bd86004687ceceb03cccfe7c@linux-foundation.org>
On Tue, Mar 18, 2025 at 04:53:40PM -0700, Andrew Morton wrote:
> On Tue, 18 Mar 2025 08:28:44 -0700 (PDT) Hugh Dickins <hughd@google.com> wrote:
> > > Cc: David Hildenbrand <david@redhat.com>
> > > Cc: "Huang, Ying" <ying.huang@linux.alibaba.com>
> > > Cc: Hugh Dickins <hughd@google.com>
> > > Cc: Kairui Song <kasong@tencent.com>
> > > Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
> > > Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
> > > Cc: Ryan Roberts <ryan.roberts@arm.com>
> > > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > > Stable-dep-of: 058313515d5a ("mm: shmem: fix potential data corruption during shmem swapin")
> > > Signed-off-by: Sasha Levin <sashal@kernel.org>
> >
> > No, NAK to this one going to stable.
>
> Permanent NAK to *any* mm.git patch going to stable unless that patch's
> changelog has an explicit cc:stable.
The commit:
058313515d5a ("mm: shmem: fix potential data corruption during shmem swapin")
DID have an explicit cc: stable, and Sasha was just fixing it up as the
number of FAILED mm stable patches are pretty high.
I have dropped both of these from both queues now, thanks.
greg k-h
prev parent reply other threads:[~2025-03-19 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250318112951.2053931-1-sashal@kernel.org>
2025-03-18 15:28 ` Patch "mm: shmem: skip swapcache for swapin of synchronous swap device" has been added to the 6.13-stable tree Hugh Dickins
2025-03-18 23:53 ` Andrew Morton
2025-03-19 13:57 ` Greg KH [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=2025031959-dense-surely-6975@gregkh \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.