mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
	srinivas.pandruvada@linux.intel.com,
	"David E. Box" <david.e.box@linux.intel.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] platform/x86/intel/vsec: Remove a useless mutex
Date: Sat, 2 Nov 2024 20:39:52 +0100	[thread overview]
Message-ID: <b318af93-cbde-486d-854d-918b61795b1f@redhat.com> (raw)
In-Reply-To: <ccc08a262304f7f8c2e435349f0f714ebf9acfcd.1730563031.git.christophe.jaillet@wanadoo.fr>

Hi,

On 2-Nov-24 4:59 PM, Christophe JAILLET wrote:
> ida_alloc()/ida_free() don't need any mutex, so remove this one.
> 
> It was introduced by commit 9a90ea7d3784 ("platform/x86/intel/vsec: Use
> mutex for ida_alloc() and ida_free()").
> 
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> See:
> https://elixir.bootlin.com/linux/v6.11.2/source/lib/idr.c#L375
> https://elixir.bootlin.com/linux/v6.11.2/source/lib/idr.c#L484
> 
> Review with care. This patch is clearly the opposite of the one in Fixes
> which states that locking IS needed.
> IIUC, idr_ functions need locking, but not ida_.
> 
> If I'm wrong, could you elaborate why? (because many other places will
> need to be fixed and the doc certainly needs updating)

This is my bad, looking at the ida docs they clearly state
no locking is necessary.

Back then I was working on / reviewing some other stuff using
idr which does need locking and I likely simply confused the 2
and suggested for the locking to be added.

Anyways dropping the locking looks good to me:

Reviewed-by: Hans de Goede <hdegoede@redhat.com>

Regards,

Hans



> ---
>  drivers/platform/x86/intel/vsec.c | 6 ------
>  1 file changed, 6 deletions(-)
> 
> diff --git a/drivers/platform/x86/intel/vsec.c b/drivers/platform/x86/intel/vsec.c
> index 7b5cc9993974..9e0f8e38178c 100644
> --- a/drivers/platform/x86/intel/vsec.c
> +++ b/drivers/platform/x86/intel/vsec.c
> @@ -79,17 +79,13 @@ static void intel_vsec_remove_aux(void *data)
>  	auxiliary_device_uninit(data);
>  }
>  
> -static DEFINE_MUTEX(vsec_ida_lock);
> -
>  static void intel_vsec_dev_release(struct device *dev)
>  {
>  	struct intel_vsec_device *intel_vsec_dev = dev_to_ivdev(dev);
>  
>  	xa_erase(&auxdev_array, intel_vsec_dev->id);
>  
> -	mutex_lock(&vsec_ida_lock);
>  	ida_free(intel_vsec_dev->ida, intel_vsec_dev->auxdev.id);
> -	mutex_unlock(&vsec_ida_lock);
>  
>  	kfree(intel_vsec_dev->resource);
>  	kfree(intel_vsec_dev);
> @@ -113,9 +109,7 @@ int intel_vsec_add_aux(struct pci_dev *pdev, struct device *parent,
>  		return ret;
>  	}
>  
> -	mutex_lock(&vsec_ida_lock);
>  	id = ida_alloc(intel_vsec_dev->ida, GFP_KERNEL);
> -	mutex_unlock(&vsec_ida_lock);
>  	if (id < 0) {
>  		xa_erase(&auxdev_array, intel_vsec_dev->id);
>  		kfree(intel_vsec_dev->resource);


  reply	other threads:[~2024-11-02 19:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-02 15:59 Christophe JAILLET
2024-11-02 19:39 ` Hans de Goede [this message]
2024-11-04 13:16 ` Ilpo Järvinen

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=b318af93-cbde-486d-854d-918b61795b1f@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=david.e.box@linux.intel.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=srinivas.pandruvada@linux.intel.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

all inboxes | Powered by JetHome®