From: Greg KH <gregkh@linuxfoundation.org>
To: Kalesh Singh <kaleshsingh@google.com>
Cc: stable@vger.kernel.org,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Charan Teja Kalla <quic_charante@quicinc.com>,
Yu Zhao <yuzhao@google.com>,
Aneesh Kumar K V <aneesh.kumar@linux.ibm.com>,
Barry Song <baohua@kernel.org>, Brian Geffon <bgeffon@google.com>,
Jan Alexander Steffens <heftig@archlinux.org>,
Lecopzer Chen <lecopzer.chen@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Oleksandr Natalenko <oleksandr@natalenko.name>,
Qi Zheng <zhengqi.arch@bytedance.com>,
Steven Barrett <steven@liquorix.net>,
Suleiman Souhlal <suleiman@google.com>,
Suren Baghdasaryan <surenb@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 6.1.y] Multi-gen LRU: avoid race in inc_min_seq()
Date: Sat, 16 Sep 2023 13:38:08 +0200 [thread overview]
Message-ID: <2023091658-cinnamon-storage-74eb@gregkh> (raw)
In-Reply-To: <20230913211256.2552031-1-kaleshsingh@google.com>
On Wed, Sep 13, 2023 at 02:12:56PM -0700, Kalesh Singh wrote:
> inc_max_seq() will try to inc_min_seq() if nr_gens == MAX_NR_GENS. This
> is because the generations are reused (the last oldest now empty
> generation will become the next youngest generation).
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-09-16 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 19:06 FAILED: patch "[PATCH] Multi-gen LRU: avoid race in inc_min_seq()" failed to apply to 6.1-stable tree gregkh
2023-09-13 21:12 ` [PATCH 6.1.y] Multi-gen LRU: avoid race in inc_min_seq() Kalesh Singh
2023-09-16 11:38 ` 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=2023091658-cinnamon-storage-74eb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=baohua@kernel.org \
--cc=bgeffon@google.com \
--cc=heftig@archlinux.org \
--cc=kaleshsingh@google.com \
--cc=lecopzer.chen@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=oleksandr@natalenko.name \
--cc=quic_charante@quicinc.com \
--cc=stable@vger.kernel.org \
--cc=steven@liquorix.net \
--cc=suleiman@google.com \
--cc=surenb@google.com \
--cc=yuzhao@google.com \
--cc=zhengqi.arch@bytedance.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