From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Umang Jain <umang.jain@ideasonboard.com>
Cc: linux-staging@lists.linux.dev,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>,
Dan Carpenter <error27@gmail.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Phil Elwell <phil@raspberrypi.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
"Ricardo B . Marliere" <ricardo@marliere.net>
Subject: Re: [PATCH 2/9] staging: vc04_services: Log using pr_err() when vchiq_state is unset
Date: Thu, 23 Nov 2023 13:02:01 +0000 [thread overview]
Message-ID: <2023112312-epic-viscosity-3848@gregkh> (raw)
In-Reply-To: <20231107095156.365492-3-umang.jain@ideasonboard.com>
On Tue, Nov 07, 2023 at 04:51:49AM -0500, Umang Jain wrote:
> In cases, where the global vchiq state is still unset, we cannot log
> to dynamic debug (access to struct device is needed, hence potential
> NULL de-reference). Log using pr_err() instead.
No, something is wrong here, don't do that.
> In vchiq_initialise(), remove the 'goto' because it is just again
> trying to log to dynamic debug. Simply return with -ENNOTCONN after
> logging to pr_err().
>
> In vchiq_open(), move the vchiq_log_debug() after the state pointer
> null check.
>
> Signed-off-by: Umang Jain <umang.jain@ideasonboard.com>
> Reviewed-by: Ricardo B. Marliere <ricardo@marliere.net>
> ---
> .../staging/vc04_services/interface/vchiq_arm/vchiq_arm.c | 6 ++----
> .../staging/vc04_services/interface/vchiq_arm/vchiq_dev.c | 7 +++----
> 2 files changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c
> index 9fb8f657cc78..9fb3e240d9de 100644
> --- a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c
> +++ b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c
> @@ -687,10 +687,8 @@ int vchiq_initialise(struct vchiq_instance **instance_out)
> usleep_range(500, 600);
> }
> if (i == VCHIQ_INIT_RETRIES) {
> - vchiq_log_error(state->dev, VCHIQ_CORE, "%s: videocore not initialized\n",
> - __func__);
> - ret = -ENOTCONN;
> - goto failed;
> + pr_err("%s: videocore not initialized\n", __func__);
> + return -ENOTCONN;
Here's a good reason to get rid of the crazy "this subsystem is special
so let us use a custom logging macro" logic.
Convert everything to just use real dev_*() calls so it makes it obvious
what is happening and how it all is working. It will save you from
doing stuff like this in the future as you will "know" that there isn't
a valid device pointer here.
thanks,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-11-23 13:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 9:51 [PATCH 0/9] staging: vc04_services: Smatch fixes and remove custom logging Umang Jain
2023-11-07 9:51 ` [PATCH 1/9] staging: vc04_services: vchiq_core: Log through struct vchiq_instance Umang Jain
2023-11-23 12:57 ` Greg Kroah-Hartman
2023-11-23 13:42 ` Laurent Pinchart
2023-11-23 12:58 ` Greg Kroah-Hartman
2023-11-07 9:51 ` [PATCH 2/9] staging: vc04_services: Log using pr_err() when vchiq_state is unset Umang Jain
2023-11-23 13:02 ` Greg Kroah-Hartman [this message]
2023-11-07 9:51 ` [PATCH 3/9] staging: vc04_services: bcm2835-camera: Remove redundant null check Umang Jain
2023-11-07 9:51 ` [PATCH 4/9] staging: vc04_services: Shorten helper function name Umang Jain
2023-11-07 12:32 ` Kieran Bingham
2023-11-23 13:11 ` Greg Kroah-Hartman
2023-11-07 9:51 ` [PATCH 5/9] staging: vc04_services: Do not pass NULL to vchiq_log_error() Umang Jain
2023-11-07 12:25 ` Laurent Pinchart
2023-11-07 12:31 ` Umang Jain
2023-11-07 12:38 ` Laurent Pinchart
2023-11-23 12:57 ` Greg Kroah-Hartman
2023-11-23 13:41 ` Laurent Pinchart
2023-11-23 13:55 ` Greg Kroah-Hartman
2023-11-07 12:36 ` Laurent Pinchart
2023-11-10 10:21 ` Stefan Wahren
2023-11-13 13:44 ` Umang Jain
2023-11-28 6:22 ` Umang Jain
2023-11-07 9:51 ` [PATCH 6/9] staging: vc04_services: Drop vchiq_log_error() in favour of dev_dbg Umang Jain
2023-11-23 13:02 ` Greg Kroah-Hartman
2023-11-23 13:49 ` Laurent Pinchart
2023-11-23 13:53 ` Greg Kroah-Hartman
2023-11-23 17:28 ` Laurent Pinchart
2023-11-23 17:31 ` Greg Kroah-Hartman
2023-11-23 18:00 ` Laurent Pinchart
2023-11-26 10:26 ` Greg Kroah-Hartman
2023-11-26 14:52 ` Laurent Pinchart
2023-11-07 9:51 ` [PATCH 7/9] staging: vc04_services: Drop vchiq_log_warning() " Umang Jain
2023-11-23 13:04 ` Greg Kroah-Hartman
2023-11-07 9:51 ` [PATCH 8/9] staging: vc04_services: Drop vchiq_log_trace() " Umang Jain
2023-11-07 9:51 ` [PATCH 9/9] staging: vc04_services: Drop vchiq_log_debug() " Umang Jain
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=2023112312-epic-viscosity-3848@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=error27@gmail.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@raspberrypi.com \
--cc=ricardo@marliere.net \
--cc=stefan.wahren@i2se.com \
--cc=umang.jain@ideasonboard.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;
as well as URLs for NNTP newsgroup(s).