Re: Linux 2.4.16-pre1

Patrick McFarland
2001-11-25T02:44:02Z

Okay, so it was 14 that had the file loopback bug, and 12 that had the ieee bug.Those bugs shouldnt have been in there in the first place! Those are very major potentially show stopping bugs. What If I get up one day, and I cant print? Or build isos? That sounds minor to you, but thats a big thing if say, the linux box is a network print server, or, its the workstation for the guy in the company who builds the iso. And, no, "use the previous kernel" isnt a good excuse. Because what if you get hit with bugs back to back? You'll have to go back to some kernel way way back. Like 2.4.2. The Kernel needs Quality Assurance.

On 24-Nov-2001, war wrote:
> 2.4.14 - Has deactivate_page linker bug. Fix: Edit loop.c, and delete the deactivate_page() function calls.
>
> 2.4.13 - No known bugs.
>
> 2.4.12 - Parallel port driver broken in this release.
>
> 2.4.11 - Allows local denial of service using symlinks.
>
> http://www.ramdown.com/war/kernel.html
>
> Patrick McFarland wrote:
>
> > er, I think I ment 2.4.13 for the loopback bug... or did that have the ieee parport problem...
> >
> > On 24-Nov-2001, Patrick McFarland wrote:
> > > Heh, speaking about stuff like this, isnt testing suppost to happen to kernels? I mean, in 2.4.14 we had the file loopback problem (_alot_ of people use that module, its great for building iso images and stuff) and then we have the inode.c bug (which may or may not exist and the fix may or may not actually fix it) then it seems bugs in other sections of the kernel. Whats going on Linus? Stable kernel releases were never this bad before.
> > >
> > > On 24-Nov-2001, Linus Torvalds wrote:
> > > >
> > > > On Sat, 24 Nov 2001, Marcelo Tosatti wrote:
> > > > > >
> > > > > > Are these going to appear on the front page of kernel.org?
> > > > >
> > > > > They have to...
> > > > >
> > > > > I'm sure hpa will do that as soon as he has time to...
> > > >
> > > > I also decided that the suggestion to move the "testing" subdirectory down
> > > > to below the kernel that the directory is for is a good idea.
> > > >
> > > > So I moved all the 2.5.x testing stuff to kernel/v2.5/testing, leaving the
> > > > old kernel/testing directory basically orphaned.
> > > >
> > > > Marcelo could either take over the old directory (which will make his
> > > > pre-patches show up on kernel.org automatically), or preferably just do
> > > > the same thing, and make the v2.4 test patches in v2.4/testing (which will
> > > > also require support from the site admin, who is probably overworked as-is
> > > > with the RAID failures ;)
> > > >
> > > > Linus
> > > >
> > > > -
> > > > 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/
> > > >
> > >
> > > --
> > > Patrick "Diablo-D3" McFarland || unknown@panax.com
> > > -
> > > 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/
> > >
> >
> > --
> > Patrick "Diablo-D3" McFarland || unknown@panax.com
> > -
> > 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/
>

--
Patrick "Diablo-D3" McFarland || unknown@panax.com