lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 28 Sep 2023 17:26:03 +0530
From:   Vinod Koul <vkoul@...nel.org>
To:     Dave Jiang <dave.jiang@...el.com>,
        Fenghua Yu <fenghua.yu@...el.com>
Cc:     dmaengine@...r.kernel.org,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Michael Prinke <michael.prinke@...el.com>
Subject: Re: [PATCH] dmaengine: idxd: Register dsa_bus_type before
 registering idxd sub-drivers


On Sun, 24 Sep 2023 09:22:32 -0700, Fenghua Yu wrote:
> idxd sub-drivers belong to bus dsa_bus_type. Thus, dsa_bus_type must be
> registered in dsa bus init before idxd drivers can be registered.
> 
> But the order is wrong when both idxd and idxd_bus are builtin drivers.
> In this case, idxd driver is compiled and linked before idxd_bus driver.
> Since the initcall order is determined by the link order, idxd sub-drivers
> are registered in idxd initcall before dsa_bus_type is registered
> in idxd_bus initcall. idxd initcall fails:
> 
> [...]

Applied, thanks!

[1/1] dmaengine: idxd: Register dsa_bus_type before registering idxd sub-drivers
      commit: 88928addeec577386e8c83b48b5bc24d28ba97fd

Best regards,
-- 
~Vinod


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ