From: Roland Dreier <roland@topspin.com>
To: Greg KH <greg@kroah.com>
Cc: Klaus Dittrich <kladit@t-online.de>,
linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kobject hotplug: don't let SEQNUM overwrite other vars
Date: Fri, 29 Oct 2004 11:44:29 -0700 [thread overview]
Message-ID: <52hdodxt2q.fsf@topspin.com> (raw)
In-Reply-To: <20041029043807.GA12309@kroah.com> (Greg KH's message of "Thu, 28 Oct 2004 23:38:07 -0500")
Greg> No, this puts back the problem where if the hotplug()
Greg> subsystem call fails, we have already incremented the seqnum
Greg> without emitting a call with that number.
Greg> Now I know userspace needs to handle this properly anyway,
Greg> but we might as well get the kernel right, and not do stuff
Greg> to make userspace unhappy if we can obviously help it.
Got it... I had remembered you saying gaps in the sequence numbers
were OK in the past.
- R.
prev parent reply other threads:[~2004-10-30 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 11:59 usb hotplug $DEVICE empty Klaus Dittrich
2004-10-29 4:24 ` [PATCH] kobject hotplug: don't let SEQNUM overwrite other vars (was Re: usb hotplug $DEVICE empty) Roland Dreier
2004-10-29 4:38 ` Greg KH
2004-10-29 18:44 ` Roland Dreier [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=52hdodxt2q.fsf@topspin.com \
--to=roland@topspin.com \
--cc=greg@kroah.com \
--cc=kladit@t-online.de \
--cc=linux-kernel@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.