linux-kernel - Re: [Ksummit-2008-discuss] Fixing the Kernel Janitors project

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:	Sat, 31 May 2008 10:38:08 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Chris Mason <chris.mason@...cle.com>,
	ksummit-2008-discuss@...ts.linux-foundation.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-2008-discuss] Fixing the Kernel Janitors project

Hi!

> > One motivation here is to bring bug reporters from active distro 
> > communities into testing mainline kernels as well.
> 
> My experience from handling both distro-reported and upstream-reported 
> bugs shows that these two worlds/communitites are really quite different 
> in their nature.
> 
> Bug reporters who report bug in the vanilla kernel are usually perfectly 
> fine when someone sends them patch to test, they don't have any problem 
> recompiling the patched kernel, testing, and reporting back.
> 
> This is not the case with distro kernel bug reporters at all. You usually 
> can't just tell them "hey, this patch might fix it, report back if it 
> does". Vast majority of theese users expect the kernel package built for 
> their distro to be provided, so that they can easily install it and test 
> it, but requiring any other effort usually doesn't work.

I guess this would be helped if we actually made compiling distro
kernel easy.

Default suse installation does not even contain gcc; I'm not sure if
we provide our kernel in easy-to-use git form, and I don't think many
suse people would be able to create kernel .rpm without help of
autobuild system... autobuild only works behind suse firewall and
buildservice is not really right answer either.

Having compile-me-kernel script that does all the neccessary steps of
compiling/installing distro kernel with custom patches would be great
way forward...

Plus, we do very little q&a on distro kernel w.r.t to non-standard
.config files. Improving that would be some work, but there would be
chance for 'disable CONFIG_NO_HZ and see if it helps' kind of
debugging.

Oh and having make prepare-kernel-for-this-distro in vanilla would
help a lot, too. Usually, vanilla boots and works on distro with
suitable config, but finding that config is not too easy.
							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/