rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kurt Borja" <kuurtb@gmail.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	<linux-kernel@vger.kernel.org>
Cc: <rust-for-linux@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Danilo Krummrich" <dakr@kernel.org>
Subject: Re: [PATCH] driver core: faux: only create the device if probe() succeeds
Date: Tue, 25 Feb 2025 08:23:42 -0500	[thread overview]
Message-ID: <D81K5EDVAF9B.1MY63B8DYC7PE@gmail.com> (raw)
In-Reply-To: <2025022545-unroasted-common-fa0e@gregkh>

On Tue Feb 25, 2025 at 1:35 AM -05, Greg Kroah-Hartman wrote:
> It's really hard to know if a faux device properly passes the callback
> to probe() without having to poke around in the faux_device structure
> and then clean up.  Instead of having to have every user of the api do
> this logic, just do it in the faux device core itself.
>
> This makes the use of a custom probe() callback for a faux device much
> simpler overall.
>
> Suggested-by: Kurt Borja <kuurtb@gmail.com>
> Cc: "Rafael J. Wysocki" <rafael@kernel.org>
> Cc: Danilo Krummrich <dakr@kernel.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Thanks for considering this!

Reviewed-by: Kurt Borja <kuurtb@gmail.com>

> ---
>  drivers/base/faux.c |   15 ++++++++++++++-
>  1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/base/faux.c b/drivers/base/faux.c
> index 531e9d789ee0..407c1d1aad50 100644
> --- a/drivers/base/faux.c
> +++ b/drivers/base/faux.c
> @@ -102,7 +102,9 @@ static void faux_device_release(struct device *dev)
>   *
>   * Note, when this function is called, the functions specified in struct
>   * faux_ops can be called before the function returns, so be prepared for
> - * everything to be properly initialized before that point in time.
> + * everything to be properly initialized before that point in time.  If the
> + * probe callback (if one is present) does NOT succeed, the creation of the
> + * device will fail and NULL will be returned.
>   *
>   * Return:
>   * * NULL if an error happened with creating the device
> @@ -147,6 +149,17 @@ struct faux_device *faux_device_create_with_groups(const char *name,
>  		return NULL;
>  	}
>  
> +	/*
> +	 * Verify that we did bind the driver to the device (i.e. probe worked),
> +	 * if not, let's fail the creation as trying to guess if probe was
> +	 * successful is almost impossible to determine by the caller.
> +	 */
> +	if (!dev->driver) {
> +		dev_err(dev, "probe did not succeed, tearing down the device\n");
> +		faux_device_destroy(faux_dev);
> +		faux_dev = NULL;
> +	}
> +
>  	return faux_dev;
>  }
>  EXPORT_SYMBOL_GPL(faux_device_create_with_groups);
-- 
 ~ Kurt

      parent reply	other threads:[~2025-02-25 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25  6:35 [PATCH] driver core: faux: only create the device if probe() succeeds Greg Kroah-Hartman
2025-02-25 11:24 ` Danilo Krummrich
2025-02-26 19:32   ` Greg Kroah-Hartman
2025-02-25 13:23 ` Kurt Borja [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=D81K5EDVAF9B.1MY63B8DYC7PE@gmail.com \
    --to=kuurtb@gmail.com \
    --cc=dakr@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rust-for-linux@vger.kernel.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 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).