Re: connector.c

[Evgeniy Polyakov <johnpol@2ka.mipt.ru>]

[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]

On Fri, 2005-04-01 at 00:02 -0800, Andrew Morton wrote:
> 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?

Nothing.
If reply message will be recived, it will be delivered to the requested 
connector user, if reply will not be received just nothing happens.

Not connector, but it's users who may expect reply to theirs messages.

-- 
        Evgeniy Polyakov

Crash is better than data corruption -- Arthur Grabowski

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]