From: John Garry <john.g.garry@oracle.com>
To: yangxingui <yangxingui@huawei.com>,
yanaijie@huawei.com, jejb@linux.ibm.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, liyihang9@h-partners.com,
liuyonglong@huawei.com, kangfenglong@huawei.com
Subject: Re: [PATCH v3 2/2] scsi: libsas: Add linkrate and sas_addr change detection in rediscover
Date: Fri, 22 May 2026 10:16:06 +0100 [thread overview]
Message-ID: <b99cd59f-b986-432e-aaf1-3b757e1c4c34@oracle.com> (raw)
In-Reply-To: <5600f8fa-489a-9b81-9966-dc5d436c462e@huawei.com>
On 21/05/2026 10:04, yangxingui wrote:
>>
>> Can this be reused (to lose and find the device with updated info)? Or
>> why not good enough?
>>
>> I don't know why you need full revalidation.
>
> Hi, John
> As the commit log. The existing pattern (unregister + sas_discover_new)
> handles the "replace" case where the SAS address changes completely,
> implying a different device.
> For the flutter case where we detect linkrate/sas_addr changes,
Can you please clarify this: you say that the existing pattern handles
"replace" case where the SAS address changes completely, and then
flutter case covers sas_addr changes.
What is the difference in the SAS address changes between the two cases?
we
> cannot reuse this synchronous pattern because:
> sas_unregister_devs_sas_addr() only marks the device as gone (sets
> SAS_DEV_GONE) and adds it to port->destroy_list. The actual sysfs
> cleanup (sas_rphy_delete) happens later in sas_destruct_devices() called
> at the end of sas_revalidate_domain() in sas_discover.c.
> I did try the approach you suggested (unregister + sas_discover_new),
> but it produces sysfs duplicate directory errors:
> Workqueue: 0000:74:02.0_disco_q sas_revalidate_domain
> Call trace:
> dump_backtrace+0x0/0x18c
> show_stack+0x14/0x1c
> dump_stack+0x88/0xac
> sysfs_warn_dup+0x64/0x7c
> sysfs_create_dir_ns+0x90/0xa0
> kobject_add_internal+0xa0/0x284
> kobject_add+0xb8/0x11c
> device_add+0xe8/0x598
> sas_port_add+0x24/0x50
> sas_ex_discover_devices+0xb10/0xc30
>
> The async pattern with DISCE_REVALIDATE_DOMAIN ensures proper ordering:
> 1. Old device added to destroy_list
> 2. Current revalidate work completes → sas_destruct_devices() truly
> deletes old device's sysfs
> 3. New DISCE_REVALIDATE_DOMAIN event triggers → discovery starts with
> clean sysfs state
> This follows libsas's async design pattern similar to sas_resume_devices
> in sas_port.c.
next prev parent reply other threads:[~2026-05-22 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 8:45 [PATCH v3 0/2] libsas: rediscover improvements for linkrate/sas_addr changes Xingui Yang
2026-05-15 8:45 ` [PATCH v3 1/2] scsi: libsas: refactor sas_ex_to_ata() using new helper sas_ex_to_dev() Xingui Yang
2026-05-21 8:04 ` John Garry
2026-05-15 8:45 ` [PATCH v3 2/2] scsi: libsas: Add linkrate and sas_addr change detection in rediscover Xingui Yang
2026-05-21 8:13 ` John Garry
2026-05-21 9:04 ` yangxingui
2026-05-22 9:16 ` John Garry [this message]
2026-05-25 2:25 ` yangxingui
2026-05-27 9:42 ` John Garry
2026-05-28 2:40 ` yangxingui
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=b99cd59f-b986-432e-aaf1-3b757e1c4c34@oracle.com \
--to=john.g.garry@oracle.com \
--cc=jejb@linux.ibm.com \
--cc=kangfenglong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=liyihang9@h-partners.com \
--cc=martin.petersen@oracle.com \
--cc=yanaijie@huawei.com \
--cc=yangxingui@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®