linux-kernel - Re: Future of Lustre in staging

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] [day] [month] [year] [list]

Message-ID: <D2773FFF.11BF44%andreas.dilger@intel.com>
Date:	Mon, 23 Nov 2015 23:37:19 +0000
From:	"Dilger, Andreas" <andreas.dilger@...el.com>
To:	Denis Kirjanov <kirjanov@...il.com>,
	Xose Vazquez Perez <xose.vazquez@...il.com>
CC:	Greg KH <gregkh@...uxfoundation.org>,
	Christoph Hellwig <hch@...radead.org>,
	"Drokin, Oleg" <oleg.drokin@...el.com>,
	Staging <driverdev-devel@...uxdriverproject.org>,
	Lustre devel <lustre-devel@...ts.lustre.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Future of Lustre in staging

On 2015/11/20, 06:30, "Denis Kirjanov" <kirjanov@...il.com> wrote:

>On 11/20/15, Xose Vazquez Perez <xose.vazquez@...il.com> wrote:
>> Hi,
>>
>> From https://lwn.net/Articles/662979/
>>
>> --cut--
>> Christoph complained a bit about the staging tree. He said that it
>> breaks allmodconfig builds, but that problem was evidently fixed a while
>> ago. He also dislikes the Lustre filesystem, which has been in staging
>> for some time now; Greg agreed and said that he would like to delete it.
>> It was generally agreed that the work being done on Lustre is not
>> substantial enough to justify its continued presence. Christoph also
>> said that the use of the staging tree for code that is about to be
>> deleted could be improved; there are, he said, people doing white-space
>> fixes on doomed code.
>> --end--
>>
>> Could anyone clarify it?
>
>AFAIK, Intel is going to work more harder on Lustre code, so the best
>option would be to wait a bit.
>Agreed, checkpatch fixes are just a mess..

I think it is important to note that it isn't just Intel working on this
code, but also ORNL, Cray, Indiana University, and others.

As for build breakage pf Lustre in staging, more often as not that is due
to patches landing outside of staging that cause Lustre builds to break.
That isn't really something that we can control while Lustre is in the
staging branch if that isn't required for normal builds.  The zero-day
patch bot has been good at catching those issues, and we've been good at
submitting fixes quickly, so I don't think it is a huge problem.

Cheers, Andreas
-- 
Andreas Dilger

Lustre Principal Architect
Intel High Performance Data Division


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