I've investigate myself what uevent are sent after each command.
I use "udevadm monitor" to watch the event sent from kernel.
The experiment starts from removing the existing device but
if it's placed at last, the uevents are the same.
What's very curious to me is that the ACTION!="remove" in my
12, 2017 at 6:01 PM, Akira Hayakawa wrote:
>
>> And I want to stop the read request because it makes it difficult to test
>> kernel code.
>> So the second question is: how can I stop the read request?
>
> You can install local udev rule that will disable udev'
I have a device /dev/sdb1 and let's trace the block request by blktrace
$ sudo blktrace -d /dev/sdb1
When I write 4KB using dd
$ sudo dd if=/dev/zero of=/dev/sdb1 oflag=direct bs=4k count=1
The block trace (after blkparsed) is write request as expected
8,17 22 0.03171 5930
