linux-kernel - Re: Wiki for automatic reports / fixes

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]

Message-ID: <CAB=NE6UR2_SQTxTe2E50fEGDg49F_jtYpbtcz90YdeKiJO5Tmg@mail.gmail.com>
Date:	Mon, 5 Oct 2015 10:03:04 -0700
From:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
To:	Ian Jackson <Ian.Jackson@...citrix.com>
Cc:	Fengguang Wu <fengguang.wu@...el.com>,
	Valentin Rothberg <valentinrothberg@...il.com>,
	Dan Carpenter <error27@...il.com>,
	Mel Gorman <mgorman@...e.de>,
	Steven Rostedt <rostedt@...dmis.org>,
	Johannes Thumshirn <jthumshirn@...e.de>,
	Konstantin Ryabitsev <mricon@...nel.org>,
	Jonathan Corbet <corbet@....net>,
	Lars Kurth <lars.kurth.xen@...il.com>,
	Stefano Stabellini <stefano.stabellini@...citrix.com>,
	Vitaly Kuznetsov <vkuznets@...hat.com>,
	Robert Schweikert <rjschwei@...e.com>, ms@...e.de,
	Juergen Gross <jgross@...e.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Joerg Roedel <jroedel@...e.de>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: Re: Wiki for automatic reports / fixes

On Mon, Oct 5, 2015 at 9:56 AM, Ian Jackson <Ian.Jackson@...citrix.com> wrote:
> Luis R. Rodriguez writes ("Wiki for automatic reports / fixes"):
> [...]
>>  While discussing expectations and information about
>> reports over these with Valentin it occurred to me information about
>> all these may be scattered separately and some developers may be
>> surprised when they first get reports / fixes from these sorts of
>> testing systems and that perhaps it may be useful if we had a single
>> wiki entry point where we could refer folks to the different ongoing
>> testing infrastructures out there working upstream.
>>
>> If we could piggy back off of an already existing wiki then great, but
>> if not I was thinking something off of wiki.kernel.org might be good.
>> How about tests.wiki.kernel.org ? If such projects don't have a wiki
>> they could perhaps use pages off of tests.wiki.kernel.org to elaborate
>> and set expectations straight. Thoughts?
>
> To clarify what I think you are suggesting, is to create a new wiki or
> wiki page which gives information about automatic tests that are
> performed on upstream (or going-upstream) Linux branches ?

That's right, as it stands we have a slew of folks doing a series of
battery of tests on either linux-next or other branches, and
developers / maintainers get e-mails about this. Typically one becomes
aware of these tests through experience and in dealing with reports
but other times one may not even be aware of ongoing effort on this
front, such was the case of Valentin's dead code analysis with
undertaker. Knowing what existing work is being done can and could be
used can also save people from re-inventing the wheel, but also and
most importantly collaborate.

> I think this is a good idea.  I'm not sure how much information we
> need for each tester, but a page for each would be about right.

Sure, I figure if each tester framework has its own dedicated page we
can at least refer to it, but a basic page which describes general
coverage / mailing lists / contact info / and what to expect might be
useful. As it stands most of this is just tribal knowledge.

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