From: "Joseph, Jithu" <jithu.joseph@intel.com>
To: Yuan Can <yuancan@huawei.com>
Cc: <ashok.raj.linux@gmail.com>, <tony.luck@intel.com>,
<hdegoede@redhat.com>, <ilpo.jarvinen@linux.intel.com>,
<darcari@redhat.com>, <platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH] platform/x86/intel/ifs: Add missing destroy_work_on_stack()
Date: Tue, 5 Nov 2024 12:31:56 -0800 [thread overview]
Message-ID: <3397dd32-fa9e-4447-8be2-06b29e74960e@intel.com> (raw)
In-Reply-To: <20241105120728.21646-1-yuancan@huawei.com>
On 11/5/2024 4:07 AM, Yuan Can wrote:
> This commit add missed destroy_work_on_stack() operations for
> local_work.w in scan_chunks_sanity_check().
>
If you were seeing any specific warnings, might be helpful to mention that too in the commit
> Fixes: 3279decb2c3c ("platform/x86/intel/ifs: Annotate work queue on stack so object debug does not complain")
> Signed-off-by: Yuan Can <yuancan@huawei.com>
> ---
> drivers/platform/x86/intel/ifs/load.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/platform/x86/intel/ifs/load.c b/drivers/platform/x86/intel/ifs/load.c
> index de54bd1a5970..2faeb1ffbd92 100644
> --- a/drivers/platform/x86/intel/ifs/load.c
> +++ b/drivers/platform/x86/intel/ifs/load.c
> @@ -347,6 +347,7 @@ static int scan_chunks_sanity_check(struct device *dev)
> INIT_WORK_ONSTACK(&local_work.w, copy_hashes_authenticate_chunks);
> schedule_work_on(cpu, &local_work.w);
> wait_for_completion(&ifs_done);
> + destroy_work_on_stack(&local_work.w);
> if (ifsd->loading_error) {
> ret = -EIO;
> goto out;
The change looks good to me.
(I see other users of INIT_WORK_ONSTACK having a corresponding destroy_xxx())
Reviewed-by: Jithu Joseph <jithu.joseph@intel.com>
Thanks
Jithu
prev parent reply other threads:[~2024-11-05 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 12:07 [PATCH] platform/x86/intel/ifs: Add missing destroy_work_on_stack() Yuan Can
2024-11-05 16:04 ` Ilpo Järvinen
2024-11-05 20:31 ` Joseph, Jithu [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=3397dd32-fa9e-4447-8be2-06b29e74960e@intel.com \
--to=jithu.joseph@intel.com \
--cc=ashok.raj.linux@gmail.com \
--cc=darcari@redhat.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=yuancan@huawei.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