workqueue: Remove unnecessary kfree() call in rcu_free_wq()
Subsystems (2)
PATCH v5 1/1 workqueue: Remove unnecessary kfree() call in rcu_free_wq()
From: Zhang Qiang <[email protected]>
The data structure member "wq->rescuer" was reset to a null pointer in one if branch. It was passed to a call of the function "kfree" in the callback function "rcu_free_wq" (which was eventually executed). The function "kfree" does not perform more meaningful data processing for a passed null pointer (besides immediately returning from such a call). Thus delete this function call which became unnecessary with the referenced software update.
---
v1->v2->v3->v4->v5:
Modify weakly submitted information.
kernel/workqueue.c | 1 - 1 file changed, 1 deletion(-)
kernel/workqueue.c +0 -1
@@ -3491,7 +3491,6 @@ static void rcu_free_wq(struct rcu_head *rcu)else free_workqueue_attrs (wq->unbound_attrs); -kfree (wq->rescuer);kfree (wq); }
Signature · 1 line
2.24.1
Quoted 2 lines
Thus delete this function call which became unnecessary with the referenced software update.
…
Quoted 1 line
Suggested-by Markus Elfring <[email protected]>
Would the tag “Co-developed-by” be more appropriate according to the patch review to achieve a more pleasing commit message?
Quoted 2 lines
v1->v2->v3->v4->v5:
Modify weakly submitted information.
Now I wonder about your wording choice “weakly”.
Regards,
Markus
A message that is not in the archive (sent off-list or not yet received): DM6PR11MB32573F3884A864ECD586235EFF8E0@DM6PR11MB3257.namprd11.prod.outlook.com
VGhhbmtzIGZvciB5b3VyIGd1aWRlLg0KSSB3aWxsIHRyeSB0byBjaGFuZ2UgdGhlIHdlYWtuZXNz IG9mIHdlYWsgd29yZGluZy4NCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fXw0Kt6K8/sjLOiBaaGFuZywgUWlhbmcgPFFpYW5nLlpoYW5nQHdpbmRyaXZlci5jb20+DQq3 osvNyrG85DogMjAyMMTqNdTCMjjI1SA5OjQxDQrK1bz+yMs6IE1hcmt1cyBFbGZyaW5nOyBUZWp1 biBIZW87IExhaSBKaWFuZ3NoYW4NCrOty806IGxpbnV4LWtlcm5lbEB2Z2VyLmtlcm5lbC5vcmc7 IGtlcm5lbC1qYW5pdG9yc0B2Z2VyLmtlcm5lbC5vcmcNCtb3zOI6ILvYuLQ6IFtQQVRDSCB2NV0g d29ya3F1ZXVlOiBSZW1vdmUgdW5uZWNlc3Nhcnkga2ZyZWUoKSBjYWxsIGluIHJjdV9mcmVlX3dx KCkNCg0KVGhhbmtzIGZvciB5b3VyIGd1aWRlLiBJIHRyaWVkIHRvIGNoYW5nZSB0aGUgd2Vha25l c3Mgb2Ygd2VhayB3b3JkaW5nDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N CreivP7IyzogbGludXgta2VybmVsLW93bmVyQHZnZXIua2VybmVsLm9yZyA8bGludXgta2VybmVs LW93bmVyQHZnZXIua2VybmVsLm9yZz4gtPqx7SBNYXJrdXMgRWxmcmluZyA8TWFya3VzLkVsZnJp bmdAd2ViLmRlPg0Kt6LLzcqxvOQ6IDIwMjDE6jXUwjI3yNUgMTY6MjANCsrVvP7IyzogWmhhbmcs IFFpYW5nIDxRaWFuZy5aaGFuZ0B3aW5kcml2ZXIuY29tPjsgVGVqdW4gSGVvIDx0akBrZXJuZWwu b3JnPjsgTGFpIEppYW5nc2hhbiA8amlhbmdzaGFubGFpQGdtYWlsLmNvbT4NCrOty806IGxpbnV4 LWtlcm5lbEB2Z2VyLmtlcm5lbC5vcmcgPGxpbnV4LWtlcm5lbEB2Z2VyLmtlcm5lbC5vcmc+OyBr ZXJuZWwtamFuaXRvcnNAdmdlci5rZXJuZWwub3JnIDxrZXJuZWwtamFuaXRvcnNAdmdlci5rZXJu ZWwub3JnPg0K1vfM4jogUmU6IFtQQVRDSCB2NV0gd29ya3F1ZXVlOiBSZW1vdmUgdW5uZWNlc3Nh cnkga2ZyZWUoKSBjYWxsIGluIHJjdV9mcmVlX3dxKCkNCg0KPiBUaHVzIGRlbGV0ZSB0aGlzIGZ1 bmN0aW9uIGNhbGwgd2hpY2ggYmVjYW1lIHVubmVjZXNzYXJ5IHdpdGggdGhlIHJlZmVyZW5jZWQN Cj4gc29mdHdhcmUgdXBkYXRlLg0Koa0NCj4gU3VnZ2VzdGVkLWJ5OiBNYXJrdXMgRWxmcmluZyA8 TWFya3VzLkVsZnJpbmdAd2ViLmRlPg0KDQpXb3VsZCB0aGUgdGFnIKGwQ28tZGV2ZWxvcGVkLWJ5 obEgYmUgbW9yZSBhcHByb3ByaWF0ZSBhY2NvcmRpbmcgdG8gdGhlIHBhdGNoIHJldmlldw0KdG8g YWNoaWV2ZSBhIG1vcmUgcGxlYXNpbmcgY29tbWl0IG1lc3NhZ2U/DQoNCg0KPiAgdjEtPnYyLT52 My0+djQtPnY1Og0KPiAgTW9kaWZ5IHdlYWtseSBzdWJtaXR0ZWQgaW5mb3JtYXRpb24uDQoNCk5v dyBJIHdvbmRlciBhYm91dCB5b3VyIHdvcmRpbmcgY2hvaWNlIKGwd2Vha2x5obEuDQoNClJlZ2Fy ZHMsDQpNYXJrdXMNCg=
Guys, the patch is wrong. The kfree is harmless when this is called from destroy_workqueue() and required when it's called from pwq_unbound_release_workfn(). Lai Jiangshan already explained this already. Why are we still discussing this?
regards,
dan carpenter
Tejun Heo
maintainerQuoted 4 lines · Dan Carpenter
Guys, the patch is wrong. The kfree is harmless when this is called from
destroy_workqueue()and required when it's called frompwq_unbound_release_workfn(). Lai Jiangshan already explained this already. Why are we still discussing this?
Oops, missed that. Reverting.
Thanks.
Signature · 1 line
tejun
Quoted 6 lines
Quoted 4 lines
Guys, the patch is wrong. The kfree is harmless when this is called from
destroy_workqueue()and required when it's called frompwq_unbound_release_workfn(). Lai Jiangshan already explained this already. Why are we still discussing this?Oops, missed that. Reverting.
Can it matter to use separate callback functions for these cases?
https://elixir.bootlin.com/linux/v5.7-rc7/C/ident/rcu_free_pwq
Regards,
Markus
Quoted 2 lines
Can it matter to use separate callback functions for these cases?
https://elixir.bootlin.com/linux/v5.7-rc7/C/ident/rcu_free_pwq
See also:
https://elixir.bootlin.com/linux/v5.7-rc7/C/ident/rcu_free_wq
Regards,
Markus
Lai Jiangshan
reviewerQuoted 6 lines · Dan Carpenter
Guys, the patch is wrong. The kfree is harmless when this is called from
destroy_workqueue()and required when it's called frompwq_unbound_release_workfn(). Lai Jiangshan already explained this already. Why are we still discussing this?
I'm also confused why they have been debating about the changelog after the patch was queued. My statement was about "the patch is a correct cleanup, but the changelog is totally misleading".
destroy_workqueue(percpu_wq) -> rcu_free_wq()
ordestroy_workqueue(unbound_wq) -> put_pwq() ->pwq_unbound_release_workfn() -> rcu_free_wq()
So the patch is correct to me. Only can destroy_workqueue() lead to rcu_free_wq().
Still, the kfree(NULL) is harmless. But it is cleaner to have the patch. But the changelog is wrong, even after the lengthened debating, and English is not my mother tongue, so I just looked on.
Quoted 12 lines · Lai Jiangshan
Quoted 6 lines · Dan Carpenter
Guys, the patch is wrong. The kfree is harmless when this is called from
destroy_workqueue()and required when it's called frompwq_unbound_release_workfn(). Lai Jiangshan already explained this already. Why are we still discussing this?I'm also confused why they have been debating about the changelog after the patch was queued. My statement was about "the patch is a correct cleanup, but the changelog is totally misleading".
Quoted 7 lines
destroy_workqueue(percpu_wq)->rcu_free_wq()
ordestroy_workqueue(unbound_wq)->put_pwq()->pwq_unbound_release_workfn()->rcu_free_wq()So the patch is correct to me. Only can
destroy_workqueue()lead torcu_free_wq().
It looks like there are lots of paths which call put_pwq() and put_pwq_unlocked().
1168 static void pwq_dec_nr_in_flight(struct pool_workqueue *pwq, int color)
1169 {
1170 /* uncolored work items don't participate in flushing or nr_active */
1171 if (color = WORK_NO_COLOR)
1172 goto out_put;
1173 We don't take an extra reference in this function.
1200 out_put: 1201 put_pwq(pwq); 1202 }
I don't know this code well, so I will defer to your expertise if you say it is correct.
Quoted 5 lines
Still, the kfree(NULL) is harmless. But it is cleaner to have the patch. But the changelog is wrong, even after the lengthened debating, and English is not my mother tongue, so I just looked on.
We have tried to tell Markus not to advise people about commit messages but he doesn't listen. He has discouraged some contributors. :/
regards,
dan carpenter
Lai Jiangshan
reviewerQuoted 32 lines · Dan Carpenter
Quoted 12 lines · Lai Jiangshan
Quoted 6 lines · Dan Carpenter
Guys, the patch is wrong. The kfree is harmless when this is called from
destroy_workqueue()and required when it's called frompwq_unbound_release_workfn(). Lai Jiangshan already explained this already. Why are we still discussing this?I'm also confused why they have been debating about the changelog after the patch was queued. My statement was about "the patch is a correct cleanup, but the changelog is totally misleading".
Quoted 7 lines
destroy_workqueue(percpu_wq)->rcu_free_wq()
ordestroy_workqueue(unbound_wq)->put_pwq()->pwq_unbound_release_workfn()->rcu_free_wq()So the patch is correct to me. Only can
destroy_workqueue()lead torcu_free_wq().It looks like there are lots of paths which call
put_pwq()andput_pwq_unlocked().1168 static void pwq_dec_nr_in_flight(struct pool_workqueue *pwq, int color) 1169 { 1170 /* uncolored work items don't participate in flushing or nr_active */ 1171 if (color = WORK_NO_COLOR) 1172 goto out_put; 1173
Quoted 8 lines
We don't take an extra reference in this function.
1200 out_put: 1201 put_pwq(pwq); 1202 }I don't know this code well, so I will defer to your expertise if you say it is correct.
wq owns the ultimate or permanent references to itself by owning references to wq->numa_pwq_tbl[node], wq->dfl_pwq. The pwq's references keep the pwq in wq->pwqs.
Only destroy_workqueue() can release these ultimate references and then (after maybe a period of time) deplete the wq->pwqs finally and then free itself in rcu callback.
Actually, in short, we don't need the care about the above detail. The responsibility to free rescuer is on destroy_workqueue(), and since it does the free early, it doesn't need to do it again later.
e2dca7adff8f moved the free of rescuer into rcu callback, and I didn't check all the changes between then and now. But at least now, the rescuer is not accessed in rcu mananer, so we don't need to free it in rcu mananer.
Quoted 12 lines
Quoted 6 lines
Still, the kfree(NULL) is harmless. But it is cleaner to have the patch. But the changelog is wrong, even after the lengthened debating, and English is not my mother tongue, so I just looked on.
We have tried to tell Markus not to advise people about commit messages but he doesn't listen. He has discouraged some contributors. :/
regards,
dan carpenter
Tejun Heo
maintainerHello,
Quoted 3 lines · Lai Jiangshan
wq owns the ultimate or permanent references to itself by owning references to wq->numa_pwq_tbl[node],
wq->dfl_pwq. The pwq's references keep the pwq inwq->pwqs.
Yeah, regardless of who puts a wq the last time, the base reference is put by destroy_workqueue() and thus it's guaranteed that a wq can't be rcu freed without going through destroy_workqueue(). lol I'm undoing the revert.
Thanks.
Signature · 1 line
tejun
Quoted 3 lines
Yeah, regardless of who puts a wq the last time, the base reference is put by
destroy_workqueue()and thus it's guaranteed that a wq can't be rcu freed without going throughdestroy_workqueue(). lol I'm undoing the revert.
* Would you like to add such background information to the change description?
* How do you think about integrate a following patch version after the extra clarification?
Regards,
Markus
Quoted 55 lines · Lai Jiangshan
Quoted 32 lines · Dan Carpenter
Quoted 12 lines · Lai Jiangshan
Quoted 6 lines · Dan Carpenter
Guys, the patch is wrong. The kfree is harmless when this is called from
destroy_workqueue()and required when it's called frompwq_unbound_release_workfn(). Lai Jiangshan already explained this already. Why are we still discussing this?I'm also confused why they have been debating about the changelog after the patch was queued. My statement was about "the patch is a correct cleanup, but the changelog is totally misleading".
Quoted 7 lines
destroy_workqueue(percpu_wq)->rcu_free_wq()
ordestroy_workqueue(unbound_wq)->put_pwq()->pwq_unbound_release_workfn()->rcu_free_wq()So the patch is correct to me. Only can
destroy_workqueue()lead torcu_free_wq().It looks like there are lots of paths which call
put_pwq()andput_pwq_unlocked().1168 static void pwq_dec_nr_in_flight(struct pool_workqueue *pwq, int color) 1169 { 1170 /* uncolored work items don't participate in flushing or nr_active */ 1171 if (color = WORK_NO_COLOR) 1172 goto out_put; 1173Quoted 8 lines
We don't take an extra reference in this function.
1200 out_put: 1201 put_pwq(pwq); 1202 }I don't know this code well, so I will defer to your expertise if you say it is correct.
wq owns the ultimate or permanent references to itself by owning references to wq->numa_pwq_tbl[node],
wq->dfl_pwq. The pwq's references keep the pwq inwq->pwqs.Only
destroy_workqueue()can release these ultimate references and then (after maybe a period of time) deplete thewq->pwqsfinally and then free itself in rcu callback.Actually, in short, we don't need the care about the above detail. The responsibility to free rescuer is on
destroy_workqueue(), and since it does the free early, it doesn't need to do it again later.
Quoted 5 lines
e2dca7adff8fmoved the free of rescuer into rcu callback, and I didn't check all the changes between then and now. But at least now, the rescuer is not accessed in rcu mananer, so we don't need to free it in rcu mananer.
Ah... Thanks for the explanation!
regards,
dan carpenter
Quoted 6 lines
Quoted 4 lines
Still, the kfree(NULL) is harmless. But it is cleaner to have the patch. But the changelog is wrong, even after the lengthened debating, and English is not my mother tongue, so I just looked on.
We have tried to tell Markus not to advise people about commit messages
A few concerns were mentioned.
Quoted 1 line
but he doesn't listen.
I am still listening as usual.
I am offering constructive patch reviews for selected topics.
Quoted 1 line
He has discouraged some contributors. :/
There are the usual risks that additional views are occasionally not picked up in positive ways.
Regards,
Markus
Quoted 2 lines
I'm also confused why they have been debating about the changelog after the patch was queued.
I suggest to take another look at the provided patch review comments.
Quoted 2 lines
My statement was about "the patch is a correct cleanup, but the changelog is totally misleading".
The commit message was accordingly adjusted, wasn't it?
Quoted 10 lines
destroy_workqueue(percpu_wq)->rcu_free_wq()
ordestroy_workqueue(unbound_wq)->put_pwq()->pwq_unbound_release_workfn()->rcu_free_wq()So the patch is correct to me. Only can
destroy_workqueue()lead torcu_free_wq().Still, the kfree(NULL) is harmless. But it is cleaner to have the patch.
Thanks for such a feedback.
Quoted 1 line
But the changelog is wrong, even after the lengthened debating,
Do you expect any corresponding improvements?
Quoted 1 line
and English is not my mother tongue, so I just looked on.
How will the patch review evolve further despite of this information?
Regards,
Markus
Quoted 2 lines
I'm also confused why they have been debating about the changelog after the patch was queued.
I suggest to take another look at the provided patch review comments.
Quoted 2 lines
My statement was about "the patch is a correct cleanup, but the changelog is totally misleading".
The commit message was accordingly adjusted, wasn't it?
Quoted 10 lines
destroy_workqueue(percpu_wq)->rcu_free_wq()
ordestroy_workqueue(unbound_wq)->put_pwq()->pwq_unbound_release_workfn()->rcu_free_wq()So the patch is correct to me. Only can
destroy_workqueue()lead torcu_free_wq().Still, the kfree(NULL) is harmless. But it is cleaner to have the patch.
Thanks for such a feedback.
Quoted 1 line
But the changelog is wrong, even after the lengthened debating,
Do you expect any corresponding improvements?
Quoted 1 line
and English is not my mother tongue, so I just looked on.
How will the patch review evolve further despite of this information?
Regards,
Markus
Quoted 10 lines · On Wed, May 27, 2020 at 03:57:15PM +0800, [email protected] wrote:
From: Zhang Qiang <[email protected]>
The data structure member "
wq->rescuer" was reset to a null pointer in one if branch. It was passed to a call of the function "kfree" in the callback function "rcu_free_wq" (which was eventually executed). The function "kfree" does not perform more meaningful data processing for a passed null pointer (besides immediately returning from such a call). Thus delete this function call which became unnecessary with the referenced software update.
Quoted 4 lines
Fixes def98c84b6cd ("workqueue: Fix spurious sanity check failures in destroy_workqueue()")Suggested-by Markus Elfring <[email protected]>Signed-off-by Zhang Qiang <[email protected]>
Applied to wq/for-5.8.
Thanks.
Signature · 1 line
tejun