Busybox mdev will not chmod the device node when the matched rule contains a '!'. Matching this behaviour makes it possible for a rule to preserve the mode set by the kernel for devices that are created automatically by devtmpfs.
While reviewing it, I found that the same path where the chmod() occurs also has the mknod() in it, so it needs to be guarded with elem->movetype != MOVEINFO_NOCREATE anyway - so your patch is more than a behaviour adjustment, it's a bugfix 🙂 Applied, thanks! -- Laurent
