linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	James Bottomley <jbottomley@odin.com>,
	Ewan Milne <emilne@redhat.com>,
	Bart van Assche <bart.vanassche@sandisk.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 11/20] scsi_dh_alua: Use workqueue for RTPG
Date: Wed, 30 Dec 2015 14:19:24 +0100	[thread overview]
Message-ID: <20151230131923.GA15270@lst.de> (raw)
In-Reply-To: <1449560260-53407-12-git-send-email-hare@suse.de>

This looks good in general, but a couple nitpicks below:

> +static uint optimize_stpg;
> +module_param(optimize_stpg, uint, S_IRUGO|S_IWUSR);
> +MODULE_PARM_DESC(optimize_stpg, "Allow use of a non-optimized path, rather than sending a STPG, when implicit TPGS is supported (0=No,1=Yes). Default is 0.");

why is this moved around in this patch?  It doesn't seem related to the
rest of it, and isn't documented in the changelog either.

>  {
> -	struct alua_port_group *pg = NULL;
> +	struct alua_port_group *pg;

looks like this should be folded into the patch that introduces the
unessecary NULL assignment.

>  	list_for_each_entry(pg, &port_group_list, node) {
>  		if (pg->group_id != group_id)
> @@ -214,18 +240,26 @@ struct alua_port_group *alua_get_pg(struct scsi_device *sdev,
>  	pg->group_id = group_id;
>  	pg->tpgs = tpgs;
>  	pg->state = TPGS_STATE_OPTIMIZED;
> +	if (optimize_stpg)
> +		pg->flags |= ALUA_OPTIMIZE_STPG;


why is this moved earlier here?  Doing it from the beginning seems
useful to me, but I'd expect it in a separate patch with a proper
description.

>  	kref_init(&pg->kref);
> +	INIT_DELAYED_WORK(&pg->rtpg_work, alua_rtpg_work);
> +	INIT_LIST_HEAD(&pg->rtpg_list);
> +	INIT_LIST_HEAD(&pg->node);
> +	spin_lock_init(&pg->lock);
>  
>  	/* Re-check list again to catch concurrent updates */
>  	spin_lock(&port_group_lock);
>  	tmp_pg = alua_lookup_pg(id_str, id_size, group_id);
>  	if (tmp_pg) {
>  		spin_unlock(&port_group_lock);
> -		kfree(pg);
> -		return tmp_pg;
> +		kref_put(&pg->kref, release_port_group);
> +		pg = tmp_pg;
> +		tmp_pg = NULL;

The only thing release_port_group does in addition to the kfree
is a list_del on pg->entry.  But given that we never added
the pg to a list it doesn't need to be deleted, and it can't
have another reference.  Why this change?

While we're at it, there are 6 calls to
'kref_put(&pg->kref, release_port_group)' in addition to this one,
so it might make sense to add a helper for it to the patch introducing
struct alua_port_group.

>   * Extract the relative target port and the target port group
>   * descriptor from the list of identificators.
>   *
> - * Returns 0 or SCSI_DH_ error code on failure.
> + * Returns the target port group id or -1 on failure

That's not how I interpret the code below, it seems to always return
SCSI_DH_* values.

> +	struct alua_port_group *pg = NULL, *old_pg = NULL;
> +	bool pg_found = false;

> +	pg = alua_get_pg(sdev, group_id, tpgs, id_str, id_size);
> +	if (!pg)
>  		return SCSI_DH_NOMEM;
> +	/* Check for existing port_group references */
> +	spin_lock(&h->pg_lock);
> +	if (h->pg) {
> +		old_pg = pg;
> +		/* port_group has changed. Update to new port group */
> +		if (h->pg != pg) {
> +			old_pg = h->pg;
> +			rcu_assign_pointer(h->pg, pg);
> +			h->pg->expiry = 0;

why do we set expiry to 0 here, but not if we didn't have a pg
yet?  This could use a comment not just here but in all the places
that set it to zero.

> +			pg_found = true;

pg_found should be pg_updated, right?

> +	if (pg_found)
> +		synchronize_rcu();
> +	if (old_pg) {
> +		if (old_pg->rtpg_sdev)
> +			flush_delayed_work(&old_pg->rtpg_work);
> +		kref_put(&old_pg->kref, release_port_group);
> +	}

This code looks odd.  I can't see why we need a synchronize_rcu here.
The only thing we should need is a kfree_rcu for the final free in
release_port_group.  I also don't quite understand the flush_delayed_work.
As far as I can tell we only need it if rtpg_sdev is the sdev passed
in, so it we probably should check for that.

  reply	other threads:[~2015-12-30 13:19 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08  7:37 [PATCH 00/20] ALUA device handler update, part II Hannes Reinecke
2015-12-08  7:37 ` [PATCH 01/20] scsi_dh_alua: Pass buffer as function argument Hannes Reinecke
2015-12-08  7:37 ` [PATCH 02/20] scsi_dh_alua: separate out alua_stpg() Hannes Reinecke
2015-12-30 11:06   ` Christoph Hellwig
2015-12-08  7:37 ` [PATCH 03/20] scsi_dh_alua: Make stpg synchronous Hannes Reinecke
2015-12-30 11:10   ` Christoph Hellwig
2015-12-08  7:37 ` [PATCH 04/20] scsi_dh_alua: call alua_rtpg() if stpg fails Hannes Reinecke
2015-12-30 11:10   ` Christoph Hellwig
2015-12-08  7:37 ` [PATCH 05/20] scsi_dh_alua: switch to scsi_execute_req_flags() Hannes Reinecke
2015-12-08  7:37 ` [PATCH 06/20] scsi_dh_alua: Use separate alua_port_group structure Hannes Reinecke
2015-12-30 11:17   ` Christoph Hellwig
2015-12-31 12:47     ` Hannes Reinecke
2015-12-08  7:37 ` [PATCH 07/20] scsi_dh_alua: allocate RTPG buffer separately Hannes Reinecke
2015-12-08  7:37 ` [PATCH 08/20] scsi_dh_alua: use unique device id Hannes Reinecke
2015-12-30 11:20   ` Christoph Hellwig
2015-12-31 12:53     ` Hannes Reinecke
2015-12-08  7:37 ` [PATCH 09/20] scsi_dh_alua: simplify alua_initialize() Hannes Reinecke
2015-12-30 11:21   ` Christoph Hellwig
2015-12-08  7:37 ` [PATCH 10/20] revert commit a8e5a2d593cb ("[SCSI] scsi_dh_alua: ALUA handler attach should succeed while TPG is transitioning") Hannes Reinecke
2015-12-30 11:22   ` Christoph Hellwig
2015-12-31 12:54     ` Hannes Reinecke
2015-12-08  7:37 ` [PATCH 11/20] scsi_dh_alua: Use workqueue for RTPG Hannes Reinecke
2015-12-30 13:19   ` Christoph Hellwig [this message]
2015-12-31 13:01     ` Hannes Reinecke
2016-01-03 10:53       ` Christoph Hellwig
2015-12-08  7:37 ` [PATCH 12/20] scsi_dh_alua: Allow workqueue to run synchronously Hannes Reinecke
2015-12-30 13:20   ` Christoph Hellwig
2015-12-31 13:54     ` Hannes Reinecke
2016-01-03 10:54       ` Christoph Hellwig
2015-12-08  7:37 ` [PATCH 13/20] scsi_dh_alua: Recheck state on unit attention Hannes Reinecke
2015-12-30 13:22   ` Christoph Hellwig
2015-12-31 14:02     ` Hannes Reinecke
2015-12-08  7:37 ` [PATCH 14/20] scsi_dh_alua: update all port states Hannes Reinecke
2015-12-30 13:23   ` Christoph Hellwig
2015-12-31 14:09     ` Hannes Reinecke
2015-12-08  7:37 ` [PATCH 15/20] scsi_dh_alua: Send TEST UNIT READY to poll for transitioning Hannes Reinecke
2015-12-30 13:24   ` Christoph Hellwig
2015-12-08  7:37 ` [PATCH 16/20] scsi_dh: add 'rescan' callback Hannes Reinecke
2015-12-30 13:24   ` Christoph Hellwig
2015-12-08  7:37 ` [PATCH 17/20] scsi: Add 'access_state' attribute Hannes Reinecke
2015-12-30 13:24   ` Christoph Hellwig
2015-12-30 13:26   ` Christoph Hellwig
2015-12-08  7:37 ` [PATCH 18/20] scsi_dh_alua: use common definitions for ALUA state Hannes Reinecke
2015-12-30 13:28   ` Christoph Hellwig
2015-12-08  7:37 ` [PATCH 19/20] scsi_dh_alua: update 'access_state' field Hannes Reinecke
2015-12-30 13:34   ` Christoph Hellwig
2015-12-31 14:15     ` Hannes Reinecke
2015-12-08  7:37 ` [PATCH 20/20] scsi_dh_alua: Update version to 2.0 Hannes Reinecke
2015-12-08 15:06 ` [PATCH 00/20] ALUA device handler update, part II Hannes Reinecke

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=20151230131923.GA15270@lst.de \
    --to=hch@lst.de \
    --cc=bart.vanassche@sandisk.com \
    --cc=emilne@redhat.com \
    --cc=hare@suse.de \
    --cc=jbottomley@odin.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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).