On Thu, Sep 05, 2019 at 08:25:32PM +0900, Masahiro Yamada wrote: > On Thu, Sep 5, 2019 at 8:16 PM Jessica Yu <jeyu@xxxxxxxxxx> wrote: > > > > +++ Arnd Bergmann [05/09/19 12:52 +0200]: > > >On Thu, Sep 5, 2019 at 12:41 PM Jessica Yu <jeyu@xxxxxxxxxx> wrote: > > >> +++ Matthew Dharm [04/09/19 09:16 -0700]: > > >> >On Wed, Sep 4, 2019 at 5:12 AM Guenter Roeck <linux@xxxxxxxxxxxx> wrote: > > > > > >> >HOWEVER, I have one question: If these patches are included, and > > >> >someone wants to introduce a bit of code which needs to use two > > >> >symbols from different namespaces but with the same name, can that be > > >> >done? That is, if driver A has symbol 'foo' and driver B has symbol > > >> >'foo' (both in their respective namespaces), and driver C wants to use > > >> >A.foo and B.foo, can that be supported? > > >> > > >> As of now, we currently don't support this - modpost will warn if a > > >> symbol is exported more than once (across modules + vmlinux), and the > > >> module loader currently assumes exported symbol names are unique. Do > > >> you have a concrete use case? If there is a strong need for this, I > > >> don't think it'd be too hard to implement. > > > > > >I think what would prevent this from working in general is that having > > >two modules with the same exported symbol in different namespaces > > >won't link if you try to build both modules into the kernel itself. > > > > > > Arnd > > > > Ah yeah, you are right. I only tried building an identically named > > exported symbol in a module and in the kernel, and there I got away > > with a modpost warning. But this breaks when building the module into > > the kernel, so I guess this is out of the question. > > > > Thanks, > > > > Jessica > > > > > The cover letter starts with > "As of Linux 5.3-rc7, there are 31207 [1] exported symbols in the kernel". > > Whether or not we apply this patch set, > we will have to carefully maintain them > so that 31207 symbols are unique, anyway. > (And, we can do this with allmodconfig + modpost) > > So, what is the point of the namespace, > where it does not loosen the scope of uniqueness? It does not "loosen" anything. The problem is, we have 31207 exported symbols and no one has any idea how they are "clustered" :) Ideally we would have separate namespaces where we could "keep" others from accessing symbols that are required to be global, but we do not want anyone else to use them. But we have C, and we need to live with that. This is the "next best thing". This provides a namespace and a marking by the user of that exported symbol that they really do know what they are doing. The USB storage exports are a concrete example of this in this patchset. Those symbols are to only be used by other USB storage drivers, and they are marked that way here. This also gives us the ability to start to actually understand what our different exported symbols are for. Right now the USB core exports a ton of stuff, but who is expected to use what? Right now any USB driver can use any of those functions and no one notices. After this patchset is merged, I will start to "carve up" the USB exports into different "namespaces". One example will be the functions only for use by USB host controller drivers. Then if someone submits a new driver that says "use the USB host controller driver namespace", and that driver is _not_ a USB host controller driver, it's a huge red flag that something really isn't correct here. Some other USB functions will probably get marked "USB core only" or some such thing, and then to use them you have to say you are importing from the "usb core only" which again, is a huge flag that you are doing something wrong. So on it's own, this patchset doesn't do much. But it gives us the building blocks on which to start to make sense of those 31000+ different exported symbols. As an aside, this is something that I know I and others have been wanting to see happen for 10+ years now, and I'm very happy to see it show up in a workable form as we have known this is a issue for a very long time. Hope this helps explain things better, greg k-h
