All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Saravana Kannan <saravanak@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] driver core: Fix sleeping in invalid context during device link deletion
Date: Fri, 17 Jul 2020 09:34:34 -0700	[thread overview]
Message-ID: <20200717163434.GA119309@roeck-us.net> (raw)
In-Reply-To: <6b37125c-96f5-c59c-f170-934d68c9bed1@samsung.com>

On Fri, Jul 17, 2020 at 12:13:04AM +0200, Marek Szyprowski wrote:
> Hi Saravana,
> 
> On 16.07.2020 23:45, Saravana Kannan wrote:
> > Marek and Guenter reported that commit 287905e68dd2 ("driver core:
> > Expose device link details in sysfs") caused sleeping/scheduling while
> > atomic warnings.
> >
> > BUG: sleeping function called from invalid context at kernel/locking/mutex.c:935
> > in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 12, name: kworker/0:1
> > 2 locks held by kworker/0:1/12:
> >    #0: ee8074a8 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x174/0x7dc
> >    #1: ee921f20 ((work_completion)(&sdp->work)){+.+.}-{0:0}, at: process_one_work+0x174/0x7dc
> > Preemption disabled at:
> > [<c01b10f0>] srcu_invoke_callbacks+0xc0/0x154
> > ----- 8< ----- SNIP
> > [<c064590c>] (device_del) from [<c0645c9c>] (device_unregister+0x24/0x64)
> > [<c0645c9c>] (device_unregister) from [<c01b10fc>] (srcu_invoke_callbacks+0xcc/0x154)
> > [<c01b10fc>] (srcu_invoke_callbacks) from [<c01493c4>] (process_one_work+0x234/0x7dc)
> > [<c01493c4>] (process_one_work) from [<c01499b0>] (worker_thread+0x44/0x51c)
> > [<c01499b0>] (worker_thread) from [<c0150bf4>] (kthread+0x158/0x1a0)
> > [<c0150bf4>] (kthread) from [<c0100114>] (ret_from_fork+0x14/0x20)
> > Exception stack(0xee921fb0 to 0xee921ff8)
> >
> > This was caused by the device link device being released in the context
> > of srcu_invoke_callbacks().  There is no need to wait till the RCU
> > callback to release the device link device.  So release the device
> > earlier and move the call_srcu() into the device release code. That way,
> > the memory will get freed only after the device is released AND the RCU
> > callback is called.
> >
> > Fixes: 287905e68dd2 ("driver core: Expose device link details in sysfs")
> > Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
> > Reported-by: Guenter Roeck <linux@roeck-us.net>
> > Signed-off-by: Saravana Kannan <saravanak@google.com>
> > ---
> >
> > v1->v2:
> > - Better fix
> > - Changed subject
> > - v1 is this patch https://lore.kernel.org/lkml/20200716050846.2047110-1-saravanak@google.com/
> >
> > Marek and Guenter,
> >
> > I reproduced the original issue and tested this fix. Seems to work for
> > me. Can you confirm?
> 
> Confirmed, this one fixes the issue! :)
> 
Same here.

Tested-by: Guenter Roeck <linux@roeck-us.net>

Guenter

> Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
> 
> > Thanks,
> > Saravana
> >
> >   drivers/base/core.c | 45 +++++++++++++++++++++++++++------------------
> >   1 file changed, 27 insertions(+), 18 deletions(-)
> >
> > diff --git a/drivers/base/core.c b/drivers/base/core.c
> > index 5373ddd029f6..ec16b97d45ed 100644
> > --- a/drivers/base/core.c
> > +++ b/drivers/base/core.c
> > @@ -306,10 +306,34 @@ static struct attribute *devlink_attrs[] = {
> >   };
> >   ATTRIBUTE_GROUPS(devlink);
> >   
> > +static void device_link_free(struct device_link *link)
> > +{
> > +	while (refcount_dec_not_one(&link->rpm_active))
> > +		pm_runtime_put(link->supplier);
> > +
> > +	put_device(link->consumer);
> > +	put_device(link->supplier);
> > +	kfree(link);
> > +}
> > +
> > +#ifdef CONFIG_SRCU
> > +static void __device_link_free_srcu(struct rcu_head *rhead)
> > +{
> > +	device_link_free(container_of(rhead, struct device_link, rcu_head));
> > +}
> > +
> >   static void devlink_dev_release(struct device *dev)
> >   {
> > -	kfree(to_devlink(dev));
> > +	struct device_link *link = to_devlink(dev);
> > +
> > +	call_srcu(&device_links_srcu, &link->rcu_head, __device_link_free_srcu);
> >   }
> > +#else
> > +static void devlink_dev_release(struct device *dev)
> > +{
> > +	device_link_free(to_devlink(dev));
> > +}
> > +#endif
> >   
> >   static struct class devlink_class = {
> >   	.name = "devlink",
> > @@ -730,22 +754,7 @@ static void device_link_add_missing_supplier_links(void)
> >   	mutex_unlock(&wfs_lock);
> >   }
> >   
> > -static void device_link_free(struct device_link *link)
> > -{
> > -	while (refcount_dec_not_one(&link->rpm_active))
> > -		pm_runtime_put(link->supplier);
> > -
> > -	put_device(link->consumer);
> > -	put_device(link->supplier);
> > -	device_unregister(&link->link_dev);
> > -}
> > -
> >   #ifdef CONFIG_SRCU
> > -static void __device_link_free_srcu(struct rcu_head *rhead)
> > -{
> > -	device_link_free(container_of(rhead, struct device_link, rcu_head));
> > -}
> > -
> >   static void __device_link_del(struct kref *kref)
> >   {
> >   	struct device_link *link = container_of(kref, struct device_link, kref);
> > @@ -758,7 +767,7 @@ static void __device_link_del(struct kref *kref)
> >   
> >   	list_del_rcu(&link->s_node);
> >   	list_del_rcu(&link->c_node);
> > -	call_srcu(&device_links_srcu, &link->rcu_head, __device_link_free_srcu);
> > +	device_unregister(&link->link_dev);
> >   }
> >   #else /* !CONFIG_SRCU */
> >   static void __device_link_del(struct kref *kref)
> > @@ -773,7 +782,7 @@ static void __device_link_del(struct kref *kref)
> >   
> >   	list_del(&link->s_node);
> >   	list_del(&link->c_node);
> > -	device_link_free(link);
> > +	device_unregister(&link->link_dev);
> >   }
> >   #endif /* !CONFIG_SRCU */
> >   
> 
> Best regards
> -- 
> Marek Szyprowski, PhD
> Samsung R&D Institute Poland
> 

  parent reply	other threads:[~2020-07-17 16:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200716214531eucas1p2c173df09a6e00ef15dfae43ce8f1f9cd@eucas1p2.samsung.com>
2020-07-16 21:45 ` [PATCH v2] driver core: Fix sleeping in invalid context during device link deletion Saravana Kannan
2020-07-16 22:13   ` Marek Szyprowski
2020-07-16 22:16     ` Saravana Kannan
2020-07-17 16:34     ` Guenter Roeck [this message]
2020-07-17 17:31       ` Saravana Kannan

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=20200717163434.GA119309@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=rafael@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.