From: John Garry <john.garry@huawei.com>
To: James Bottomley <jejb@linux.ibm.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: luojiaxing <luojiaxing@huawei.com>,
"saravanak@google.com" <saravanak@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v1] driver core: Use list_del_init to replace list_del at device_links_purge()
Date: Wed, 8 Jan 2020 16:08:44 +0000 [thread overview]
Message-ID: <4b185c9f-7fa2-349d-9f72-3c787ac30377@huawei.com> (raw)
In-Reply-To: <1578499287.3260.7.camel@linux.ibm.com>
On 08/01/2020 16:01, James Bottomley wrote:
>>>> cdev->dev = NULL;
>>>> return device_add(&cdev->cdev);
>>>> }
>>>> }
>>>> return -ENODEV;
>>>> }
>>> The design of the code is simply to remove the link to the inserted
>>> device which has been removed.
>>>
>>> I*think* this means the calls to device_del and device_add are
>>> unnecessary and should go. enclosure_remove_links and the put of
>>> the
>>> enclosed device should be sufficient.
>> That would make more sense than trying to "reuse" the device
>> structure
>> here by tearing it down and adding it back.
> OK, let's try that. This should be the patch if someone can try it
> (I've compile tested it, but the enclosure system is under a heap of
> stuff in the garage).
I can test it now.
But it is a bit suspicious that we had the device_del() and device_add()
at all, especially since the code change makes it look a bit more like
pre-43d8eb9cfd0 ("ses: add support for enclosure component hot removal")
John
>
> James
>
> ---
>
> diff --git a/drivers/misc/enclosure.c b/drivers/misc/enclosure.c
> index 6d27ccfe0680..3c2d405bc79b 100644
> --- a/drivers/misc/enclosure.c
> +++ b/drivers/misc/enclosure.c
> @@ -406,10 +406,9 @@ int enclosure_remove_device(struct enclosure_device *edev, struct device *dev)
> cdev = &edev->component[i];
> if (cdev->dev == dev) {
> enclosure_remove_links(cdev);
> - device_del(&cdev->cdev);
> put_device(dev);
> cdev->dev = NULL;
> - return device_add(&cdev->cdev);
> + return 0;
> }
> }
> return -ENODEV;
next prev parent reply other threads:[~2020-01-08 16:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 11:34 Luo Jiaxing
2020-01-08 11:53 ` John Garry
2020-01-08 12:26 ` Greg KH
2020-01-08 14:50 ` John Garry
2020-01-08 15:44 ` Greg KH
2020-01-08 15:51 ` James Bottomley
2020-01-08 15:57 ` Greg KH
2020-01-08 16:01 ` James Bottomley
2020-01-08 16:08 ` John Garry [this message]
2020-01-08 17:10 ` John Garry
2020-01-09 1:04 ` James Bottomley
2020-01-14 15:07 ` Greg KH
2020-01-14 15:20 ` John Garry
2020-01-14 15:28 ` Greg KH
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=4b185c9f-7fa2-349d-9f72-3c787ac30377@huawei.com \
--to=john.garry@huawei.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=luojiaxing@huawei.com \
--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
all inboxes | Powered by JetHome®