linux-kernel - Re: [PATCH] coda: alloc_upcall: s/task_pgrp_nr/task_pgrp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 21 Jan 2009 00:03:11 -0500
From:	Jan Harkes <jaharkes@...cmu.edu>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Pavel Emelyanov <xemul@...nvz.org>,
	Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] coda: alloc_upcall: s/task_pgrp_nr/task_pgrp_vnr/

On Sun, Jan 18, 2009 at 08:34:53AM +0100, Oleg Nesterov wrote:
> Needs an ack from maintaner, I do not know where coda_in_hdr->pgid is used.

It is used to uniquely identify a process and any of it children during
conflict resolution.

When a conflict is detected, all accesses to the inconsistent object are
blocked. A special resolver process is forked off by the cache manager
and this is run in a new process group and only accesses from processes
in this group are allowed. The resolver process (or any of it's children)
compare the conflicting replicas, and ideally resolve the inconsistency
after which normal accesses are unblocked.

So yes this should not a per namespace thing, but also not a process
specific pid, the resolver forks off different helper processes
depending on the type of files that are involved in the conflict, i.e.
mbox files require different merge strategy compared to opendocument
files.

I'm not sure what you are trying to do.

Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/