Skip to contentSkip to conversation

Linux 2.4.35 tree abandoned/delayed?

DISCUSSION Tony Borras 3 participants 4 messages Jul 19, 2007 5 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw
Quoted 17 lines · On Tue, 17 Jul 2007 22:50:10 +0200 Willy Tarreau <[email protected]> wrote:

Hi Tony,

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

Quoted 9 lines · Tony Borras
Quoted 2 lines · On Tue, 17 Jul 2007 07:20:06 +0200 Willy Tarreau <[email protected]> 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
Quoted 7 lines

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

Negatory on that, Willy!

Here is what I have verified:
At kernel.org:/pub/linux/v2.4

file: patch-2.4.34.3.bz2 has the corruption at line 213:
goto errout

That is where that came from, when I patched my 2.4.34 to arrive at 2.4.34.5, before applying the 2.4.35.rc5 patch!

Hope that helps, maybe you can fix, because I cant post to kernel.org v2.4 tree, that I know of.

TonyB

There are 10 types of people in this world, those that read binary and those who don't!

--
__ __ _ I N C. http://www.sysdev.org

/ __|\\// __||  \  __   __          /         [email protected]
\__ \ \/\__ \||)|/ O_)\/ /        \/  System Tools / Utilities
|___/ || ___/|_ /\___|\_/        WIntel / Linux Device Drivers
#6 lore raw
Quoted 30 lines · Tony Borras
Quoted 17 lines · On Tue, 17 Jul 2007 22:50:10 +0200 Willy Tarreau <[email protected]> wrote:

Hi Tony,

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

Quoted 9 lines · Tony Borras
Quoted 2 lines · On Tue, 17 Jul 2007 07:20:06 +0200 Willy Tarreau <[email protected]> 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
Quoted 7 lines

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

Negatory on that, Willy!

Quoted 9 lines

Here is what I have verified:
At kernel.org:/pub/linux/v2.4

file: patch-2.4.34.3.bz2 has the corruption at line 213:
goto errout

That is where that came from, when I patched my 2.4.34 to arrive at 2.4.34.5, before applying the 2.4.35.rc5 patch!

That sounds wrong. To the best of my knowledge, the 2.4.35-rc5 patch should be applied on top of 2.4.34, not on top of 2.4.34.5 ...

Signature · 3 lines
Jesper Juhl <[email protected]>
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
#7 lore raw
Quoted 16 lines · On Thu, 19 Jul 2007 02:10:58 +0200 "Jesper Juhl" <[email protected]> wrote:
Quoted 6 lines

file: patch-2.4.34.3.bz2 has the corruption at line 213:
goto errout

That is where that came from, when I patched my 2.4.34 to arrive at 2.4.34.5, before applying the 2.4.35.rc5 patch!

That sounds wrong. To the best of my knowledge, the 2.4.35-rc5 patch should be applied on top of 2.4.34, not on top of 2.4.34.5 ...

Signature · 5 lines
Jesper Juhl <[email protected]>
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

You are absolutely right! Since I was keeping a 2.4.34.current and 2.4.35.pre5 is just a pre, I stupidly slapped it on top at my current build tree!

too much Summer partying!

Thanks a lot!
TonyB

There are 10 types of people in this world, those that read binary and those who don't!

--
__ __ _ I N C. http://www.sysdev.org

/ __|\\// __||  \  __   __          /         [email protected]
\__ \ \/\__ \||)|/ O_)\/ /        \/  System Tools / Utilities
|___/ || ___/|_ /\___|\_/        WIntel / Linux Device Drivers
#8 lore raw
In reply to Tony Borras
Quoted 30 lines · Tony Borras
Quoted 17 lines · On Tue, 17 Jul 2007 22:50:10 +0200 Willy Tarreau <[email protected]> wrote:

Hi Tony,

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

Quoted 9 lines · Tony Borras
Quoted 2 lines · On Tue, 17 Jul 2007 07:20:06 +0200 Willy Tarreau <[email protected]> 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
Quoted 7 lines

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

Negatory on that, Willy!

Quoted 8 lines

Here is what I have verified:
At kernel.org:/pub/linux/v2.4

file: patch-2.4.34.3.bz2 has the corruption at line 213:
goto errout

That is where that came from, when I patched my 2.4.34 to arrive at 2.4.34.5,

So your 2.4.34.5 tree is wrong, you forgot to apply 2.4.34.4 to it, which only fixes this goto. You should rebuild your 2.4.34.X tree from scratch.

Quoted 1 line

before applying the 2.4.35.rc5 patch!

No, once again, you should not apply any 2.4.35-preX to 2.4.34.X. You should apply it to plain 2.4.34.

If you don't have it anymore, I suggest that you revert the 2.4.34.X patches with "patch -R".

Also, I think you got a lot of rejects when applying 2.4.35 on top of 2.4.34.X since most changes are the sames.

Regards,
Willy