From: Dan Carpenter <dan.carpenter@linaro.org>
To: Abdelrahman Fekry <abdelrahmanfekry375@gmail.com>
Cc: hansg@kernel.org, mchehab@kernel.org,
sakari.ailus@linux.intel.com, andy@kernel.org,
gregkh@linuxfoundation.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH] staging: media: atomisp: Add lock asserts for mutex protection
Date: Fri, 15 Aug 2025 23:03:06 +0300 [thread overview]
Message-ID: <aJ-Sept8uMm2Opeq@stanley.mountain> (raw)
In-Reply-To: <20250815170901.32105-1-abdelrahmanfekry375@gmail.com>
On Fri, Aug 15, 2025 at 08:09:01PM +0300, Abdelrahman Fekry wrote:
> Add lockdep_assert_held(&isp->mutex) to critical functions accessing
> shared device state. This enforces proper locking and detects violations.
>
> Suggested-by: Hans de Goede <hdegoede@redhat.com>
> Signed-off-by: Abdelrahman Fekry <abdelrahmanfekry375@gmail.com>
> ---
> .../staging/media/atomisp/pci/atomisp_cmd.c | 3 ++
> .../media/atomisp/pci/atomisp_compat_css20.c | 31 +++++++++++++++++++
> 2 files changed, 34 insertions(+)
>
> diff --git a/drivers/staging/media/atomisp/pci/atomisp_cmd.c b/drivers/staging/media/atomisp/pci/atomisp_cmd.c
> index 3a4eb4f6d3be..48ca33e1c92d 100644
> --- a/drivers/staging/media/atomisp/pci/atomisp_cmd.c
> +++ b/drivers/staging/media/atomisp/pci/atomisp_cmd.c
> @@ -3794,6 +3794,7 @@ int atomisp_try_fmt(struct atomisp_device *isp, struct v4l2_pix_format *f,
> const struct atomisp_format_bridge **fmt_ret,
> const struct atomisp_format_bridge **snr_fmt_ret)
> {
> + lockdep_assert_held(&isp->mutex);
This should go after the declarations.
> const struct atomisp_format_bridge *fmt, *snr_fmt;
> struct atomisp_sub_device *asd = &isp->asd;
> struct v4l2_mbus_framefmt ffmt = { };
> @@ -4324,6 +4325,8 @@ static int atomisp_set_fmt_to_snr(struct video_device *vdev, const struct v4l2_p
> int atomisp_set_fmt(struct video_device *vdev, struct v4l2_format *f)
> {
> struct atomisp_device *isp = video_get_drvdata(vdev);
> + lockdep_assert_held(&isp->mutex);
Same. Etc...
> +
> struct atomisp_video_pipe *pipe = atomisp_to_video_pipe(vdev);
> struct atomisp_sub_device *asd = pipe->asd;
> const struct atomisp_format_bridge *format_bridge;
[ snip ]
> @@ -1726,6 +1746,10 @@ int atomisp_css_input_configure_port(
> {
> int i;
> struct atomisp_stream_env *stream_env;
> +
No blank line here.
> + struct atomisp_device *isp = asd->isp;
> +
> + lockdep_assert_held(&isp->mutex);
> /*
> * Calculate rx_count as follows:
> * Input: mipi_freq : CSI-2 bus frequency in Hz
regards,
dan carpenter
prev parent reply other threads:[~2025-08-15 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 17:09 [PATCH] staging: media: atomisp: Add lock asserts for mutex protection Abdelrahman Fekry
2025-08-15 20:03 ` Dan Carpenter [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=aJ-Sept8uMm2Opeq@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=abdelrahmanfekry375@gmail.com \
--cc=andy@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=skhan@linuxfoundation.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 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.