Re: cxl: Fix kobject memory leak in cxl_sysfs_afu_new_cr()
> Okay, so I don’t have to send the v2 patch. It will become more interesting under which circumstances the presented software development concerns will be taken better into account. Regards, Markus
Re: [PATCH] cxl: Fix kobject memory leak in cxl_sysfs_afu_new_cr()
在 2020/6/3 14:50, Greg Kroah-Hartman 写道: On Wed, Jun 03, 2020 at 02:34:07PM +0800, wanghai (M) wrote: 在 2020/6/3 14:14, Greg Kroah-Hartman 写道: On Wed, Jun 03, 2020 at 09:42:41AM +0800, wanghai (M) wrote: 在 2020/6/3 1:20, Markus Elfring 写道: Fix it by adding a call to kobject_put() in the error path of kobject_init_and_add(). Thanks for another completion of the exception handling. Would an other patch subject be a bit nicer? Thanks for the guidance, I will perfect this description and send a v2 Please note that you are responding to someone that a lot of kernel developers and maintainers have blacklisted as being very annoying and not helpful at all. Please do not feel that you need to respond to, or change any patch in response to their emails at all. I strongly recommend you just add them to your filters to not have to see their messages. That's what I have done. thanks, greg k-h . Okay, so I don’t have to send the v2 patch. No, all should be fine, I'll review the patch when after 5.8-rc1 is out, and if I find any problems with it, will let you know then. Got it. Thanks. thanks, Wang Hai
Re: [PATCH] cxl: Fix kobject memory leak in cxl_sysfs_afu_new_cr()
On Wed, Jun 03, 2020 at 02:34:07PM +0800, wanghai (M) wrote: > > 在 2020/6/3 14:14, Greg Kroah-Hartman 写道: > > On Wed, Jun 03, 2020 at 09:42:41AM +0800, wanghai (M) wrote: > > > 在 2020/6/3 1:20, Markus Elfring 写道: > > > > > Fix it by adding a call to kobject_put() in the error path of > > > > > kobject_init_and_add(). > > > > Thanks for another completion of the exception handling. > > > > > > > > Would an other patch subject be a bit nicer? > > > Thanks for the guidance, I will perfect this description and send a v2 > > Please note that you are responding to someone that a lot of kernel > > developers and maintainers have blacklisted as being very annoying and > > not helpful at all. > > > > Please do not feel that you need to respond to, or change any patch in > > response to their emails at all. > > > > I strongly recommend you just add them to your filters to not have to > > see their messages. That's what I have done. > > > > thanks, > > > > greg k-h > > > > . > > Okay, so I don’t have to send the v2 patch. No, all should be fine, I'll review the patch when after 5.8-rc1 is out, and if I find any problems with it, will let you know then. thanks, greg k-h
Re: [PATCH] cxl: Fix kobject memory leak in cxl_sysfs_afu_new_cr()
> Please note that you are responding to someone that a lot of kernel > developers and maintainers have blacklisted as being very annoying I can understand that you can occasionally become annoyed. > and not helpful at all. I got the impression that some contributors (including you) found also a selection of my contributions useful. > Please do not feel that you need to respond to, or change any patch in > response to their emails at all. I suggest to reconsider your responses to provided information once more. > I strongly recommend you just add them to your filters to not have to > see their messages. That's what I have done. I find such an “advice” questionable while it is generally possible to adjust the communication settings as needed. Regards, Markus
Re: [PATCH] cxl: Fix kobject memory leak in cxl_sysfs_afu_new_cr()
在 2020/6/3 14:14, Greg Kroah-Hartman 写道: On Wed, Jun 03, 2020 at 09:42:41AM +0800, wanghai (M) wrote: 在 2020/6/3 1:20, Markus Elfring 写道: Fix it by adding a call to kobject_put() in the error path of kobject_init_and_add(). Thanks for another completion of the exception handling. Would an other patch subject be a bit nicer? Thanks for the guidance, I will perfect this description and send a v2 Please note that you are responding to someone that a lot of kernel developers and maintainers have blacklisted as being very annoying and not helpful at all. Please do not feel that you need to respond to, or change any patch in response to their emails at all. I strongly recommend you just add them to your filters to not have to see their messages. That's what I have done. thanks, greg k-h . Okay, so I don’t have to send the v2 patch. -- thanks, Wang Hai
Re: [PATCH] cxl: Fix kobject memory leak in cxl_sysfs_afu_new_cr()
On Wed, Jun 03, 2020 at 09:42:41AM +0800, wanghai (M) wrote: > > 在 2020/6/3 1:20, Markus Elfring 写道: > > > Fix it by adding a call to kobject_put() in the error path of > > > kobject_init_and_add(). > > Thanks for another completion of the exception handling. > > > > Would an other patch subject be a bit nicer? > Thanks for the guidance, I will perfect this description and send a v2 Please note that you are responding to someone that a lot of kernel developers and maintainers have blacklisted as being very annoying and not helpful at all. Please do not feel that you need to respond to, or change any patch in response to their emails at all. I strongly recommend you just add them to your filters to not have to see their messages. That's what I have done. thanks, greg k-h
Re: cxl: Fix kobject memory leak in cxl_sysfs_afu_new_cr()
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?id=f359287765c04711ff54fbd11645271d8e5ff763#n465 >> I just used the original author's label, should I replace all his labels >> like'err','err1' with reasonable one. > > No. Do you insist to deviate from the current Linux coding style? Regards, Markus
Re: [PATCH] cxl: Fix kobject memory leak in cxl_sysfs_afu_new_cr()
"wanghai (M)" writes: > 在 2020/6/3 1:20, Markus Elfring 写道: >>> Fix it by adding a call to kobject_put() in the error path of >>> kobject_init_and_add(). >> Thanks for another completion of the exception handling. >> >> Would an other patch subject be a bit nicer? > Thanks for the guidance, I will perfect this description and send a v2 >> >> … >>> +++ b/drivers/misc/cxl/sysfs.c >>> @@ -624,7 +624,7 @@ static struct afu_config_record >>> *cxl_sysfs_afu_new_cr(struct cxl_afu *afu, int c >>> rc = kobject_init_and_add(>kobj, _config_record_type, >>> >dev.kobj, "cr%i", cr->cr); >>> if (rc) >>> - goto err; >>> + goto err1; >> … >> >> Can an other label be more reasonable here? >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?id=f359287765c04711ff54fbd11645271d8e5ff763#n465 > I just used the original author's label, should I replace all his labels > like'err','err1' with reasonable one. No. cheers
Re: [PATCH] cxl: Fix kobject memory leak in cxl_sysfs_afu_new_cr()
在 2020/6/3 1:20, Markus Elfring 写道: Fix it by adding a call to kobject_put() in the error path of kobject_init_and_add(). Thanks for another completion of the exception handling. Would an other patch subject be a bit nicer? Thanks for the guidance, I will perfect this description and send a v2 … +++ b/drivers/misc/cxl/sysfs.c @@ -624,7 +624,7 @@ static struct afu_config_record *cxl_sysfs_afu_new_cr(struct cxl_afu *afu, int c rc = kobject_init_and_add(>kobj, _config_record_type, >dev.kobj, "cr%i", cr->cr); if (rc) - goto err; + goto err1; … Can an other label be more reasonable here? https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?id=f359287765c04711ff54fbd11645271d8e5ff763#n465 I just used the original author's label, should I replace all his labels like'err','err1' with reasonable one.
Re: [PATCH] cxl: Fix kobject memory leak in cxl_sysfs_afu_new_cr()
> Fix it by adding a call to kobject_put() in the error path of > kobject_init_and_add(). Thanks for another completion of the exception handling. Would an other patch subject be a bit nicer? … > +++ b/drivers/misc/cxl/sysfs.c > @@ -624,7 +624,7 @@ static struct afu_config_record > *cxl_sysfs_afu_new_cr(struct cxl_afu *afu, int c > rc = kobject_init_and_add(>kobj, _config_record_type, > >dev.kobj, "cr%i", cr->cr); > if (rc) > - goto err; > + goto err1; … Can an other label be more reasonable here? https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?id=f359287765c04711ff54fbd11645271d8e5ff763#n465 Regards, Markus
