From: Greg KH <greg@kroah.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Sasha Levin <sashal@kernel.org>, Chuck Lever <cel@kernel.org>,
linux-stable <stable@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Petr Vorel <pvorel@suse.cz>, Sherry Yang <sherry.yang@oracle.com>,
Calum Mackay <calum.mackay@oracle.com>,
"kernel-team@fb.com" <kernel-team@fb.com>,
"ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [PATCH 6.1.y 00/18] Backport "make svc_stat per-net instead of global"
Date: Mon, 12 Aug 2024 16:02:39 +0200 [thread overview]
Message-ID: <2024081214-sizzle-repave-65f5@gregkh> (raw)
In-Reply-To: <A0BF8EAF-A16D-4200-8362-E833BA23159D@oracle.com>
On Mon, Aug 12, 2024 at 01:52:18PM +0000, Chuck Lever III wrote:
>
>
> > On Aug 12, 2024, at 7:34 AM, Sasha Levin <sashal@kernel.org> wrote:
> >
> > On Sat, Aug 10, 2024 at 03:59:51PM -0400, cel@kernel.org wrote:
> >> From: Chuck Lever <chuck.lever@oracle.com>
> >>
> >> Following up on
> >>
> >> https://lore.kernel.org/linux-nfs/d4b235df-4ee5-4824-9d48-e3b3c1f1f4d1@oracle.com/
> >>
> >> Here is a backport series targeting origin/linux-6.1.y that closes
> >> the information leak described in the above thread.
> >>
> >> I started with v6.1.y because that is the most recent LTS kernel
> >> and thus the closest to upstream. I plan to look at 5.15 and 5.10
> >> LTS too if this series is applied to v6.1.y.
> >
> > 6.6 would be the most recent LTS, and we would need to have this series
> > on top of 6.6 first before we can backport it to older trees :)
>
> Fair enough -- I was told this work was already in 6.6.y, which
> is why I started with v6.1. I'll take care of it.
Only the first few commits are in 6.6.y already, and those don't make
much sense to take into 6.1.y now as they don't do anything on their
own.
thanks,
greg k-h
next prev parent reply other threads:[~2024-08-12 14:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 19:59 [PATCH 6.1.y 00/18] Backport "make svc_stat per-net instead of global" cel
2024-08-10 19:59 ` [PATCH 6.1.y 01/18] nfsd: move reply cache initialization into nfsd startup cel
2024-08-10 19:59 ` [PATCH 6.1.y 02/18] nfsd: move init of percpu reply_cache_stats counters back to nfsd_init_net cel
2024-08-10 19:59 ` [PATCH 6.1.y 03/18] NFSD: Refactor nfsd_reply_cache_free_locked() cel
2024-08-10 19:59 ` [PATCH 6.1.y 04/18] NFSD: Rename nfsd_reply_cache_alloc() cel
2024-08-10 19:59 ` [PATCH 6.1.y 05/18] NFSD: Replace nfsd_prune_bucket() cel
2024-08-10 19:59 ` [PATCH 6.1.y 06/18] NFSD: Refactor the duplicate reply cache shrinker cel
2024-08-10 19:59 ` [PATCH 6.1.y 07/18] NFSD: Rewrite synopsis of nfsd_percpu_counters_init() cel
2024-08-10 19:59 ` [PATCH 6.1.y 08/18] NFSD: Fix frame size warning in svc_export_parse() cel
2024-08-10 20:00 ` [PATCH 6.1.y 09/18] sunrpc: don't change ->sv_stats if it doesn't exist cel
2024-08-10 20:00 ` [PATCH 6.1.y 10/18] nfsd: stop setting ->pg_stats for unused stats cel
2024-08-10 20:00 ` [PATCH 6.1.y 11/18] sunrpc: pass in the sv_stats struct through svc_create_pooled cel
2024-08-10 20:00 ` [PATCH 6.1.y 12/18] sunrpc: remove ->pg_stats from svc_program cel
2024-08-10 20:00 ` [PATCH 6.1.y 13/18] sunrpc: use the struct net as the svc proc private cel
2024-08-10 20:00 ` [PATCH 6.1.y 14/18] nfsd: rename NFSD_NET_* to NFSD_STATS_* cel
2024-08-10 20:00 ` [PATCH 6.1.y 15/18] nfsd: expose /proc/net/sunrpc/nfsd in net namespaces cel
2024-08-10 20:00 ` [PATCH 6.1.y 16/18] nfsd: make all of the nfsd stats per-network namespace cel
2024-08-10 20:00 ` [PATCH 6.1.y 17/18] nfsd: remove nfsd_stats, make th_cnt a global counter cel
2024-08-10 20:00 ` [PATCH 6.1.y 18/18] nfsd: make svc_stat per-network namespace instead of global cel
2024-08-12 11:34 ` [PATCH 6.1.y 00/18] Backport "make svc_stat per-net instead of global" Sasha Levin
2024-08-12 13:52 ` Chuck Lever III
2024-08-12 14:02 ` Greg KH [this message]
2024-08-15 8:27 ` Greg KH
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=2024081214-sizzle-repave-65f5@gregkh \
--to=greg@kroah.com \
--cc=calum.mackay@oracle.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kernel-team@fb.com \
--cc=linux-nfs@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=sashal@kernel.org \
--cc=sherry.yang@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).