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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <a9e22dff0706220439m4bc70a30i8cc83fe92cff8bc9@mail.gmail.com>
Date:	Fri, 22 Jun 2007 14:39:50 +0300
From:	"Ni@m" <niam.niam@...il.com>
To:	"Michal Piotrowski" <michal.k.k.piotrowski@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [1/2] 2.6.22-rc5: known regressions with patches v2

> 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.
>

Are you going to release 2.6.22 with this bugs?? But question wasn't
on this subject ...
The question was "why linux kernel release should have some bugs that
would be fixed fixed in future?"
Let's wait and publish kernel w/o known bugs. Let's wait for some
time, let's publish 2.6.22-rc_last, test it for some time(2 weeks for
example), fix bugs if any and after _test_period_of_whole_kernel_ but
not _separate_patches/parts_ of kernel release stable one!
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ