Kay Sievers wrote:
On Thu, Feb 5, 2009 at 08:43, Harald Hoyer <harald@xxxxxxxxxx> wrote:Radek Vykydal <rvykydal@xxxxxxxxxx> encountered a problem with md devices. If the raid is about to be removed a "change" and "remove" event is sent. The "change" event has to be skipped if ATTR{md/array_state} is empty, but somehow the condition does not match, which might point to a bug in the condition code. The following patch is needed: < ATTR{md/array_state}=="|clear|inactive", GOTO="md_end" ---ATTR{md/array_state}=="clear|inactive", GOTO="md_end" ATTR(md/array_state}!="?*", GOTO="md_end"A non-existent attribute makes the rule always fail. Are you sure, the second rule will fix the issue? It should also never match, when the attribute is no longer available. I guess, we need to add a TEST!= key here. Thanks, Kay
The attribute exists, but is empty. -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
