From: Dominique Martinet <dominique.martinet@atmark-techno.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, "Jamal Hadi Salim" <jhs@mojatatu.com>,
"Cong Wang" <xiyou.wangcong@gmail.com>,
"Jiri Pirko" <jiri@resnulli.us>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Mat Martineau" <mathew.j.martineau@linux.intel.com>,
"Paolo Abeni" <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rajat Gupta" <rajat.gupta@oss.qualcomm.com>,
"Yiming Qian" <yimingqian591@gmail.com>,
"Keenan Dong" <keenanat2000@gmail.com>,
"Han Guidong" <2045gemini@gmail.com>,
"Zhang Cen" <rollkingzzc@gmail.com>,
"Davide Caratti" <dcaratti@redhat.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Victor Nogueira" <victor@mojatatu.com>
Subject: Re: [PATCH 5.10.y] net/sched: fix pedit partial COW leading to page cache corruption
Date: Thu, 2 Jul 2026 10:00:30 +0900 [thread overview]
Message-ID: <akW4LleEw9axSYaB@atmark-techno.com> (raw)
In-Reply-To: <stable-reply-pedit-cow-510-20260701193800@kernel.org>
Sasha Levin wrote on Wed, Jul 01, 2026 at 08:38:34PM -0400:
> > [Dominique: plenty of context conflict but the code itself could still
> > mostly be used]
>
> Thanks! However, the same upstream fix (899ee91156e5) is already queued for
> 5.10.y via Wentao Guan's backport, which brings in the act_pedit
> RCU/percpu-stats prerequisites first and then applies the fix nearly
> verbatim.
Oh, thanks!
Sorry for the noise, I'll remember to check next time.
--
Dominique
prev parent reply other threads:[~2026-07-02 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260630-cve-2026-46331-v1-1-c1986f356f26@atmark-techno.com>
2026-06-30 8:27 ` [PATCH 5.10.y] net/sched: fix pedit partial COW leading to page cache corruption Dominique Martinet
2026-07-02 0:38 ` Sasha Levin
2026-07-02 1:00 ` Dominique Martinet [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=akW4LleEw9axSYaB@atmark-techno.com \
--to=dominique.martinet@atmark-techno.com \
--cc=2045gemini@gmail.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=keenanat2000@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rajat.gupta@oss.qualcomm.com \
--cc=rollkingzzc@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=toke@redhat.com \
--cc=victor@mojatatu.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yimingqian591@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