From: "代子为 (Ziwei Dai)" <Ziwei.Dai@unisoc.com>
To: "paulmck@kernel.org" <paulmck@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"王双 (Shuang Wang)" <shuang.wang@unisoc.com>
Subject: 答复: linux-next: Fixes tag needs some work in the rcu tree
Date: Thu, 6 Apr 2023 01:42:15 +0000 [thread overview]
Message-ID: <82b6b670854f4366a4c02543f56be6b7@BJMBX01.spreadtrum.com> (raw)
In-Reply-To: <66b7fceb-0a9d-42c1-987f-1ac6c857d987@paulmck-laptop>
> -----邮件原件-----
> 发件人: Paul E. McKenney <paulmck@kernel.org>
> 发送时间: 2023年4月6日 6:59
> 收件人: Stephen Rothwell <sfr@canb.auug.org.au>
> 抄送: 代子为 (Ziwei Dai) <Ziwei.Dai@unisoc.com>; Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Linux Next Mailing List
> <linux-next@vger.kernel.org>
> 主题: Re: linux-next: Fixes tag needs some work in the rcu tree
>
>
> 注意: 这封邮件来自于外部。除非你确定邮件内容安全,否则不要点击任何链接和附件。
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the
> sender and know the content is safe.
>
>
>
> On Thu, Apr 06, 2023 at 08:36:19AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > In commit
> >
> > acdc79917d65 ("rcu/kvfree: Avoid freeing new kfree_rcu() memory
> > after old grace period")
> >
> > Fixes tag
> >
> > Fixes: 0392bebebf26 ("rcu/kvfree: Avoid freeing new kfree_rcu()
> > memory after old grace period")
> >
> > has these problem(s):
> >
> > - Subject does not match target commit subject
> > Just use
> > git log -1 --format='Fixes: %h ("%s")'
> >
> > Maybe you meant:
> >
> > Fixes: 0392bebebf26 ("rcu: Add multiple in-flight batches of
> > kfree_rcu() work")
>
> Hello, Stephen,
>
> There is currently some debate as to exactly which commit(s) introduced the bug, which will hopefully come to a conclusion before
> tomorrow's -next. If they do not, I will use your correction as a placeholder.
>
> Just for completeness, the current other two candidates (which appear quite plausible to me) are these:
>
> Fixes: 34c881745549 ("rcu: Support kfree_bulk() interface in kfree_rcu()")
> Fixes: 5f3c8d620447 ("rcu/tree: Maintain separate array for vmalloc ptrs")
>
> Ziwei Dai, what are your thoughts on this? This is from a mainline perspective, my guess being that your investigation involved some
> other Linux-kernel tree.
>
> Thanx, Paul
Hi Paul, right, please help correct it.
prev parent reply other threads:[~2023-04-06 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 22:36 linux-next: Fixes tag needs some work in the rcu tree Stephen Rothwell
2023-04-05 22:59 ` Paul E. McKenney
2023-04-06 1:42 ` 代子为 (Ziwei Dai) [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=82b6b670854f4366a4c02543f56be6b7@BJMBX01.spreadtrum.com \
--to=ziwei.dai@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shuang.wang@unisoc.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).