Hi Mike,
On Tue, 1 Sep 2020 22:17:51 -0500, Michael Christie wrote:
> > --- a/drivers/target/target_core_xcopy.c
> > +++ b/drivers/target/target_core_xcopy.c
> > @@ -68,8 +68,14 @@ static int target_xcopy_locate_se_dev_e4_iter(struct se_device *se_dev,
> > if (rc != 0)
> > return 0;
> >
> > - info->found_dev = se_dev;
> > pr_debug("XCOPY 0xe4: located se_dev: %p\n", se_dev);
> > + if (info->found_dev) {
> > + pr_warn("XCOPY 0xe4 descriptor conflict for se_dev %p and %p\n",
> > + info->found_dev, se_dev);
> > + target_undepend_item(&info->found_dev->dev_group.cg_item);
> > + return -ENOTUNIQ;
> > + }
> > + info->found_dev = se_dev;
>
> Was it valid to copy to/from the same LUN? You would copy from/to different src/destinations on that LUN. Would your patch break that?
XCOPY allows for copies to occur on the same LUN or between separate
src/destinations. The intention of this patch is that regardless of the
source or destination, if the NAA WWN could refer to multiple LUNs on
the same target (via target_for_each_device()) then the XCOPY should
fail and force the initiator to fallback to initiator driver copy.
Cheers, David
