[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023053137-leggings-grumbly-a33a@gregkh>
Date: Wed, 31 May 2023 20:20:13 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Maxime Ripard <maxime@...no.tech>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Brendan Higgins <brendan.higgins@...ux.dev>,
David Gow <davidgow@...gle.com>,
linux-kselftest@...r.kernel.org, kunit-dev@...glegroups.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] drivers: base: Add tests showing devm handling
inconsistencies
On Mon, Apr 17, 2023 at 06:12:26PM +0200, Maxime Ripard wrote:
> Hi,
>
> On Wed, Mar 29, 2023 at 08:38:30PM +0100, Maxime Ripard wrote:
> > Hi,
> >
> > This follows the discussion here:
> > https://lore.kernel.org/linux-kselftest/20230324123157.bbwvfq4gsxnlnfwb@houat/
> >
> > This shows a couple of inconsistencies with regard to how device-managed
> > resources are cleaned up. Basically, devm resources will only be cleaned up
> > if the device is attached to a bus and bound to a driver. Failing any of
> > these cases, a call to device_unregister will not end up in the devm
> > resources being released.
> >
> > We had to work around it in DRM to provide helpers to create a device for
> > kunit tests, but the current discussion around creating similar, generic,
> > helpers for kunit resumed interest in fixing this.
> >
> > This can be tested using the command:
> > ./tools/testing/kunit/kunit.py run --kunitconfig=drivers/base/test/
> >
> > Let me know what you think,
> > Maxime
> >
> > Signed-off-by: Maxime Ripard <maxime@...no.tech>
>
> Is there any news on this?
Can you resend, last I saw the kernel test robot had a problem, which
causes any patch series like that to be ignored by me.
thanks,
greg k-h
Powered by blists - more mailing lists