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: <c8d6d56f-bd8f-4d2c-a95a-4ed11bf952b8@lunn.ch> Date: Sun, 29 Oct 2023 20:39:44 +0100 From: Andrew Lunn <andrew@...n.ch> To: Boqun Feng <boqun.feng@...il.com> Cc: FUJITA Tomonori <fujita.tomonori@...il.com>, benno.lossin@...ton.me, netdev@...r.kernel.org, rust-for-linux@...r.kernel.org, tmgross@...ch.edu, miguel.ojeda.sandonis@...il.com, wedsonaf@...il.com Subject: Re: [PATCH net-next v7 1/5] rust: core abstractions for network PHY drivers > Of course, it's not maintainable in longer term since it relies on > hard-coding the bit offset of these bit fields. But I think it's best we > can do from Linux kernel side. It's up to Andrew and Miguel whether this > temporary solution is OK. What is the likely time scale for getting a new version of bindgen with the necessary bit field support? We have probably missed the merge window for v6.7. So there is around 9 weeks to the next merge window. If a working bindgen is likely to be available by then, we should not bother with a workaround, just wait. If you think bindgen is going to take longer than that, then we should consider workarounds. But we have no rush, its still 9 weeks before we need working code. Zooming out a bit. Is there any other in mainline Rust code, or about to be submitted for this merge window code, using bit fields? I assume that is equally broken? Andrew
Powered by blists - more mailing lists