mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: johnpol@2ka.mipt.ru
Cc: linux-kernel@vger.kernel.org
Subject: Re: connector.c
Date: Fri, 1 Apr 2005 00:02:15 -0800	[thread overview]
Message-ID: <20050401000215.6d85c477.akpm@osdl.org> (raw)
In-Reply-To: <1112342595.9334.120.camel@uganda>

Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
>
> On Thu, 2005-03-31 at 23:42 -0800, Andrew Morton wrote:
>  > Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
>  > >
>  > > > What happens if we expect a reply to our message but userspace never sends
>  > > > one?  Does the kernel leak memory?  Do other processes hang?
>  > > 
>  > > It is only advice, one may easily skip seq/ack initialization.
>  > > I could remove it totally from the header, but decided to 
>  > > place it to force people to use more reliable protocols over netlink
>  > > by introducing such overhead.
>  > 
>  > hm.  I don't know what that means.
> 
>  Messages that are passed between agents must have only id,
>  but I decided to force people to use provided seq/ack fields
>  to store there some information about message order.
>  Neither kernel nor userspace requires that fields to be 
>  somehow initialized.

Back to my original question.  If the kernel expects a reply from userspace
to a particular message, and that reply never comes, what happens?

  reply	other threads:[~2005-04-01  8:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01  1:30 connector.c Andrew Morton
2005-04-01  2:41 ` connector.c Tommy Reynolds
2005-04-01 14:29   ` connector.c Matthias Urlichs
2005-04-01 17:36     ` connector.c Paul Jackson
2005-04-01  7:07 ` connector.c Evgeniy Polyakov
2005-04-01  7:42   ` connector.c Andrew Morton
2005-04-01  8:03     ` connector.c Evgeniy Polyakov
2005-04-01  8:02       ` Andrew Morton [this message]
2005-04-01  8:28         ` connector.c Evgeniy Polyakov

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=20050401000215.6d85c477.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=johnpol@2ka.mipt.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®