From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Saravana Kannan <saravanak@google.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"open list:TARGET SUBSYSTEM" <linux-scsi@vger.kernel.org>,
Avri Altman <avri.altman@wdc.com>, Bean Huo <huobean@gmail.com>,
Can Guo <cang@codeaurora.org>,
Asutosh Das <asutoshd@codeaurora.org>,
Bart Van Assche <bvanassche@acm.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3 1/3] driver core: Prevent warning when removing a device link from unregistered consumer
Date: Wed, 14 Jul 2021 20:22:06 +0200 [thread overview]
Message-ID: <CAJZ5v0iPXYvmOPv-kQnzMbkqNZtaZ9TMgJht5=VNnx0t3gi1Dw@mail.gmail.com> (raw)
In-Reply-To: <20210710103819.12532-2-adrian.hunter@intel.com>
On Sat, Jul 10, 2021 at 12:38 PM Adrian Hunter <adrian.hunter@intel.com> wrote:
>
> sysfs_remove_link() causes a warning if the parent directory does not
> exist. That can happen if the device link consumer has not been registered.
> So do not attempt sysfs_remove_link() in that case.
>
> Fixes: 287905e68dd29 ("driver core: Expose device link details in sysfs")
> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
Reviewed-by: Rafael J. Wysocki <rafael@kernel.org>
> ---
> drivers/base/core.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/base/core.c b/drivers/base/core.c
> index ea5b85354526..2de8f7d8cf54 100644
> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -575,8 +575,10 @@ static void devlink_remove_symlinks(struct device *dev,
> return;
> }
>
> - snprintf(buf, len, "supplier:%s:%s", dev_bus_name(sup), dev_name(sup));
> - sysfs_remove_link(&con->kobj, buf);
> + if (device_is_registered(con)) {
> + snprintf(buf, len, "supplier:%s:%s", dev_bus_name(sup), dev_name(sup));
> + sysfs_remove_link(&con->kobj, buf);
> + }
> snprintf(buf, len, "consumer:%s:%s", dev_bus_name(con), dev_name(con));
> sysfs_remove_link(&sup->kobj, buf);
> kfree(buf);
> --
> 2.17.1
>
next prev parent reply other threads:[~2021-07-14 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 10:38 [PATCH V3 0/3] driver core: Add ability to delete device links of unregistered devices Adrian Hunter
2021-07-10 10:38 ` [PATCH V3 1/3] driver core: Prevent warning when removing a device link from unregistered consumer Adrian Hunter
2021-07-10 15:19 ` Greg Kroah-Hartman
2021-07-14 18:21 ` Rafael J. Wysocki
2021-07-14 18:22 ` Rafael J. Wysocki [this message]
2021-07-10 10:38 ` [PATCH V3 2/3] driver core: Add ability to delete device links of unregistered devices Adrian Hunter
2021-07-14 18:26 ` Rafael J. Wysocki
2021-07-10 10:38 ` [PATCH V3 3/3] scsi: ufshcd: Fix device links when BOOT WLUN fails to probe Adrian Hunter
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='CAJZ5v0iPXYvmOPv-kQnzMbkqNZtaZ9TMgJht5=VNnx0t3gi1Dw@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=huobean@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=saravanak@google.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).