Previously the macro argument err was expanded and thus potentially
evaluated multiple times. This is fine for simple values or pure
functions, but not for say iohelp_create_iouser. Fix this by
evaluating the macro argument only once.
---
libiohelp/iouser-create.c |3 ++-
1 file changed, 2 ins
On Thu, Jul 18, 2013 at 12:03:58PM +0200, Neal H. Walfield wrote:
> If you introduce a new RPC, it should be done right. In particular,
> it should not introduce security problems. If you just write a
> translator that doesn't require a new RPC, emulating Linux is fine.
I'm starting to agree tha
At Thu, 18 Jul 2013 11:39:14 +0200,
Justus Winter wrote:
> He has shown me how this could be implemented, but doing so requires
> attaching credentials to all fsys_* by means of
> e.g. libdiskfs/fsmutations.h and fixing all functions that are
> affected by this. I think it's doable, but my time mig
Justus Winter, le Thu 18 Jul 2013 11:39:14 +0200, a écrit :
> Quoting Samuel Thibault (2013-07-15 10:26:18)
> > Neal H. Walfield, le Fri 12 Jul 2013 15:13:30 +0200, a écrit :
> > > How do you do permission checking?
> > >
> > > Making a directory executable but not readable is a useful way to
> >
Quoting Samuel Thibault (2013-07-15 10:26:18)
> Neal H. Walfield, le Fri 12 Jul 2013 15:13:30 +0200, a écrit :
> > How do you do permission checking?
> >
> > Making a directory executable but not readable is a useful way to
> > grant permission by knowledge of a shared secret.
>
> Right.
>
> Tha
On Thu, Jul 18, 2013 at 12:22:07AM +0800, Yue Lu wrote:
> On Thu, Jul 18, 2013 at 12:13 AM, Richard Braun wrote:
> > On Thu, Jul 18, 2013 at 12:07:20AM +0800, Yue Lu wrote:
> >> when I used thread_info() to check the suspend count, they are zero.
> >> But I met a strange thing.
> >> this is my cod
