Path: archiver1.google.com!news2.google.com!fu-berlin.de!bofh.it!robomod
From: Linus Torvalds <torva...@osdl.org>
Newsgroups: linux.kernel
Subject: Linux 2.6.0
Date: Thu, 18 Dec 2003 05:20:37 +0100
Message-ID: <13XOk-1FW-25@gated-at.bofh.it>
X-Original-To: Kernel Mailing List <linux-ker...@vger.kernel.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: robo...@news.nic.it
X-Mailing-List: linux-kernel@vger.kernel.org
Approved: robo...@news.nic.it
Lines: 154
Organization: linux.* mail to news gateway
X-Original-Date: Wed, 17 Dec 2003 20:14:06 -0800 (PST)
X-Original-Message-ID: <Pine.LNX.4.58.0312171951030.5789@home.osdl.org>
X-Original-Sender: linux-kernel-ow...@vger.kernel.org


				"The beaver is out of detox"
						- Anon

This should not be a big surprise to anybody on the list any more, since
we've been building up to it for a long time now, and for the last few
weeks I haven't accepted any patches except for what amounts to fairly
obvious one-liners.

Anyway, 2.6.0 is out there now, and the patch from -test11 is a swelte 
11kB in size. It's not the totally empty patch I was hoping for, but 
judging by the bugs I worked on personally, things are looking pretty 
good. 

To give you an example, one of the nastier bugs that we chased for the 
last five weeks was a bug that could only be reproduced reliably on a 
16- or 32-way system, and only when the system had flaky disks. Putting in 
known-good disks made the problem disappear. Similarly, compiling the 
kernel with another compiler made the problem disappear.

It turned out to be a really subtle bug wrt SMP ordering and stack
allocation, and lots of thanks to Ram Pai for gathering all the
information that eventually led to it being fixed. The fix was a one-liner
and a big comment - but my point is that the quality of bugs has been
pretty high lately, and we feel that we're in pretty good shape.

Andrew has written up some caveats and pointers to information about 2.4.x
vs 2.6.x changes, and I'll let him post that. Some known issues were not
considered to be release-critical and a number of them have pending fixes
in the -mm queue. Generally they just didn't have the kind of verification
yet where I was willing to take them in order to make sure a fair 2.6.0
release.

NOTE! I'll continue to keep track of the 2.6 BK tree until we're closer to
the time when we literally split it for 2.7.x, because both Andrew and I
are pretty comfortable with our respective toolchains. But Andrew is the
stable tree maintainer, so everything should be approved by him at this
point. Think of the -mm tree as the staging area, and mine as a release
tree. We'll work together, but Andrew is boss.

(BK merging will have to go through some approval format, we'll see how
that works out exactly).

		Linus

---

Summary of changes from v2.6.0-test11 to v2.6.0
============================================

Alan Stern:
  o USB: fix bug not setting device state following usb_device_reset()

Andrey Borzenkov:
  o USB: prevent catch-all USB aliases in modules.alias

Arnaldo Carvalho de Melo:
  o [IPV6]: Fix TCP socket leak

David Brownell:
  o USB: fix remove device after set_configuration

David S. Miller:
  o [NETFILTER]: In conntrack, do not fragment TSO packets by accident
  o [PKT_SCHED]: Do not dereference the special pointer value 'HTB_DIRECT'

Greg Kroah-Hartman:
  o USB: register usb-serial ports in the proper place in sysfs
  o USB: fix race with hub devices disconnecting while stuff is still
    happening to them
  o USB: fix bug for multiple opens on ttyUSB devices
  o kobject: fix bug where a parent could be deleted before a child
    device

Harald Welte:
  o [NETFILTER]: Sanitize ip_ct_tcp_timeout_close_wait value, from 2.4.x

Herbert Xu:
  o USB: Fix connect/disconnect race

Hideaki Yoshifuji:
  o [IPV6]: Fix ipv4 mapped address calculation in udpv6_sendmsg()

Hirofumi Ogawa:
  o Missing initialization of /proc/net/tcp seq_file

Ingo Molnar:
  o Fix lost wakeups problem
  o Fix /proc access to dead thread group list oops

James McMechan:
  o tmpfs oops fix

Jean Delvare:
  o I2C: fix i2c_smbus_write_byte() for i2c-nforce2

Jeff Garzik:
  o fix use-after-free in libata
  o fix oops on unload in pcnet32
  o remove manual driver poisoning of net_device
  o wireless airo oops fix

Jens Axboe:
  o fix broken x86_64 rdtscll
  o scsi_ioctl memcpy'ing user address
  o no bio unmap on cdb copy failure
  o Fix IDE bus reset and DMA disable when reading blank DVD-R
  o CDROM_SEND_PACKET bug

Jes Sorensen:
  o qla1280 crash fix in error handling

Julian Anastasov:
  o [BRIDGE]: Provide correct TOS value to IPv4 routing

Linus Torvalds:
  o Fix x86 kernel page fault error codes
  o Fix ide-scsi.c uninitialized variable
  o Fix the PROT_EXEC breakage on anonymous mmap
  o Fix subtle bug in "finish_wait()", which can cause kernel stack
    corruption on SMP because of another CPU still accessing a
    waitqueue even after it was de-allocated.
  o More subtle SMP bugs in prepare_to_wait()/finish_wait()
  o Fix thread group leader zombie leak

Martin Devera:
  o [PKT_SCHED]: In HTB, filters must be destroyed before the classes

Matthew Dharm:
  o USB storage: fix for jumpshot and datafab devices

Neil Brown:
  o Fix possible bio corruption with RAID5

Oliver Neukum:
  o USB: fix sleping in interrupt bug in auerswald driver
  o USB: fix race with signal delivery in usbfs

Pavlin Radoslavov:
  o [RTNETLINK]: Add RTPROT_XORP

René Scharfe:
  o HPFS: missing lock_kernel() in hpfs_readdir()

Tom Rini:
  o USB: mark the scanner driver as obsolete

Ulrich Drepper:
  o Fix 'noexec' behaviour
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Path: archiver1.google.com!news2.google.com!newsfeed2.dallas1.level3.net!
news.level3.com!news-out.visi.com!petbe.visi.com!news.tele.dk!
news.tele.dk!small.news.tele.dk!tiscali!newsfeed1.ip.tiscali.net!
news.cid.net!bofh.it!robomod
From: Andrew Morton <a...@osdl.org>
Newsgroups: linux.kernel
Subject: Re: Linux 2.6.0
Date: Thu, 18 Dec 2003 06:20:21 +0100
Message-ID: <13YK9-2W3-13@gated-at.bofh.it>
References: <13XOk-1FW-25@gated-at.bofh.it>
X-Original-To: linux-ker...@vger.kernel.org
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i686-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: robo...@news.nic.it
X-Mailing-List: linux-kernel@vger.kernel.org
Approved: robo...@news.nic.it
Lines: 86
Organization: linux.* mail to news gateway
X-Original-Date: Wed, 17 Dec 2003 21:15:16 -0800
X-Original-Message-ID: <20031217211516.2c578bab.akpm@osdl.org>
X-Original-References: <Pine.LNX.4.58.0312171951030.5...@home.osdl.org>
X-Original-Sender: linux-kernel-ow...@vger.kernel.org

Linus Torvalds <torva...@osdl.org> wrote:
>
> Andrew has written up some caveats and pointers to information about 2.4.x
>  vs 2.6.x changes, and I'll let him post that. Some known issues were not
>  considered to be release-critical and a number of them have pending fixes
>  in the -mm queue. Generally they just didn't have the kind of verification
>  yet where I was willing to take them in order to make sure a fair 2.6.0
>  release.

It's actually rather short because I started late.  See below.

There are also the "must-fix" and "should-fix" lists of items which we have
identified as still on the 2.6 todo list.  These are at

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/must-fix/must-fix-7.txt and
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/must-fix/should-fix-7.txt




- The 2.6.0 kernel has undergone several weeks of stabilization and we
  expect it to run well on server-class machines.

  Desktops and laptops may have more trouble at this time because of the
  much wider range of hardware and because of as-yet unimplemented fixes for
  the hardware and BIOS bugs from which these machines tend to suffer.

  During the 2.6.0 stabilization period a significant number of less
  serious fixes have accumulated in various auxiliary kernel trees and these
  shall be merged into the 2.6 stream after the 2.6.0 release.  Many of these
  fixes appear in Andrew Morton's "-mm" tree, at

	ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/

- Please report any problems to the appropriate mailing list.  If you do
  not know which list to use, send the report to linux-ker...@vger.kernel.org
  and it should reach the right person.  Some active subsystem mailing lists
  are:

	linux1394-de...@lists.sourceforge.net
	linux-...@oss.sgi.com
	linux-a...@intel.com
	linux-s...@vger.kernel.org
	ext2-de...@lists.sourceforge.net
	linux-usb-us...@lists.sourceforge.net

  Alternatively, kernel bug reports may be entered into the kernel bug
  tracking system at http://bugme.osdl.org/

- There are significant changes in the module subsystem, the LVM (Device
  Mapper) and RAID subsystems.  Details about these and many other kernel
  changes are presented in David Jones's kernel upgrade document at

	http://www.linux.org.uk/~davej/docs/post-halloween-2.6.txt

  Users who are testing 2.6 kernels for the first time should consult this
  document.

- The ATA RAID drivers (eg the HighPoint RAID driver) have not been ported
  to the new BIO code and are not available under the 2.6 kernel at this
  time.

- cryptoloop doesn't work on highmem machines.  Fixes exist in -mm and are
  queued for 2.6.1.

- There are known performance problems with the default disk I/O scheduler
  which show up when the workload is performing small, random reads and
  writes (ie: database loads).  Largely fixed in -mm.

  In general, the "deadline" I/O scheduler is, and shall remain somewhat
  faster than the default "anticipatory" I/O scheduler with these sorts of
  workloads.  Database admins should consider adding the "elevator=deadline"
  kernel boot parameter.

- There are performance problems due to misbehaviour in the readahead code
  which also impact database-style workloads.  Fixed in -mm, queued for
  2.6.1.

- There are a larger number of as-yet unmerged frame buffer driver fixes.


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