All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Freudenberger <freude@linux.ibm.com>
To: Tony Krowiak <akrowiak@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, jjherne@linux.ibm.com,
	borntraeger@de.ibm.com
Subject: Re: [PATCH] s390/ap: fixes bug in the AP bus's __verify_queue_reservations function
Date: Thu, 07 Jul 2022 08:47:38 +0200	[thread overview]
Message-ID: <e0cfef0c765e577d86be53c9606cbca3@linux.ibm.com> (raw)
In-Reply-To: <20220706222619.602094-1-akrowiak@linux.ibm.com>

On 2022-07-07 00:26, Tony Krowiak wrote:
> The AP bus's __verify_queue_reservations function increments the ref 
> count
> for the device driver passed in as a parameter, but fails to decrement 
> it
> before returning control to the caller. This will prevents any 
> subsequent
> removal of the module.
> 
> Signed-off-by: Tony Krowiak <akrowiak@linux.ibm.com>
> Reported-by: Tony Krowiak <akrowiak@linux.ibm.com>
> ---
>  drivers/s390/crypto/ap_bus.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/s390/crypto/ap_bus.c 
> b/drivers/s390/crypto/ap_bus.c
> index 5c13d2079d96..0a9045b49c50 100644
> --- a/drivers/s390/crypto/ap_bus.c
> +++ b/drivers/s390/crypto/ap_bus.c
> @@ -1435,7 +1435,7 @@ static int __verify_queue_reservations(struct
> device_driver *drv, void *data)
>  	if (ap_drv->in_use) {
>  		rc = ap_drv->in_use(ap_perms.apm, newaqm);
>  		if (rc)
> -			return -EBUSY;
> +			rc = -EBUSY;
>  	}
> 
>  	/* release the driver's module */
Tony, good catch. Thanks. Please add my Reviewed-by: Harald 
Freudenberger <freude@linux.ibm.com>
and then commit into devel and cc stable.

  reply	other threads:[~2022-07-07  6:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 22:26 [PATCH] s390/ap: fixes bug in the AP bus's __verify_queue_reservations function Tony Krowiak
2022-07-07  6:47 ` Harald Freudenberger [this message]
2022-07-11 17:31   ` Anthony Krowiak

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=e0cfef0c765e577d86be53c9606cbca3@linux.ibm.com \
    --to=freude@linux.ibm.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=jjherne@linux.ibm.com \
    --cc=linux-s390@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 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.