* linux-next: Fixes tag needs some work in the rcu tree
@ 2023-04-05 22:36 Stephen Rothwell
2023-04-05 22:59 ` Paul E. McKenney
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2023-04-05 22:36 UTC (permalink / raw)
To: Paul E. McKenney
Cc: Ziwei Dai, Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
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")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: Fixes tag needs some work in the rcu tree
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)
0 siblings, 1 reply; 3+ messages in thread
From: Paul E. McKenney @ 2023-04-05 22:59 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Ziwei Dai, Linux Kernel Mailing List, Linux Next Mailing List
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* 答复: linux-next: Fixes tag needs some work in the rcu tree
2023-04-05 22:59 ` Paul E. McKenney
@ 2023-04-06 1:42 ` 代子为 (Ziwei Dai)
0 siblings, 0 replies; 3+ messages in thread
From: 代子为 (Ziwei Dai) @ 2023-04-06 1:42 UTC (permalink / raw)
To: paulmck, Stephen Rothwell
Cc: Linux Kernel Mailing List, Linux Next Mailing List,
王双 (Shuang Wang)
> -----邮件原件-----
> 发件人: 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-04-06 1:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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).