Samuel Thibault, le Wed 08 Jul 2015 18:22:56 +0200, a écrit :
> Justus Winter, le Wed 08 Jul 2015 16:22:28 +0200, a écrit :
> > Alternatively, you could re-purpose the existing RPC `vm_wire',
> > changing the type of its first argument from `host_priv_t' to `host_t'
> > (this is backwards compatibl
Richard Braun, le Wed 08 Jul 2015 20:49:14 +0200, a écrit :
> On Tue, Jul 07, 2015 at 05:59:58PM +0200, Samuel Thibault wrote:
> > A way to reproduce this workload is using pbuilder instead of building
> > in a system with dependencies already installed.
>
> FYI, pbuilder on sid fails because of
Funny to see a *.patch (and later on a *.diff) file being classified as
a security threat ...
On Wed, 2015-07-08 at 15:55 +0200, nore...@kth.se wrote:
> ###
>
> F-Secure Anti-Virus for Microsoft Exchange has processed the message
> sent by 'bug-hurd-bounces
On Tue, Jul 07, 2015 at 05:59:58PM +0200, Samuel Thibault wrote:
> A way to reproduce this workload is using pbuilder instead of building
> in a system with dependencies already installed.
FYI, pbuilder on sid fails because of
1/ procfs: Too many arguments
Try `procfs --help' or `procfs --usage'
Justus Winter, le Wed 08 Jul 2015 16:22:28 +0200, a écrit :
> Alternatively, you could re-purpose the existing RPC `vm_wire',
> changing the type of its first argument from `host_priv_t' to `host_t'
> (this is backwards compatible as the privileged host control port is
> also a host port), and chan
On Wed, Jul 08, 2015 at 04:32:36PM +0200, Samuel Thibault wrote:
> > Isn't a per-process limit rather pointless? I thought Linux limit is
> > per-user.
>
> On Linux it's per process too, changing ulimit -l in a process won't
> affect another process.
>
> The issue with mlocked memory is mostly a
Hello,
Justus Winter, le Wed 08 Jul 2015 16:22:28 +0200, a écrit :
> You talked about that in your FOSDEM talk, right?
Yes, although since I hadn't had any look at it at the time, I hadn't
realized that passing host==NULL wasn't an option (since we need a port
to make the RPC on anyway).
> Ever
Hi :)
Quoting Samuel Thibault (2015-07-08 15:55:33)
> I have implemented a start of support for calling mlock() in a non-root
> process, which I have attached.
Sweet. You talked about that in your FOSDEM talk, right? Ever since
I thought that managing this in userspace is the better solution, t
Hello,
I have implemented a start of support for calling mlock() in a non-root
process, which I have attached. I had to introduce a newer RPC since
the existing vm_wire RPC is done on the privileged host port. It for now
allows 64KiB mlocked memory per task (the default Linux value).
Could someb
Quoting Ludovic Courtès (2015-07-07 22:29:05)
> Justus Winter <4win...@informatik.uni-hamburg.de> skribis:
>
> > Sounds awesome. One thing to be aware of (iirc) is that the
> > mount/umount code depends on the fstab parser. I'm not sure whether
> > it is needed for the mount/umount(2) interface,
10 matches
Mail list logo
