public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Matan Cohen <matan@matanco.space>
Cc: linux-staging@lists.linux.dev,
	parthiban.veerasooran@microchip.com,
	christian.gromm@microchip.com
Subject: Re: [PATCH] staging: most: video: replace BUG_ON with WARN_ON_ONCE and add recovery
Date: Mon, 20 Apr 2026 14:35:00 +0200	[thread overview]
Message-ID: <2026042033-elevate-company-449c@gregkh> (raw)
In-Reply-To: <20260420113503.62552-1-matan@matanco.space>

On Mon, Apr 20, 2026 at 11:35:03AM +0000, Matan Cohen wrote:
> BUG_ON() halts the kernel unconditionally. The check after
> most_deregister_component() guards against a bug in mostcore: it
> currently does not call disconnect_channel() for linked channels on
> deregistration, so if that ever changes unexpectedly, video_devices
> could be non-empty.
> 
> Replace BUG_ON with WARN_ON_ONCE so the kernel stays up, and add a
> recovery path that drains and frees any remaining devices to avoid
> memory leaks in that error case.
> 
> Also document what the spinlock and mutex in struct most_video_dev
> each protect.
> ---
>  drivers/staging/most/video/video.c | 19 ++++++++++++++++---
>  1 file changed, 16 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/most/video/video.c b/drivers/staging/most/video/video.c
> index 04351f8ccccf1..4ade49569bd63 100644
> --- a/drivers/staging/most/video/video.c
> +++ b/drivers/staging/most/video/video.c
> @@ -33,14 +33,14 @@ struct most_video_dev {
>  	bool mute;
>  
>  	struct list_head pending_mbos;
> -	spinlock_t list_lock;
> +	spinlock_t list_lock; /* protects pending_mbos and mute */
>  
>  	struct v4l2_device v4l2_dev;
>  	atomic_t access_ref;
>  	struct video_device *vdev;
>  	unsigned int ctrl_input;
>  
> -	struct mutex lock;
> +	struct mutex lock; /* v4l2 device lock */
>  
>  	wait_queue_head_t wait_data;
>  };
> @@ -577,7 +577,20 @@ static void __exit comp_exit(void)
>  
>  	most_deregister_configfs_subsys(&comp);
>  	most_deregister_component(&comp);
> -	BUG_ON(!list_empty(&video_devices));
> +
> +	if (WARN_ON_ONCE(!list_empty(&video_devices))) {
> +		/* clean up any devices unexpectedly added during deregister phase */
> +		spin_lock_irq(&list_lock);
> +		list_replace_init(&video_devices, &free_list);
> +		spin_unlock_irq(&list_lock);
> +
> +		list_for_each_entry_safe(mdev, tmp, &free_list, list) {
> +			list_del_init(&mdev->list);
> +			comp_unregister_videodev(mdev);
> +			v4l2_device_disconnect(&mdev->v4l2_dev);
> +			v4l2_device_put(&mdev->v4l2_dev);
> +		}
> +	}
>  }
>  
>  module_init(comp_init);
> -- 
> 2.43.0
> 
> 

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- Your patch does not have a Signed-off-by: line.  Please read the
  kernel file, Documentation/process/submitting-patches.rst and resend
  it after adding that line.  Note, the line needs to be in the body of
  the email, before the patch, not at the bottom of the patch or in the
  email signature.

- Your patch did many different things all at once, making it difficult
  to review.  All Linux kernel patches need to only do one thing at a
  time.  If you need to do multiple things (such as clean up all coding
  style issues in a file/driver), do it in a sequence of patches, each
  one doing only one thing.  This will make it easier to review the
  patches to ensure that they are correct, and to help alleviate any
  merge issues that larger patches can cause.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot

  reply	other threads:[~2026-04-20 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20 11:35 [PATCH] staging: most: video: replace BUG_ON with WARN_ON_ONCE and add recovery Matan Cohen
2026-04-20 12:35 ` Greg KH [this message]
2026-04-20 14:14 ` Dan Carpenter
2026-04-21 15:15   ` Matan Cohen
2026-04-21 15:22     ` 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=2026042033-elevate-company-449c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=christian.gromm@microchip.com \
    --cc=linux-staging@lists.linux.dev \
    --cc=matan@matanco.space \
    --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