From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: [PATCH 0/3] Autoloading for RDMA netlink modules Date: Tue, 25 Jul 2017 09:40:29 -0600 Message-ID: <20170725154029.GB6715@obsidianresearch.com> References: <1500935204-6505-1-git-send-email-jgunthorpe@obsidianresearch.com> <20170725063236.GQ3259@mtr-leonro.local> <20170725143420.GA434@obsidianresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20170725143420.GA434-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Leon Romanovsky Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Leon Romanovsky , Doug Ledford List-Id: linux-rdma@vger.kernel.org On Tue, Jul 25, 2017 at 08:34:20AM -0600, Jason Gunthorpe wrote: > > Second, from brief review, it is unclear to me, how do you protect > > autoload caused by regular user who sends netlink message to ib_core. > > You don't, that isn't how kernel auto loading works. Any user can > attempt to create any kind of socket and the core kernel code will > load the correct module to support that socket. That is the standard > way kernel autoloading works, particularly for net families. I should clarify some more that this is needed to avoid problematic dependencies during boot up. For instance, long term, I want to use rdma netlink from within udev to fill in some more ID_ fields in the database, I cannot resolve the race conditions with udev running and modules loading unless the kernel can fully autoload the netlink subystem, just like other netlink subsystems. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html