This is an unconditional rule which will just second-guess kernel defaults everywhere, and it will not go to upstream either. Wouldn't it make more sense to fix whichever kernel driver is responsible for this device (or possibly QEMU) to pick a scheduler which is appropriate for these virtual drives, instead of picking the wrong one and then requiring userspace to clean up behind it? This udev rule is ok for an SRU, but not for a long-term solution.
Also, the "*Google*" match is too weak. What if I attach an Android device in UMS mode, these should certainly not deviate from the kernel defaults.
Can you please give some rationale why the scheduler needs to be changed? What is "GCE"?
This is an unconditional rule which will just second-guess kernel defaults everywhere, and it will not go to upstream either. Wouldn't it make more sense to fix whichever kernel driver is responsible for this device (or possibly QEMU) to pick a scheduler which is appropriate for these virtual drives, instead of picking the wrong one and then requiring userspace to clean up behind it? This udev rule is ok for an SRU, but not for a long-term solution.
Also, the "*Google*" match is too weak. What if I attach an Android device in UMS mode, these should certainly not deviate from the kernel defaults.
Can you please give some rationale why the scheduler needs to be changed? What is "GCE"?
Thanks!