Re: Re: loop back broken in 2.2.14

Re: Re: loop back broken in 2.2.14

[joeja]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]

Okay, I can delete out those two lines to get loop working.

Is 2.4.x really a stable tree?  Or should I wait for 2.4.25 before I consider it really stable?

> > François Cami wrote:
> >
> > > yes, see 2.4.15pre1
> > > warning, the iptables code in 2.4.15pre1 and pre2 seems broken.
> >
> > and further it is likely that pre3 fixes iptables code :)
> > (it looks like the patch got reverted)
>
> Actually it doesn't seem to be reverted,
> just reworked -

hmm, spoke too soon -

looks like they were reverted after all...

cu

jjs

Re: Re: loop back broken in 2.2.14

[joeja]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2541 bytes --]

I thought that the -pre would be the developer kernels, and that an actual release (2.4.14) would have been somewhat tested.  I fully understand that a 'runtime' bug in the vm or some other system could arrise and that is one thing. I also understand when a 'less used' driver like NTFS or VFAT breaks, but to see bugs in the loop device in a 'stabilizing' kernel is something that I thought I'd never see.

Hmm anyone working on a regression testing tool for the kernel compilation options??

Also new features DO go into stable trees, there are many times when 2.3.x was open that stuff was backported to 2.2.x.  I also heard that ext3 might end up in 2.4.15, which I'd love to see happen (that and lm_sensors)

I DO think that there needs to be a better way of handling some of these small bugs.  Like maybe where the kernel is posted (in my case obtaining from ftp.kernel.org) there should be a readme.first.2.4.14 for every version of the kernel and in there things like this could be stated.  Simple one line in loop.c commment out the two lines or remove the two lines with deactivate_page.  

I don't mind 'testing', but how can you test what wont compile or what compiles but does not run?

Joe
John Alvord <jalvo@mbay.net> wrote:
> In developer-speak, stable == stablizing, which means that fixes go in
but no new features. That can include monstrous fixes like the VM
cleanup.

When you are running developer kernels, you are on the kernel test
team whether you know it or not, whether you think thats OK or hate
it.

For "stable" kernels, wait for the distributors like red hat/suse/etc.
There is no way around serious testing which they perform.

john


On Mon, 12 Nov 2001 12:40:43 -0500, joeja@mindspring.com wrote:

>Okay, I can delete out those two lines to get loop working.
>
>Is 2.4.x really a stable tree?  Or should I wait for 2.4.25 before I consider it really stable?
>
>> > François Cami wrote:
>> >
>> > > yes, see 2.4.15pre1
>> > > warning, the iptables code in 2.4.15pre1 and pre2 seems broken.
>> >
>> > and further it is likely that pre3 fixes iptables code :)
>> > (it looks like the patch got reverted)
>>
>> Actually it doesn't seem to be reverted,
>> just reworked -
>
>hmm, spoke too soon -
>
>looks like they were reverted after all...
>
>cu
>
>jjs
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/

Re: loop back broken in 2.2.14

[J Sloan]

joeja@mindspring.com wrote:

> Okay, I can delete out those two lines to get loop working.
>
> Is 2.4.x really a stable tree?  Or should I wait for 2.4.25 before I consider it really stable?

If by stable you mean "unchanging", of course not -

much development is still happening.

If however by stable you mean "does not crash",
it has been very stable here, with a few known
needed patches applied.  2.4.14 is stable for me
on all systems, but compaq smart controllers do
need a small patch - I am also running the low
latency and/or preempt patches with excellent
stability.

cu

jjs

Re: Re: loop back broken in 2.2.14

[Michael Peddemors]

Well, the loopback bug is a pain.. but we have had these pains on quite
a few releases in the 2.4.x series... 

I wonder if maybe a new method of distributing kernels should happen..
2.4.14 should become 2.4.14-stable meaning that it never ever changes
after release, and 2.4.14-fixed means that these tiny typos, gotchas,
and backport driver fixes can get into 2.4.14-fixed which may change
from day to day, but not get any enhancements, only minor fixes..

People could try 2.4.14-stable, and if they have a problem, they could
just try the 2.4.14-fixed to see if their problem is already
addressed...

The idea is that at least every major release kernel should compile, and
it would reduce the noise levels from people trying out *stable* kernel
versions..

Just a thought..

On Mon, 2001-11-12 at 12:27, joeja@mindspring.com wrote:
> I thought that the -pre would be the developer kernels, and that an actual release (2.4.14) would have been somewhat tested.  I fully understand that a 'runtime' bug in the vm or some other system could arrise and that is one thing. I also understand when a 'less used' driver like NTFS or VFAT breaks, but to see bugs in the loop device in a 'stabilizing' kernel is something that I thought I'd never see.
> 

-- 
"Catch the Magic of Linux..."
--------------------------------------------------------
Michael Peddemors - Senior Consultant
LinuxAdministration - Internet Services
NetworkServices - Programming - Security
Wizard IT Services http://www.wizard.ca
Linux Support Specialist - http://www.linuxmagic.com
--------------------------------------------------------
(604)589-0037 Beautiful British Columbia, Canada