Re: Udevd sequence number overlap issue!

[Kay Sievers <kay.sievers@vrfy.org>]

On Wed, Apr 07, 2004 at 09:40:55AM +0800, Yin, Hu wrote:
> Hi, All,
> 
> I have a question, that is, why udevd didn't handle sequence number
> overlap issue---that means it's possible for udevsend to send two
> messages with the same sequence number to udevd, especially for test
> environment. I know udevd can execute successfully at this case.
> But should we explicitly handle this issue?
> 
> Should we take this issue into consideration? Look forward to your replying.

If you change the sequences, like it happens while you run a test script
with hardcoded numbers, the first event will be delayed by 10 seconds.
You can prevent this by killing udevd before running the test.  It will
expect sequence number 0 as the first event.

You can also bypass the timeout by omitting SEQNUM for udevsend, it will
bypass the timeout handling and move straight to the exec queue.

If you want to test udev - bypass the timeout. If you want to test
udevsend/udevd just kill udevd or wait one timeout for reinitialization
of the exepected_seqnum.
What do you think is missing and why should we have a special test case?
In both cases you get exactly the expected behavior.

thanks,
Kay


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel