On Tue, 2008-03-18 at 14:32 +0100, Hannes Reinecke wrote:
> With the target rework we cannot set the attribute of the
> sysfs files as the sysfs object is not registered yet. So
> just modify the attribute itself.
>
> Signed-off-by: Hannes Reinecke <hare@xxxxxxx>
> ---
> drivers/scsi/scsi_transport_spi.c | 10 +++++-----
> 1 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/scsi/scsi_transport_spi.c b/drivers/scsi/scsi_transport_spi.c
> index bc12b5d..4f9c98c 100644
> --- a/drivers/scsi/scsi_transport_spi.c
> +++ b/drivers/scsi/scsi_transport_spi.c
> @@ -1473,13 +1473,13 @@ static int spi_target_configure(struct transport_container *tc,
> * to ignore, sysfs also does a WARN_ON and dumps a trace,
> * which is bad, so temporarily, skip attributes that are
> * already visible (the revalidate one) */
> - if (j && attr != &dev_attr_revalidate.attr)
> + if (j && attr != &dev_attr_revalidate.attr) {
> + if ((j & 1))
> + attr->mode |= S_IWUSR;
> +
> rc = sysfs_add_file_to_group(kobj, attr,
> target_attribute_group.name);
> - /* and make the attribute writeable if we have a set
> - * function */
> - if ((j & 1))
> - rc = sysfs_chmod_file(kobj, attr, attr->mode | S_IWUSR);
> + }
> }
We can't do it like this, I'm afraid. The attribute passed in is global
to the entire transport class. You'd basically make every following
revalidate attribute writeable.
My initial reaction is that the target should obviously be visible when
we call configure, the same way the device is. Could this be fixed just
by moving the configure event?
James
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
