From: Dan Carpenter <dan.carpenter@linaro.org>
To: Minu Jin <s9430939@naver.com>
Cc: parthiban.veerasooran@microchip.com,
christian.gromm@microchip.com, gregkh@linuxfoundation.org,
hverkuil+cisco@kernel.org,
laurent.pinchart+renesas@ideasonboard.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: most: video: fix potential race in list iteration
Date: Wed, 4 Feb 2026 12:35:59 +0300 [thread overview]
Message-ID: <aYMS_9xQ4LGgMS-j@stanley.mountain> (raw)
In-Reply-To: <20260203112800.3351763-1-s9430939@naver.com>
On Tue, Feb 03, 2026 at 08:28:00PM +0900, Minu Jin wrote:
> There is a pattern in the loops where the lock is dropped
> to call a specific function and then re-acquired.
>
> The list can be exposed during this short gap, creating a potential
> race condition. This patch fixes the problem by moving nodes to a
> local list while holding the lock, instead of using the
> unlock/lock pattern in the loop.
>
> Signed-off-by: Minu Jin <s9430939@naver.com>
> ---
> drivers/staging/most/video/video.c | 22 ++++++++++++++--------
> 1 file changed, 14 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/staging/most/video/video.c b/drivers/staging/most/video/video.c
> index 32f71d9a9cf7..e7db58e5746a 100644
> --- a/drivers/staging/most/video/video.c
> +++ b/drivers/staging/most/video/video.c
> @@ -121,6 +121,7 @@ static int comp_vdev_close(struct file *filp)
> struct comp_fh *fh = to_comp_fh(filp);
> struct most_video_dev *mdev = fh->mdev;
> struct mbo *mbo, *tmp;
> + LIST_HEAD(free_list);
>
> /*
> * We need to put MBOs back before we call most_stop_channel()
> @@ -134,12 +135,15 @@ static int comp_vdev_close(struct file *filp)
> spin_lock_irq(&mdev->list_lock);
> mdev->mute = true;
> list_for_each_entry_safe(mbo, tmp, &mdev->pending_mbos, list) {
> - list_del(&mbo->list);
> - spin_unlock_irq(&mdev->list_lock);
> - most_put_mbo(mbo);
> - spin_lock_irq(&mdev->list_lock);
> + list_move(&mbo->list, &free_list);
> }
This loop moves ever single item in the list one by one. You could
do it in one step instead by copying the list_head and setting
pending_mbos to point to itself.
Same in other loop.
regards,
dan carpenter
next prev parent reply other threads:[~2026-02-04 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 11:28 [PATCH] staging: most: video: fix potential race in list iteration Minu Jin
2026-02-04 9:35 ` Dan Carpenter [this message]
2026-02-05 2:16 ` [PATCH v2] " Minu Jin
2026-02-05 5:45 ` Dan Carpenter
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=aYMS_9xQ4LGgMS-j@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=christian.gromm@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil+cisco@kernel.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=parthiban.veerasooran@microchip.com \
--cc=s9430939@naver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.