Hi,
I've read about the possible bugs.
About the combination between mmap and mandatory locks:
of course the mapping of memory is causing troubles when a mandatory lock
is set. The mapped region should or forward the lock to the new memory
location (where remapped) or the mmap should be denied, un
On Thu, 03.01.13 23:21, Stef Bon (stef...@gmail.com) wrote:
> Yes, thanks a lot. I've read it, understood, maybe this whole locking thing
> should be replaced with a better approach. First you mention in the first
> blog entry:
>
> "Mandatory locking is available too. It's based on the POSIX lock
2013/1/3 Kay Sievers
>
> FWIW, adding poll() support would look like something like this:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=66d7dd518ae413a383ab2c6c263cc30617329842
>
> Kay
>
Thanks a lot. I will try to write a patch with it, although the way linux
h
Yes, thanks a lot. I've read it, understood, maybe this whole locking thing
should be replaced with a better approach. First you mention in the first
blog entry:
"Mandatory locking is available too. It's based on the POSIX locking API
but not portable in itself. It's dangerous business and should
On Thu, 03.01.13 20:06, Stef Bon (stef...@gmail.com) wrote:
> Well, I'm working on notifyfs, a fuse fs which is a cache for gui clients
> and a filesystem event notifier. It uses inotify on linux to notify clients
> about changes. I want to be complete and add information about locks as
> well (ne
Well, I'm working on notifyfs, a fuse fs which is a cache for gui clients
and a filesystem event notifier. It uses inotify on linux to notify clients
about changes. I want to be complete and add information about locks as
well (new, changed and removed).
On the localhost this requires monitoring th
On Thu, Jan 3, 2013 at 6:38 PM, Lennart Poettering
wrote:
> On Wed, 02.01.13 22:59, Stef Bon (stef...@gmail.com) wrote:
>> sorry for the offtopic question here, but I do not know a better place for
>> it.
>>
>> I'm building a lockmonitor. I thought that would be just as easy as with
>> the /proc/
On Wed, 02.01.13 22:59, Stef Bon (stef...@gmail.com) wrote:
> Hi,
>
> sorry for the offtopic question here, but I do not know a better place for
> it.
>
> I'm building a lockmonitor. I thought that would be just as easy as with
> the /proc/self/mountinfo "file".
The poll-ability of /proc/self/m
No problem. Just a misunderstading or how you want to call it.
Stef
2013/1/2 Dave Reisner
>
> On Jan 2, 2013 5:41 PM, "Stef Bon" wrote:
> >
> > You are sure?? I mean the locks file, not the mounts file.
> > I think you haven't understood my post very good.
>
> Not a lack of understanding, jus
On Jan 2, 2013 5:41 PM, "Stef Bon" wrote:
>
> You are sure?? I mean the locks file, not the mounts file.
> I think you haven't understood my post very good.
Not a lack of understanding, just misread it. My bad.
___
systemd-devel mailing list
systemd-dev
You are sure?? I mean the locks file, not the mounts file.
I think you haven't understood my post very good.
Stef
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Jan 2, 2013 4:59 PM, "Stef Bon" wrote:
>
> Hi,
>
> sorry for the offtopic question here, but I do not know a better place
for it.
>
> I'm building a lockmonitor. I thought that would be just as easy as with
the /proc/self/mountinfo "file".
>
> But that is not the case. It's not pollable, like t
Hi,
sorry for the offtopic question here, but I do not know a better place for
it.
I'm building a lockmonitor. I thought that would be just as easy as with
the /proc/self/mountinfo "file".
But that is not the case. It's not pollable, like the mountinfo fle is.
I've looked into the code of the ke
13 matches
Mail list logo
