From: Minu Jin <s9430939@naver.com>
To: parthiban.veerasooran@microchip.com,
christian.gromm@microchip.com, gregkh@linuxfoundation.org,
dan.carpenter@linaro.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Minu Jin <s9430939@naver.com>
Subject: [PATCH] staging: most: dim2: fix a race condition in complete_all_mbos()
Date: Fri, 6 Feb 2026 01:02:31 +0900 [thread overview]
Message-ID: <20260205160231.1543828-1-s9430939@naver.com> (raw)
The current implementation of complete_all_mbos() repeatedly acquires
and releases the spinlock in loop. This causes lock contention.
This patch refactors the function to use list_replace_init(), moving all
entries to a local list. This removes the loop-based locking approach
and significantly reduces lock contention.
Signed-off-by: Minu Jin <s9430939@naver.com>
---
drivers/staging/most/dim2/dim2.c | 18 +++++++-----------
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/drivers/staging/most/dim2/dim2.c b/drivers/staging/most/dim2/dim2.c
index 80af965356d0..fb54bb1a803f 100644
--- a/drivers/staging/most/dim2/dim2.c
+++ b/drivers/staging/most/dim2/dim2.c
@@ -415,20 +415,16 @@ static irqreturn_t dim2_ahb_isr(int irq, void *_dev)
*/
static void complete_all_mbos(struct list_head *head)
{
+ struct mbo *mbo, *mbo_tmp;
unsigned long flags;
- struct mbo *mbo;
-
- for (;;) {
- spin_lock_irqsave(&dim_lock, flags);
- if (list_empty(head)) {
- spin_unlock_irqrestore(&dim_lock, flags);
- break;
- }
+ LIST_HEAD(del_list);
- mbo = list_first_entry(head, struct mbo, list);
- list_del(head->next);
- spin_unlock_irqrestore(&dim_lock, flags);
+ spin_lock_irqsave(&dim_lock, flags);
+ list_replace_init(head, &del_list);
+ spin_unlock_irqrestore(&dim_lock, flags);
+ list_for_each_entry_safe(mbo, mbo_tmp, &del_list, list) {
+ list_del(&mbo->list);
mbo->processed_length = 0;
mbo->status = MBO_E_CLOSE;
mbo->complete(mbo);
--
2.43.0
next reply other threads:[~2026-02-05 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 16:02 Minu Jin [this message]
2026-02-06 7:20 ` Dan Carpenter
2026-02-06 18:04 ` Minu Jin
2026-02-07 11:55 ` Greg KH
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=20260205160231.1543828-1-s9430939@naver.com \
--to=s9430939@naver.com \
--cc=christian.gromm@microchip.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=parthiban.veerasooran@microchip.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
all inboxes | Powered by JetHome®