mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "moreau francis" <francis_moreau2000@yahoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to test vanilla kernel
Date: Fri, 24 Mar 2006 10:00:26 +0100	[thread overview]
Message-ID: <9a8748490603240100v33097236v1ccc79871b285941@mail.gmail.com> (raw)
In-Reply-To: <20060324082444.69962.qmail@web25812.mail.ukl.yahoo.com>

On 3/24/06, moreau francis <francis_moreau2000@yahoo.fr> wrote:
> I'm wondering how you folks, install and run the latest vanilla kernel.

There are many ways to test a kernel.

The most basic test would be to grab the kernel sources, build a new
kernel, install it, boot it & see if it blows up.

If you want to get a bit more advanced the kernel sources include a
few modules to stress test different parts of the infrastructure. You
can run those.

You can build your kernels with different (sometimes unusual)
configuration options to test if some combination of options produce
bad results.

You can also write a few apps that test the various syscalls. Use
fuzzers to pass in random values to syscalls and check for errors.
Write scripts/apps to create/delete lots of random files, dirs etc to
test filesystems.
Run benchmark apps on different kernel versions to test for
performance regressions.

In short, use your imagination and try to crash the kernel in various ways.
If you happen to provoke a crash, bug, other unwanted behaviour;
gather all the info, and send in a bug report - see
Documentation/ReportingBugs.


> I guess
> that people install their prefered distrib as a start point

Ofcourse, you need a working install before you start replacing your kernel.

> and then download
> the kernel sources.

Yup.

>But each distrib patch and update the kernel,

Many do, but not all of them, some ship vanilla kernels, like my
personal favorite, Slackware.

> is it safe to
> forget them ?
>
Unless you have something setup on your box which depends on
functionality patched into the kernel by your vendor, then yes,
running a vanilla kernel is perfectly OK - if it was not we'd never
get it tested ;-)


> BTW, is there a 'best' distrib to achieve that ?
>
No.
Use whatever distro you happen to prefer.


--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2006-03-24  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-24  8:24 moreau francis
2006-03-24  9:00 ` Jesper Juhl [this message]
2006-03-24  9:35   ` moreau francis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9a8748490603240100v33097236v1ccc79871b285941@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=francis_moreau2000@yahoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®