Re: How to write a proper fork hook code?
On Mon, 2015-03-02 at 11:54 +0100, Samuel Thibault wrote:
> Svante Signell, le Mon 02 Mar 2015 11:53:11 +0100, a écrit :
> > On Mon, 2015-03-02 at 11:15 +0100, Samuel Thibault wrote:
> > > Svante Signell, le Mon 02 Mar 2015 11:03:22 +0100, a écrit :
> > > > On Mon, 2015-03-02 at 10:57 +0100, Svante Signell wrote:
> > > > maybe you could help me find where the design flaw is.
> > >
> > > That would take time, which I don't have.
> >
> > Maybe you should allocate time then
>
> When?
>
> > (or somebody else).
>
> Somebody else which could be you.
To summarise, the problem at hand is:
- how to detect a fork(2) call made in user space (glibc) in "kernel
space" (hurd)
or
- how to obtain (selected parts of) struct protid or struct node from
"kernel space" (hurd) to user space (glibc) to apply a fork hook call.
So far, I've not been able to find a solution. Creating another RPC seem
overkill, as extending the file_record_lock RPC do.
Reply to: