Summary: | sys-kernel/genkernel: race: mdadm should wait for drive scan to settle | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ed Santiago <gentoo> |
Component: | Current packages | Assignee: | Gentoo Genkernel Maintainers <genkernel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ed Santiago
2020-04-17 00:46:29 UTC
Not a bug. Options like scandelay, rootdelay... are existing exactly for this kind of problem. I'm afraid I must respectfully disagree. Adding delays is, by definition, racy. The correct way to avoid a race condition is not by adding delays but by adding hooks such that a flag is set indicating completion of processing. This is in no way controversial. I understand that genkernel has an aversion to udev, which is why I didn't suggest `udevadm settle` in my initial comment: I was hoping you would be able to use other processing hooks for determining that device processing is complete. I still hope you'll consider doing so. Genkernel switched to udev due to bug 706434. Now that bundled mdadm is also udev-aware (https://gitweb.gentoo.org/proj/genkernel.git/commit/?id=f6f9384b423e9bb9b8cee294f4ddbeee7c518463), the reported problem should be resolved. Please re-open/file a new bug if you are still experiencing the problem for >=genkernel-4.1.0_beta1. |