From: Bart Van Assche <bvanassche@acm.org>
To: Ye Bin <yebin10@huawei.com>,
jejb@linux.ibm.com, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATH v2] scsi: scsi_dh_rdac: Avoid crash during rdac_bus_attach
Date: Thu, 22 Jul 2021 21:04:18 -0700 [thread overview]
Message-ID: <a1113b04-e320-a12b-5a59-ec7479d5eec1@acm.org> (raw)
In-Reply-To: <20210113063103.2698953-1-yebin10@huawei.com>
On 1/12/21 10:31 PM, Ye Bin wrote:
> sdev->handler_data = NULL;
> + synchronize_rcu();
> kfree(h);
What is the purpose of the new synchronize_rcu() call? If its purpose is
to wait until *h is no longer in use, please use kfree_rcu() instead.
Thanks,
Bart.
next prev parent reply other threads:[~2021-07-23 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 6:31 [PATH v2] scsi: scsi_dh_rdac: Avoid crash during rdac_bus_attach Ye Bin
2021-07-22 13:09 ` yebin
2021-07-23 4:04 ` Bart Van Assche [this message]
2021-07-28 14:24 ` yebin
2021-07-28 21:55 ` Bart Van Assche
2021-07-29 3:37 ` 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=a1113b04-e320-a12b-5a59-ec7479d5eec1@acm.org \
--to=bvanassche@acm.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=yebin10@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;
as well as URLs for NNTP newsgroup(s).