On Mon, Jun 14, 2021 at 10:09:07AM -0700, Moritz Fischer wrote:
> From: Russ Weight <russell.h.weight@xxxxxxxxx>
>
> The FPGA manager class driver data structure is being treated as a
> managed resource instead of using the class.dev_release call-back
> function to release the class data structure. This change populates
> the class.dev_release function, changes the fpga_mgr_free() function
> to call put_device() and changes the fpga_mgr_unregister() function
> to call device_del() instead of device_unregister().
>
> Signed-off-by: Russ Weight <russell.h.weight@xxxxxxxxx>
> Reviewed-by: Xu Yilun <yilun.xu@xxxxxxxxx>
> Signed-off-by: Moritz Fischer <mdf@xxxxxxxxxx>
> ---
> drivers/fpga/fpga-mgr.c | 35 +++++++++++++++--------------------
> 1 file changed, 15 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/fpga/fpga-mgr.c b/drivers/fpga/fpga-mgr.c
> index 42ddc0844781..9f6c3760b6ff 100644
> --- a/drivers/fpga/fpga-mgr.c
> +++ b/drivers/fpga/fpga-mgr.c
> @@ -585,8 +585,10 @@ struct fpga_manager *fpga_mgr_create(struct device *parent, const char *name,
> return NULL;
>
> id = ida_simple_get(&fpga_mgr_ida, 0, 0, GFP_KERNEL);
> - if (id < 0)
> - goto error_kfree;
> + if (id < 0) {
> + kfree(mgr);
> + return NULL;
> + }
>
> mutex_init(&mgr->ref_mutex);
>
> @@ -602,17 +604,12 @@ struct fpga_manager *fpga_mgr_create(struct device *parent, const char *name,
> mgr->dev.id = id;
>
> ret = dev_set_name(&mgr->dev, "fpga%d", id);
> - if (ret)
> - goto error_device;
> + if (ret) {
> + put_device(&mgr->dev);
> + return NULL;
> + }
>
> return mgr;
> -
> -error_device:
> - ida_simple_remove(&fpga_mgr_ida, id);
> -error_kfree:
> - kfree(mgr);
> -
> - return NULL;
> }
> EXPORT_SYMBOL_GPL(fpga_mgr_create);
>
> @@ -622,8 +619,7 @@ EXPORT_SYMBOL_GPL(fpga_mgr_create);
> */
> void fpga_mgr_free(struct fpga_manager *mgr)
> {
> - ida_simple_remove(&fpga_mgr_ida, mgr->dev.id);
> - kfree(mgr);
> + put_device(&mgr->dev);
> }
> EXPORT_SYMBOL_GPL(fpga_mgr_free);
>
> @@ -692,16 +688,11 @@ int fpga_mgr_register(struct fpga_manager *mgr)
>
> ret = device_add(&mgr->dev);
> if (ret)
> - goto error_device;
> + return ret;
If this fails, are you sure you want to just return the error number?
You can not call device_del() afterward if this fails, you have to call
put_device(). See the documentation for device_add() for details.
This is messy as you are doing a "two step" initialization of your
fpga_manager device for some odd reason. Why do you need to do that?
When you call this you seem to be forced to do:
fpga_mgr_create()
fpga_mgr_register()
in each individual driver.
Why force drivers to do this and not just do a simple:
fpga_mgr_register()
that internally does the create/add process?
Why the two steps? That's normally reserved for when you need to do
something complex in the "core" for the subsystem, and shouldn't be
pushed out to each individual driver like it currently is for the fpga
core as you will run into the problem you have here.
Namely when you want to clean up from a failure, you don't know if you
really did register that device properly or not.
And no, don't add another flag, just make this simple and hard to get
wrong. As it is it feels like each fpga driver has to do extra work to
be sure to get this all correct each time.
So I can not take this as-is, sorry.
And sorry I never noticed these problems when the code when in
originally.
thanks,
greg k-h
