public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Tony Borras <tonyb@sysdev.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.35 tree abandoned/delayed?
Date: Tue, 17 Jul 2007 22:41:57 +0200	[thread overview]
Message-ID: <20070717204155.GE943@1wt.eu> (raw)
In-Reply-To: <20070716232357.3d9e5ca7.tonyb@sysdev.org>

Hi Tony,

[ first, please always keep people in CC on LKML since it's very easy to
  miss a thread ]

On Mon, Jul 16, 2007 at 11:23:57PM -0800, Tony Borras wrote:
> On Tue, 17 Jul 2007 07:20:06 +0200
> Willy Tarreau <w@1wt.eu> wrote:
> 
> > could you please report what the problem was, in case it's not
> > fixed yet ?
> 
> Ok, reproduced error at ./net/ipv4/fib_semantics.c
>   line 436 changed label:
>                    errout -> err_inval

I don't know where you downloaded 2.4.35-pre5 from, but I've checked the
sources and could not find any reference to "errout" here in any version!

Or what is possible is that your 2.4.34 kernel got corrupted on your disk
after applying any patch. Sometimes, some shell scripts providede with some
drivers directly tamper with the sources. You should check that your tree
is valid by downloading another one and comparing them.

It had already happened to me in the past and I got 3 or 4 private kernels
with a fix that I did not know I had applied. Fortunately, this does not
happen anymore with git ;-)

> then it builds fine!
> 
> started with linux-2.4.34
> then patched
>      patch-2.4.34.1
>      patch-2.4.34.2
>      patch-2.4.34.3
>      patch-2.4.34.4
>      patch-2.4.34.5
>      patch-2.4.35.pre5

Huh !!! You should not apply all 2.4.34 patches before 2.4.35. You should
see the development process like this :

---> 2.4.34 ----> 2.4.35-pre1 ----> 2.4.35-pre2 ---> ... ---> 2.4.35
       \
        `--> 2.4.34.1 --> 2.4.34.2 --> 2.4.34.3 ...

So 2.4.35-preX and 2.4.34.X are two different branches forked from 2.4.34.
All 2.4.35-preX patches are made for 2.4.34, and all 2.4.34.X patches are
made for 2.4.34 too.

You should see 2.4.34 as the real official kernel, and other ones as
convenience versions released in order to help people keep up to date
without having to use possibly buggy pre-releases, even if they are
quite close.

> I used a make oldconfig on a .config that builds in 2.4.34
> 
> Hope that helps
> TonyB

Thanks anyway for your feedback !

Regards,
Willy


  reply	other threads:[~2007-07-17 20:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8HJqo-2BV-23@gated-at.bofh.it>
     [not found] ` <8HJqo-2BV-21@gated-at.bofh.it>
     [not found]   ` <8HNDE-JM-11@gated-at.bofh.it>
2007-07-17  6:20     ` Linux 2.4.35 tree abandoned/delayed? Tony Borras
2007-07-17  7:23     ` Tony Borras
2007-07-17 20:41       ` Willy Tarreau [this message]
     [not found] <8HOJx-2nt-21@gated-at.bofh.it>
     [not found] ` <8HOJx-2nt-23@gated-at.bofh.it>
     [not found]   ` <8HOJx-2nt-25@gated-at.bofh.it>
     [not found]     ` <8HPFA-3Pn-17@gated-at.bofh.it>
     [not found]       ` <8I29I-6CE-21@gated-at.bofh.it>
2007-07-19  0:03         ` Tony Borras
2007-07-19  0:10           ` Jesper Juhl
2007-07-19  0:37             ` Tony Borras
2007-07-19  4:43           ` Willy Tarreau
     [not found] <20070716133025.55327074.tonyb@sysdev.org>
2007-07-17  0:30 ` Tony Borras
2007-07-17  5:16   ` Willy Tarreau

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=20070717204155.GE943@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tonyb@sysdev.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