Behind primary and secondary we understand the type of the nodes which might define their ordering. However, if primary node gone, we can't maintain the ordering by definition of the linked list. Thus, by ordering secondary node becomes first in the list. But in this case the meaning of it is still secondary (or auxiliary). The type of the node is maintained by the secondary pointer in it: secondary pointer Meaning NULL or valid primary node ERR_PTR(-ENODEV) secondary node So, if by some reason we do the following sequence of calls set_primary_fwnode(dev, NULL); set_primary_fwnode(dev, primary); we should preserve secondary node. This concept is supported by the description of set_primary_fwnode() along with implementation of set_secondary_fwnode(). Hence, fix the commit c15e1bdda436 to follow this as well. Fixes: c15e1bdda436 ("device property: Fix the secondary firmware node handling in set_primary_fwnode()") Cc: Ferry Toth <fntoth@gmail.com> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> --- drivers/base/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/base/core.c b/drivers/base/core.c index c852f16c111b..41feab679fa1 100644 --- a/drivers/base/core.c +++ b/drivers/base/core.c @@ -4278,7 +4278,7 @@ void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode) } else { if (fwnode_is_primary(fn)) { dev->fwnode = fn->secondary; - fn->secondary = NULL; + fn->secondary = ERR_PTR(-ENODEV); } else { dev->fwnode = NULL; } -- 2.28.0
It appears that firmware nodes can be shared between devices. In such case when a (child) device is about to be deleted, its firmware node may be shared and ACPI_COMPANION_SET(..., NULL) call for it breaks the secondary link of the shared primary firmware node. In order to prevent that, check, if the device has a parent and parent's firmware node is shared with its child, and avoid crashing the link. Fixes: c15e1bdda436 ("device property: Fix the secondary firmware node handling in set_primary_fwnode()") Reported-by: Ferry Toth <fntoth@gmail.com> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> --- drivers/base/core.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/base/core.c b/drivers/base/core.c index 41feab679fa1..78114ddac755 100644 --- a/drivers/base/core.c +++ b/drivers/base/core.c @@ -4264,6 +4264,7 @@ static inline bool fwnode_is_primary(struct fwnode_handle *fwnode) */ void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode) { + struct device *parent = dev->parent; struct fwnode_handle *fn = dev->fwnode; if (fwnode) { @@ -4278,7 +4279,8 @@ void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode) } else { if (fwnode_is_primary(fn)) { dev->fwnode = fn->secondary; - fn->secondary = ERR_PTR(-ENODEV); + if (!(parent && fn == parent->fwnode)) + fn->secondary = ERR_PTR(-ENODEV); } else { dev->fwnode = NULL; } -- 2.28.0
On Thu, Oct 22, 2020 at 09:40:59PM +0300, Andy Shevchenko wrote: > Behind primary and secondary we understand the type of the nodes > which might define their ordering. However, if primary node gone, > we can't maintain the ordering by definition of the linked list. > Thus, by ordering secondary node becomes first in the list. > But in this case the meaning of it is still secondary (or auxiliary). > The type of the node is maintained by the secondary pointer in it: > > secondary pointer Meaning > NULL or valid primary node > ERR_PTR(-ENODEV) secondary node > > So, if by some reason we do the following sequence of calls > > set_primary_fwnode(dev, NULL); > set_primary_fwnode(dev, primary); > > we should preserve secondary node. > > This concept is supported by the description of set_primary_fwnode() > along with implementation of set_secondary_fwnode(). Hence, fix > the commit c15e1bdda436 to follow this as well. > > Fixes: c15e1bdda436 ("device property: Fix the secondary firmware node handling in set_primary_fwnode()") > Cc: Ferry Toth <fntoth@gmail.com> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> FWIW: Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com> > --- > drivers/base/core.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/base/core.c b/drivers/base/core.c > index c852f16c111b..41feab679fa1 100644 > --- a/drivers/base/core.c > +++ b/drivers/base/core.c > @@ -4278,7 +4278,7 @@ void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode) > } else { > if (fwnode_is_primary(fn)) { > dev->fwnode = fn->secondary; > - fn->secondary = NULL; > + fn->secondary = ERR_PTR(-ENODEV); > } else { > dev->fwnode = NULL; > } > -- > 2.28.0 -- heikki
On Thu, Oct 22, 2020 at 09:41:00PM +0300, Andy Shevchenko wrote: > It appears that firmware nodes can be shared between devices. In such case > when a (child) device is about to be deleted, its firmware node may be shared > and ACPI_COMPANION_SET(..., NULL) call for it breaks the secondary link > of the shared primary firmware node. > > In order to prevent that, check, if the device has a parent and parent's > firmware node is shared with its child, and avoid crashing the link. > > Fixes: c15e1bdda436 ("device property: Fix the secondary firmware node handling in set_primary_fwnode()") > Reported-by: Ferry Toth <fntoth@gmail.com> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> FWIW: Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com> > --- > drivers/base/core.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/drivers/base/core.c b/drivers/base/core.c > index 41feab679fa1..78114ddac755 100644 > --- a/drivers/base/core.c > +++ b/drivers/base/core.c > @@ -4264,6 +4264,7 @@ static inline bool fwnode_is_primary(struct fwnode_handle *fwnode) > */ > void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode) > { > + struct device *parent = dev->parent; > struct fwnode_handle *fn = dev->fwnode; > > if (fwnode) { > @@ -4278,7 +4279,8 @@ void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode) > } else { > if (fwnode_is_primary(fn)) { > dev->fwnode = fn->secondary; > - fn->secondary = ERR_PTR(-ENODEV); > + if (!(parent && fn == parent->fwnode)) > + fn->secondary = ERR_PTR(-ENODEV); > } else { > dev->fwnode = NULL; > } > -- > 2.28.0 -- heikki
Hi Op 23-10-2020 om 14:35 schreef Heikki Krogerus: > On Thu, Oct 22, 2020 at 09:41:00PM +0300, Andy Shevchenko wrote: >> It appears that firmware nodes can be shared between devices. In such case >> when a (child) device is about to be deleted, its firmware node may be shared >> and ACPI_COMPANION_SET(..., NULL) call for it breaks the secondary link >> of the shared primary firmware node. >> >> In order to prevent that, check, if the device has a parent and parent's >> firmware node is shared with its child, and avoid crashing the link. >> >> Fixes: c15e1bdda436 ("device property: Fix the secondary firmware node handling in set_primary_fwnode()") >> Reported-by: Ferry Toth <fntoth@gmail.com> >> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> > FWIW: > > Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com> Tested-by: Ferry Toth <fntoth@gmail.com> >> --- >> drivers/base/core.c | 4 +++- >> 1 file changed, 3 insertions(+), 1 deletion(-) >> >> diff --git a/drivers/base/core.c b/drivers/base/core.c >> index 41feab679fa1..78114ddac755 100644 >> --- a/drivers/base/core.c >> +++ b/drivers/base/core.c >> @@ -4264,6 +4264,7 @@ static inline bool fwnode_is_primary(struct fwnode_handle *fwnode) >> */ >> void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode) >> { >> + struct device *parent = dev->parent; >> struct fwnode_handle *fn = dev->fwnode; >> >> if (fwnode) { >> @@ -4278,7 +4279,8 @@ void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode) >> } else { >> if (fwnode_is_primary(fn)) { >> dev->fwnode = fn->secondary; >> - fn->secondary = ERR_PTR(-ENODEV); >> + if (!(parent && fn == parent->fwnode)) >> + fn->secondary = ERR_PTR(-ENODEV); >> } else { >> dev->fwnode = NULL; >> } >> -- >> 2.28.0
Hi
Op 23-10-2020 om 14:34 schreef Heikki Krogerus:
> On Thu, Oct 22, 2020 at 09:40:59PM +0300, Andy Shevchenko wrote:
>> Behind primary and secondary we understand the type of the nodes
>> which might define their ordering. However, if primary node gone,
>> we can't maintain the ordering by definition of the linked list.
>> Thus, by ordering secondary node becomes first in the list.
>> But in this case the meaning of it is still secondary (or auxiliary).
>> The type of the node is maintained by the secondary pointer in it:
>>
>> secondary pointer Meaning
>> NULL or valid primary node
>> ERR_PTR(-ENODEV) secondary node
>>
>> So, if by some reason we do the following sequence of calls
>>
>> set_primary_fwnode(dev, NULL);
>> set_primary_fwnode(dev, primary);
>>
>> we should preserve secondary node.
>>
>> This concept is supported by the description of set_primary_fwnode()
>> along with implementation of set_secondary_fwnode(). Hence, fix
>> the commit c15e1bdda436 to follow this as well.
>>
>> Fixes: c15e1bdda436 ("device property: Fix the secondary firmware node handling in set_primary_fwnode()")
>> Cc: Ferry Toth<fntoth@gmail.com>
>> Signed-off-by: Andy Shevchenko<andriy.shevchenko@linux.intel.com>
> FWIW:
>
> Reviewed-by: Heikki Krogerus<heikki.krogerus@linux.intel.com>
> Tested-by: Ferry Toth<fntoth@gmail.com>
>> ---
>> drivers/base/core.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/base/core.c b/drivers/base/core.c
>> index c852f16c111b..41feab679fa1 100644
>> --- a/drivers/base/core.c
>> +++ b/drivers/base/core.c
>> @@ -4278,7 +4278,7 @@ void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode)
>> } else {
>> if (fwnode_is_primary(fn)) {
>> dev->fwnode = fn->secondary;
>> - fn->secondary = NULL;
>> + fn->secondary = ERR_PTR(-ENODEV);
>> } else {
>> dev->fwnode = NULL;
>> }
>> --
>> 2.28.0
Hi Op 23-10-2020 om 14:35 schreef Heikki Krogerus: > On Thu, Oct 22, 2020 at 09:41:00PM +0300, Andy Shevchenko wrote: >> It appears that firmware nodes can be shared between devices. In such >> case >> when a (child) device is about to be deleted, its firmware node may >> be shared >> and ACPI_COMPANION_SET(..., NULL) call for it breaks the secondary link >> of the shared primary firmware node. >> >> In order to prevent that, check, if the device has a parent and parent's >> firmware node is shared with its child, and avoid crashing the link. >> >> Fixes: c15e1bdda436 ("device property: Fix the secondary firmware >> node handling in set_primary_fwnode()") >> Reported-by: Ferry Toth <fntoth@gmail.com> >> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> > FWIW: > > Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com> Tested-by: Ferry Toth <fntoth@gmail.com> >> --- >> drivers/base/core.c | 4 +++- >> 1 file changed, 3 insertions(+), 1 deletion(-) >> >> diff --git a/drivers/base/core.c b/drivers/base/core.c >> index 41feab679fa1..78114ddac755 100644 >> --- a/drivers/base/core.c >> +++ b/drivers/base/core.c >> @@ -4264,6 +4264,7 @@ static inline bool fwnode_is_primary(struct >> fwnode_handle *fwnode) >> */ >> void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode) >> { >> + struct device *parent = dev->parent; >> struct fwnode_handle *fn = dev->fwnode; >> if (fwnode) { >> @@ -4278,7 +4279,8 @@ void set_primary_fwnode(struct device *dev, >> struct fwnode_handle *fwnode) >> } else { >> if (fwnode_is_primary(fn)) { >> dev->fwnode = fn->secondary; >> - fn->secondary = ERR_PTR(-ENODEV); >> + if (!(parent && fn == parent->fwnode)) >> + fn->secondary = ERR_PTR(-ENODEV); >> } else { >> dev->fwnode = NULL; >> } >> -- 2.28.0
On Fri, Oct 23, 2020 at 04:03:20PM +0200, Ferry Toth wrote: > Hi > > Op 23-10-2020 om 14:34 schreef Heikki Krogerus: > > On Thu, Oct 22, 2020 at 09:40:59PM +0300, Andy Shevchenko wrote: > > > Behind primary and secondary we understand the type of the nodes > > > which might define their ordering. However, if primary node gone, > > > we can't maintain the ordering by definition of the linked list. > > > Thus, by ordering secondary node becomes first in the list. > > > But in this case the meaning of it is still secondary (or auxiliary). > > > The type of the node is maintained by the secondary pointer in it: > > > > > > secondary pointer Meaning > > > NULL or valid primary node > > > ERR_PTR(-ENODEV) secondary node > > > > > > So, if by some reason we do the following sequence of calls > > > > > > set_primary_fwnode(dev, NULL); > > > set_primary_fwnode(dev, primary); > > > > > > we should preserve secondary node. > > > > > > This concept is supported by the description of set_primary_fwnode() > > > along with implementation of set_secondary_fwnode(). Hence, fix > > > the commit c15e1bdda436 to follow this as well. > > > > > > Fixes: c15e1bdda436 ("device property: Fix the secondary firmware node handling in set_primary_fwnode()") > > > Cc: Ferry Toth <fntoth@gmail.com> > > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> > > FWIW: > > > > Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com> > > Tested-by: Ferry Toth <fntoth@gmail.com> The quoting above is broken, I dare to put it below without any quoting. Tested-by: Ferry Toth <fntoth@gmail.com> > > > --- > > > drivers/base/core.c | 2 +- > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > > > diff --git a/drivers/base/core.c b/drivers/base/core.c > > > index c852f16c111b..41feab679fa1 100644 > > > --- a/drivers/base/core.c > > > +++ b/drivers/base/core.c > > > @@ -4278,7 +4278,7 @@ void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode) > > > } else { > > > if (fwnode_is_primary(fn)) { > > > dev->fwnode = fn->secondary; > > > - fn->secondary = NULL; > > > + fn->secondary = ERR_PTR(-ENODEV); > > > } else { > > > dev->fwnode = NULL; > > > } > > > -- > > > 2.28.0 -- With Best Regards, Andy Shevchenko
On Thu, Oct 22, 2020 at 8:41 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> Behind primary and secondary we understand the type of the nodes
> which might define their ordering. However, if primary node gone,
> we can't maintain the ordering by definition of the linked list.
> Thus, by ordering secondary node becomes first in the list.
> But in this case the meaning of it is still secondary (or auxiliary).
> The type of the node is maintained by the secondary pointer in it:
>
> secondary pointer Meaning
> NULL or valid primary node
> ERR_PTR(-ENODEV) secondary node
>
> So, if by some reason we do the following sequence of calls
>
> set_primary_fwnode(dev, NULL);
> set_primary_fwnode(dev, primary);
>
> we should preserve secondary node.
>
> This concept is supported by the description of set_primary_fwnode()
> along with implementation of set_secondary_fwnode(). Hence, fix
> the commit c15e1bdda436 to follow this as well.
>
> Fixes: c15e1bdda436 ("device property: Fix the secondary firmware node handling in set_primary_fwnode()")
> Cc: Ferry Toth <fntoth@gmail.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/base/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/base/core.c b/drivers/base/core.c
> index c852f16c111b..41feab679fa1 100644
> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -4278,7 +4278,7 @@ void set_primary_fwnode(struct device *dev, struct fwnode_handle *fwnode)
> } else {
> if (fwnode_is_primary(fn)) {
> dev->fwnode = fn->secondary;
> - fn->secondary = NULL;
> + fn->secondary = ERR_PTR(-ENODEV);
> } else {
> dev->fwnode = NULL;
> }
> --
Applied as 5.10-rc material along with the [2/2], thanks!