mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Yu Kuai <yukuai1@huaweicloud.com>,
	hch@lst.de, chaitanyak@nvidia.com, shinichiro.kawasaki@wdc.com,
	dgilbert@interlog.com, jejb@linux.ibm.com,
	martin.petersen@oracle.com, yukuai3@huawei.com, axboe@kernel.dk
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	yi.zhang@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH] scsi/sg: don't grab scsi host module reference
Date: Wed, 21 Jun 2023 09:06:24 -0700	[thread overview]
Message-ID: <02a90139-a94a-ea1d-cc36-8b4b66a96bba@acm.org> (raw)
In-Reply-To: <20230621160111.1433521-1-yukuai1@huaweicloud.com>

On 6/21/23 09:01, Yu Kuai wrote:
> From: Yu Kuai <yukuai3@huawei.com>
> 
> In order to prevent request_queue to be freed before cleaning up
> blktrace debugfs entries, commit db59133e9279 ("scsi: sg: fix blktrace
> debugfs entries leakage") use scsi_device_get(), however,
> scsi_device_get() will also grab scsi module reference and scsi module
> can't be removed.

I just noticed that this patch has been posted on the linux-scsi mailing 
list. If you plan to resend this patch, please send it to Jens and Cc 
both linux-block and linux-scsi because this patch fixes a bug in a 
patch that only exists in Jens' tree.

Thanks,

Bart.


  parent reply	other threads:[~2023-06-21 16:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 16:01 Yu Kuai
2023-06-21 15:47 ` Bart Van Assche
2023-06-21 16:06 ` Bart Van Assche [this message]
2023-06-23  5:44 ` Christoph Hellwig
2023-06-23 14:28 ` Jens Axboe
2023-07-04 17:04 ` Marc Hartmayer
2023-07-04 18:51   ` Benjamin Block
2023-07-05  2:16     ` Yu Kuai
2023-07-05  2:26       ` Yu Kuai
2023-07-05  1:43   ` Yu Kuai
2023-07-05  2:28     ` Yu Kuai
2023-07-05  6:13       ` Marc Hartmayer

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=02a90139-a94a-ea1d-cc36-8b4b66a96bba@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=chaitanyak@nvidia.com \
    --cc=dgilbert@interlog.com \
    --cc=hch@lst.de \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai1@huaweicloud.com \
    --cc=yukuai3@huawei.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®