From: Waiman Long <longman@redhat.com>
To: "David Wang 王标" <wangbiao3@xiaomi.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Juri Lelli" <juri.lelli@redhat.com>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Dietmar Eggemann" <dietmar.eggemann@arm.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Ben Segall" <bsegall@google.com>, "Mel Gorman" <mgorman@suse.de>,
"Daniel Bristot de Oliveira" <bristot@redhat.com>
Cc: Phil Auld <pauld@redhat.com>,
Wenjie Li <wenjieli@qti.qualcomm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: 答复: [External Mail][PATCH-tip] sched: Fix use-after-free bug in dup_user_cpus_ptr()
Date: Mon, 28 Nov 2022 10:43:09 -0500 [thread overview]
Message-ID: <f5abd919-c996-6549-8d48-a93a66daaef8@redhat.com> (raw)
In-Reply-To: <63373bf9adfc4e0abd9480d40afa2c5a@xiaomi.com>
On 11/28/22 08:34, David Wang 王标 wrote:
> Hi, Waiman
>
> We use 140 devices to test this patch 72 hours. The issue can not be reproduced. If no this patch, the issue can be reproduced.
> Could you help merge this patch to mailine?
>
> https://lore.kernel.org/all/20221125023943.1118603-1-longman@redhat.com/
>
> If this patch is applied to the maintainer's tree, we can request google to help cherrypick to ACK to fix issue.
Just want to clarify if you are testing the patch using the latest tip
tree or on top of an existing linux version without the persistent user
requested affinity patchset.
PeterZ is the scheduler maintainer who is responsible for merging
scheduler related patch. It is up to him as to when that will happen.
Cheers,
Longman
next prev parent reply other threads:[~2022-11-28 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 1:44 [PATCH-tip] sched: Fix use-after-free bug in dup_user_cpus_ptr() Waiman Long
2022-11-28 13:34 ` 答复: [External Mail][PATCH-tip] " David Wang 王标
2022-11-28 15:43 ` Waiman Long [this message]
2022-11-29 3:11 ` 答复: " David Wang 王标
2022-12-01 13:44 ` [PATCH-tip] " Will Deacon
2022-12-01 17:03 ` Waiman Long
2022-12-02 10:18 ` Will Deacon
2022-12-02 14:30 ` Waiman Long
2022-12-13 12:54 ` Will Deacon
2022-12-13 15:54 ` Waiman Long
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=f5abd919-c996-6549-8d48-a93a66daaef8@redhat.com \
--to=longman@redhat.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=wangbiao3@xiaomi.com \
--cc=wenjieli@qti.qualcomm.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;
as well as URLs for NNTP newsgroup(s).