From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udevd sequence number overlap issue!
Date: Thu, 08 Apr 2004 13:49:52 +0000 [thread overview]
Message-ID: <20040408134952.GA30979@vrfy.org> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84037B8F7E@PDSMSX403.ccr.corp.intel.com>
On Thu, Apr 08, 2004 at 09:32:31AM +0800, Yin, Hu wrote:
> First thank you very much for your reply. Maybe I didn't describe this
> issue clearly. I understand what you have said. But I mean what it will
> do when udevd receive two messages with the same sequence number at the
> same time.
The kernel will _never_ send two messages with the same sequence. This
case is really pathological and affects only _your_ testing setup. It
has _nothing_ to do with the real world.
> Is it not necessary for udevd to check whether the incoming
> sequence number has existed:-)
Is this a question? Sure it's neccessary. How will you reorder incoming
sequences without remembering the number of the last handled sequence?
Maybe I don't get your point?
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
prev parent reply other threads:[~2004-04-08 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 1:40 Udevd sequence number overlap issue! Yin, Hu
2004-04-07 10:04 ` Kay Sievers
2004-04-08 1:32 ` Yin, Hu
2004-04-08 13:49 ` Kay Sievers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040408134952.GA30979@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.