lkml.org 
[lkml]   [2008]   [Apr]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] alternative to sys_indirect, part 1
> You didn't read what I wrote.

The feeling is mutual

> For those the implementer must ensure that during the development no
> value is used which can conflict with any current and future assigned
> value and not with any other development.

Kernel socket type values are assigned by the kernel team so that
isn't a problem.

> > Every other property of a socket via accept() is inherited from the
> > parent. Making one property different would be bizarre and ugly.
>
> Implementing this would visibly change existing code and it would
> actively violate POSIX. Not a good idea.

POSIX has no interface for this new behaviour you propose so that is
complete crap. The moment you use one of these features you stepped
outside of the POSIX spec - and you know that. If there was an existing
standard we wouldn't have a problem.

Alan


\
 
 \ /
  Last update: 2008-04-24 17:37    [W:0.120 / U:0.824 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site