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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTim+pyy=Dr7-kMrSiG=5RHqY2L6P01m9hH171D8G@mail.gmail.com>
Date:	Wed, 2 Mar 2011 11:45:38 -0800
From:	Garrett Cooper <yanegomi@...il.com>
To:	subrata@...ux.vnet.ibm.com
Cc:	Paolo Ciarrocchi <paolo.ciarrocchi@...il.com>,
	Shubham Goyal <shubham@...ux.vnet.ibm.com>,
	ltp-list@...ts.sf.net, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	vapier@...too.org, chrubis@...e.cz
Subject: Re: [ANNOUNCE] The Linux Test Project has been released for FEBRUARY 2011.

On Wed, Mar 2, 2011 at 4:23 AM, Subrata Modak
<subrata@...ux.vnet.ibm.com> wrote:
> On Wed, 2011-03-02 at 13:06 +0100, Paolo Ciarrocchi wrote:
>> On Wed, Mar 2, 2011 at 12:40 PM, Shubham Goyal
>> <shubham@...ux.vnet.ibm.com> wrote:
>> > Hi,
>> >
>> > The Linux Test Project test suite has been released for the month of
>> > FEBRUARY 2011. Please see ltp/INSTALL file carefully, as there has
>> > been multiple changes for building/installing the test suite after the
>> > recent changes in Makefile infrastructure.
>>
>> Wouldn't make sense to integrate this test suite in the kernel source tree?
>
> There was discussion like this some few years back. The idea was to get
> some core tests from LTP to the kernel source tree. But then the idea
> was dropped probably to avoid maintenance overhead ;-)

Putting LTP in the kernel.org sources really doesn't make sense for
the following reasons:

1. LTP isn't really tied to a single kernel release.
2. LTP isn't the only test project out there for Linux.
3. LTP has more stuff than it needs to have for testing out the kernel
(well, it did more in the past before I started cleaning it up in the
past couple of months).
4. Maintaining it will become a political bloodbath for both parties
as Linux is loosely managed by Linus et all, and LTP has been largely
developed by SGI and maintained by IBM and a few other parties like
Fujitsu, Nokia, Redhat, etc.
5. Integrating LTP into Kbuild, etc would probably be non-trivial due
to the size of LTP (but it might be easier after the Makefile
restructuring I did a year and a half ago).

That being said, if Linux devs took the initiative and submitted
testcases that either illustrated past regressions in the kernel,
feature tested enhancements, and submitted documentation that actually
described their changes to the Linux kernel and the manpages project,
I would take this over having LTP in the linux sources because right
now things largely work because the Linux sources haven't really been
rototilled since 2.4 -> 2.6, but they are somewhat bitrotted and when
Linux rototills its sources again, we'll have to go through
rototilling our stuff as well.

Right now multiple QA engineers are sort of playing whack-a-mole
trying to figure out requirements and submit tests to LTP, and since
they don't have 100% context into the actual problem, some information
is lost in translation when the tests are submitted. This isn't
desirable.

Thanks,
-Garrett
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ