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
| ||
|
Message-ID: <36c12486-57d4-c11d-474f-f26a7de8e59a@linux.intel.com> Date: Tue, 13 Sep 2022 10:12:06 +0800 From: Jiaqing Zhao <jiaqing.zhao@...ux.intel.com> To: Paul Fertser <fercerpav@...il.com> Cc: Samuel Mendoza-Jonas <sam@...dozajonas.com>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org, openbmc@...ts.ozlabs.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] net/ncsi: Add Intel OS2BMC OEM command On 2022-09-09 15:43, Paul Fertser wrote: > Hello, > > On Fri, Sep 09, 2022 at 03:34:53PM +0800, Jiaqing Zhao wrote: >>> Can you please outline some particular use cases for this feature? >>> >> It enables access between host and BMC when BMC shares the network connection >> with host using NCSI, like accessing BMC via HTTP or SSH from host. > > Why having a compile time kernel option here more appropriate than > just running something like "/usr/bin/ncsi-netlink --package 0 > --channel 0 --index 3 --oem-payload 00000157200001" (this example uses > another OEM command) on BMC userspace startup? > Using ncsi-netlink is one way, but the package and channel id is undetermined as it is selected at runtime. Calling the netlink command on a nonexistent package/channel may lead to kernel panic. Why I prefer the kernel option is that it applies the config to all ncsi devices by default when setting up them. This reduces the effort and keeps compatibility. Lots of things in current ncsi kernel driver can be done via commands from userspace, but I think it is not a good idea to have a driver resides on both kernel and userspace.
Powered by blists - more mailing lists