Re: [PATCH v3 1/2] staging: most: video: Protect pending_mbos and mute with list_lock
From: Dan Carpenter
Date: Wed Nov 18 2026 - 07:01:46 EST
On Wed, Nov 18, 2026 at 01:22:41PM +0200, Andy Shevchenko wrote:
> On Wed, Nov 18, 2026 at 12:20:32PM +0300, Dan Carpenter wrote:
> > On Tue, Nov 17, 2026 at 10:35:57PM +0530, Shivani Patel wrote:
> > > data_ready() and get_top_mbo() read mdev->pending_mbos without holding
> > > mdev->list_lock, racing with comp_rx_data() which modifies the list
> > > under mdev->list_lock. Also, comp_vdev_close() clears mdev->mute without
> > > holding mdev->list_lock.
> > >
> > > Acquire mdev->list_lock in data_ready(), get_top_mbo(), and when
> > > clearing mdev->mute in comp_vdev_close(). Use list_first_entry_or_null()
> > > in get_top_mbo() so comp_vdev_read() can drop the redundant data_ready()
> > > check inside the read loop.
>
> ...
>
> > > -static inline bool data_ready(struct most_video_dev *mdev)
> > > +static bool data_ready(struct most_video_dev *mdev)
> > > {
> > > - return !list_empty(&mdev->pending_mbos);
> > > + unsigned long flags;
> > > + bool ready;
> > > +
> > > + spin_lock_irqsave(&mdev->list_lock, flags);
> > > + ready = !list_empty(&mdev->pending_mbos);
> > > + spin_unlock_irqrestore(&mdev->list_lock, flags);
> > > +
> > > + return ready;
> >
> > It doesn't really matter if we take the lock where since we drop it
> > right away. The list_empty() doesn't anything that requires locking
> > so far as I can see.
>
> Right, but the problem is that we possibly might compare valid pointer
> (list head itself) with the stale pointer (head->next and/or head->prev).
It's fine. If you strip away the macros what the code is doing is.
diff --git a/drivers/staging/most/video/video.c b/drivers/staging/most/video/video.c
index 3a0445ff62f4..7bebbf1e11cb 100644
--- a/drivers/staging/most/video/video.c
+++ b/drivers/staging/most/video/video.c
@@ -62,7 +62,9 @@ static DEFINE_SPINLOCK(list_lock);
static inline bool data_ready(struct most_video_dev *mdev)
{
- return !list_empty(&mdev->pending_mbos);
+ if (mdev->pending_mbos.next == mdev->pending_mbos.prev)
+ return false;
+ return true;
}
static inline struct mbo *get_top_mbo(struct most_video_dev *mdev)
The lock is unecessary, but also harmless. Why I don't like adding a
lock is because we drop the lock before we return so the return value
could be wrong by the time it gets to the caller. Nothing really
relies on the return being correct. It's useful because we set the
error code based on it, but if it's wrong the system isn't going to
crash.
It's pretty common to do this sort of thing where we check in a racy
way if we can return early, then we take a lock and check again to
ensure that something is still true when it matters.
regards,
dan carpenter