From: "Li,Rongqing" <lirongqing@baidu.com>
To: Dave Jiang <dave.jiang@intel.com>,
"fenghua.yu@intel.com" <fenghua.yu@intel.com>,
"vkoul@kernel.org" <vkoul@kernel.org>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>
Subject: RE: [External Mail] Re: [PATCH][RFC] dmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list
Date: Wed, 29 May 2024 09:15:26 +0000 [thread overview]
Message-ID: <9968be03b6064a84b6f1aaf99fc6c5e1@baidu.com> (raw)
In-Reply-To: <7b96aa7d-4e23-40dd-81de-1e60660c02dd@intel.com>
> Because if the descriptor is freed and given out to a different thread while the
> code is still walking the list, the iterator may hit a bad pointer due to the freed
> descriptor pointing to something else.
>
> Also, please include a Fixes tag for the fix. Thanks!
Ok, I will send V2, thanks
Br
prev parent reply other threads:[~2024-05-29 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 6:19 [PATCH][RFC] dmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list Li RongQing
2024-05-28 0:37 ` Li,Rongqing
2024-05-28 16:27 ` Dave Jiang
2024-05-29 9:15 ` Li,Rongqing [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=9968be03b6064a84b6f1aaf99fc6c5e1@baidu.com \
--to=lirongqing@baidu.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=vkoul@kernel.org \
/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