[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <875eecfb-618a-4989-3b9f-f8272b8d3746@gmail.com>
Date: Fri, 11 Oct 2019 21:26:05 +0200
From: Heiner Kallweit <hkallweit1@...il.com>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>
Subject: Re: Module loading problem since 5.3
On 10.10.2019 19:15, Luis Chamberlain wrote:
>
>
> On Thu, Oct 10, 2019, 6:50 PM Heiner Kallweit <hkallweit1@...il.com <mailto:hkallweit1@...il.com>> wrote:
>
> MODULE_SOFTDEP("pre: realtek")
>
> Are you aware of any current issues with module loading
> that could cause this problem?
>
>
> Nope. But then again I was not aware of MODULE_SOFTDEP(). I'd encourage an extension to lib/kmod.c or something similar which stress tests this. One way that comes to mind to test this is to allow a new tests case which loads two drives which co depend on each other using this macro. That'll surely blow things up fast. That is, the current kmod tests uses request_module() or get_fs_type(), you'd want a new test case with this added using then two new dummy test drivers with the macro dependency.
>
> If you want to resolve this using a more tested path, you could have request_module() be used as that is currently tested. Perhaps a test patch for that can rule out if it's the macro magic which is the issue.
>
> Luis
>
Maybe issue is related to a bug in introduction of symbol namespaces, see here:
https://lkml.org/lkml/2019/10/11/659
Heiner
Powered by blists - more mailing lists