linux-kernel - RE: [PATCH V2 1/6] drivers/staging/ramster: cluster/messaging foundation

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:	Tue, 27 Dec 2011 12:29:46 -0800 (PST)
From:	Dan Magenheimer <dan.magenheimer@...cle.com>
To:	Valdis.Kletnieks@...edu
Cc:	greg@...ah.com, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	ngupta@...are.org, Konrad Wilk <konrad.wilk@...cle.com>,
	Kurt Hackel <kurt.hackel@...cle.com>,
	sjenning@...ux.vnet.ibm.com, Chris Mason <chris.mason@...cle.com>
Subject: RE: [PATCH V2 1/6] drivers/staging/ramster: cluster/messaging
 foundation

> From: Valdis.Kletnieks@...edu [mailto:Valdis.Kletnieks@...edu]
> Sent: Tuesday, December 27, 2011 1:06 PM
> To: Dan Magenheimer
> Cc: greg@...ah.com; devel@...verdev.osuosl.org; linux-kernel@...r.kernel.org; linux-mm@...ck.org;
> ngupta@...are.org; Konrad Wilk; Kurt Hackel; sjenning@...ux.vnet.ibm.com; Chris Mason
> Subject: Re: [PATCH V2 1/6] drivers/staging/ramster: cluster/messaging foundation
> 
> On Thu, 22 Dec 2011 07:50:50 PST, Dan Magenheimer said:
> 
> > Copy cluster subdirectory from ocfs2.  These files implement
> > the basic cluster discovery, mapping, heartbeat / keepalive, and
> > messaging ("o2net") that ramster requires for internode communication.
> 
> Instead of doing this, can we have the shared files copied to a common
> subdirectory so that ramster and ocfs2 can share them, and we only
> have to fix bugs once?

Hi Valdis --

Thanks for your reply!

Per the discussion at:
https://lkml.org/lkml/2011/12/22/369 
your suggestion of the common subdirectory will definitely need to happen
before ramster can be promoted out of staging and, at GregKH's request,
I have added a TODO file in V3 to state that.  Before that can happen,
we'll need to work with the ocfs2 maintainers to merge the
necessary ramster-specific changes and implement a separately CONFIG-able
subdirectory for the ocfs2 cluster code.

Dan

--
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/