On 10/10/05, Philippe Gerum <[EMAIL PROTECTED]> wrote: > Dmitry Adamushko wrote: > >>As you noticed below, the point is that this feature should be active for > >>kernel-based code only; for user-space, we're toast: typical chicken-and-egg > >>problem since we need the registry to cross the space boundaries but the > >>registry requires a name to index the object first. So yes, we need to > >>check for > >>anonymous calls in every service taking a symbolic name in > >>native/syscalls.c, > >>and return -EINVAL when applicable. > > > > > > I thought that "libnative" would be a better place since this way we > > would avoid the user mode -> kernel mode switch. > > > > > >>...Or, we might auto-generate some dummy name in native/syscalls.c we would > >>pass > >>to the registry when this situation arises, so that anonymous creation and > >>use > >>from user-space would still be possible. > > > > > > Yep, in this case a name would be a string == object's address, thus > > it's unique. > > > > Ok, I'd probably vote for the 2-nd approach. > > > > Definitely better since this keeps the semantics consistent across execution > spaces. >
Ok, will be done. > -- > > Philippe. > -- Best regards, Dmitry Adamushko
