Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: "Merlijn B.W. Wajer" <merlijn@archive.org>
To: Bart Van Assche <bvanassche@acm.org>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>
Cc: linux-scsi@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	stable@kernel.org, simon@octiron.net
Subject: Re: [PATCH] sr: Fix sr_block_release()
Date: Mon, 30 Mar 2020 10:51:42 +0200	[thread overview]
Message-ID: <ed0b6af3-94c3-c184-f3fc-e6181ac0e843@archive.org> (raw)
In-Reply-To: <20200330025151.10535-1-bvanassche@acm.org>

Hi,

Oops, looks like Simon (CC) reported this earlier on too, missed that.

On 30/03/2020 04:51, Bart Van Assche wrote:
> This patch fixes the following two complaints:

Acked-By: Merlijn Wajer <merlijn@archive.org>

Cheers,
Merlijn

> 
> [snip]
> 
> Cc: Merlijn Wajer <merlijn@archive.org>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: <stable@kernel.org>
> Fixes: 51a858817dcd ("scsi: sr: get rid of sr global mutex")
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> ---
>  drivers/scsi/sr.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/scsi/sr.c b/drivers/scsi/sr.c
> index 0f1a926f6341..e8b2e014770c 100644
> --- a/drivers/scsi/sr.c
> +++ b/drivers/scsi/sr.c
> @@ -551,10 +551,12 @@ static int sr_block_open(struct block_device *bdev, fmode_t mode)
>  static void sr_block_release(struct gendisk *disk, fmode_t mode)
>  {
>  	struct scsi_cd *cd = scsi_cd(disk);
> +
>  	mutex_lock(&cd->lock);
>  	cdrom_release(&cd->cdi, mode);
> -	scsi_cd_put(cd);
>  	mutex_unlock(&cd->lock);
> +
> +	scsi_cd_put(cd);
>  }
>  
>  #ifndef CONFIG_COMPAT
> 

  reply	other threads:[~2020-03-30  8:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30  2:51 [PATCH] sr: Fix sr_block_release() Bart Van Assche
2020-03-30  8:51 ` Merlijn B.W. Wajer [this message]
2020-03-30  8:58   ` Merlijn B.W. Wajer
2020-04-01  2:11 ` Martin K. Petersen

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=ed0b6af3-94c3-c184-f3fc-e6181ac0e843@archive.org \
    --to=merlijn@archive.org \
    --cc=arnd@arndb.de \
    --cc=bvanassche@acm.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=simon@octiron.net \
    --cc=stable@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