linux-kernel - Re: [1/2] 2.6.22-rc5: known regressions with patches v2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 22 Jun 2007 14:13:59 +0200
From:	"Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc:	"Ni@m" <niam.niam@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [1/2] 2.6.22-rc5: known regressions with patches v2

On 22/06/07, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> On Fri, 22 Jun 2007 14:39:50 +0300
> "Ni@m" <niam.niam@...il.com> wrote:
>
> > > We have patches for "very high non-preempt latency in
> > > context_struct_compute_av()" and "list_add corruption. prev->next
> > > should be next (f7d28794), but was f0df8ed4 (prev=f0df8ed4) Kernel Bug
> > > at lib/list_debug.c:33", but both are too intrusive.
> > >
> > > Anyway, those bugs are not regressions.
> > The question was "why linux kernel release should have some bugs that
> > would be fixed fixed in future?"
>
> Because those bug fixes are intrusive so will potentially cause more
> other bugs that will need fixing - so make the kernel a worse not a
> better one in the short term.
>
> > Let's wait and publish kernel w/o known bugs.
>
> That would be a bit like waiting for a Debian release and never happen.

I'm trying to imagine this - Linux 2.6 "Debian style" roadmap:
15-VII-2007 - release of Linux 2.6.22
1-VIII-2007 - freeze
15-II-2009 - release of Linux 2.6.23
1-III-2009 - freeze
1-IX-2010 - release of Linux 2.6.24

:)

>
> Alan
>

Regards,
Michal

-- 
LOG
http://www.stardust.webpages.pl/log/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/