[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f6f97630-5a45-3e75-bb34-b0bdb66c1bee@fujitsu.com>
Date: Tue, 21 Mar 2023 03:19:27 +0000
From: "lizhijian@...itsu.com" <lizhijian@...itsu.com>
To: Dan Williams <dan.j.williams@...el.com>,
"vishal.l.verma@...el.com" <vishal.l.verma@...el.com>,
"dave.jiang@...el.com" <dave.jiang@...el.com>,
"ira.weiny@...el.com" <ira.weiny@...el.com>,
"nvdimm@...ts.linux.dev" <nvdimm@...ts.linux.dev>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] nvdimm: nvdimm_bus_register: Avoid adding device to the
unregistered bus
On 21/03/2023 10:38, Dan Williams wrote:
> lizhijian@...itsu.com wrote:
> [..]
>>> Now I do think it would be a good idea to fail device_add() if the bus
>>> is not registered,
>>
>> BTW, below line 369: device_add() didn't fail in practical.
>>
>
> I think that's ok because the device gets added, but never probed due to
> this part of that commit I referenced:
Very thanks for your explanation.
>
> @@ -503,20 +517,21 @@ int bus_add_device(struct device *dev)
> */
> void bus_probe_device(struct device *dev)
> {
> - struct bus_type *bus = dev->bus;
> + struct subsys_private *sp = bus_to_subsys(dev->bus);
> struct subsys_interface *sif;
>
> - if (!bus)
> + if (!sp)
> return;
>
>
> ...so it does what you want which is disable the libnvdimm subsystem
> from binding to any devices without crashing.
Yes, it's fine enough to me.
Powered by blists - more mailing lists