Senior Windows Engineer (NC) Next Step Systems US-NC-Charlotte Post A Job | Post A Resume

"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:

• USB: fix bug not setting device state following usb_device_reset()

Andrey Borzenkov:

• USB: prevent catch-all USB aliases in modules.alias

Arnaldo Carvalho de Melo:

• [IPV6]: Fix TCP socket leak

David Brownell:

• USB: fix remove device after set_configuration

David S. Miller:

• [NETFILTER]: In conntrack, do not fragment TSO packets by accident
• [PKT_SCHED]: Do not dereference the special pointer value 'HTB_DIRECT'

Greg Kroah-Hartman:

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

Harald Welte:

• [NETFILTER]: Sanitize ip_cttcp_timeoutclose_wait value, from 2.4.x

Herbert Xu:

• USB: Fix connect/disconnect race

Hideaki Yoshifuji:

• [IPV6]: Fix ipv4 mapped address calculation in udpv6_sendmsg()

Hirofumi Ogawa:

• Missing initialization of /proc/net/tcp seq_file

Ingo Molnar:

• Fix lost wakeups problem
• Fix /proc access to dead thread group list oops

James McMechan:

• tmpfs oops fix

Jean Delvare:

• I2C: fix i2c_smbus_write_byte() for i2c-nforce2

Jeff Garzik:

• fix use-after-free in libata
• fix oops on unload in pcnet32
• remove manual driver poisoning of net_device
• wireless airo oops fix

Jens Axboe:

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

Jes Sorensen:

• qla1280 crash fix in error handling

Julian Anastasov:

• [BRIDGE]: Provide correct TOS value to IPv4 routing

Linus Torvalds:

• Fix x86 kernel page fault error codes
• Fix ide-scsi.c uninitialized variable
• Fix the PROT_EXEC breakage on anonymous mmap
• 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.
• More subtle SMP bugs in prepare_to_wait()/finish_wait()
• Fix thread group leader zombie leak

Martin Devera:

• [PKT_SCHED]: In HTB, filters must be destroyed before the classes

Matthew Dharm:

• USB storage: fix for jumpshot and datafab devices

Neil Brown:

• Fix possible bio corruption with RAID5

Oliver Neukum:

• USB: fix sleping in interrupt bug in auerswald driver
• USB: fix race with signal delivery in usbfs

Pavlin Radoslavov:

• [RTNETLINK]: Add RTPROT_XORP

René Scharfe:

• HPFS: missing lock_kernel() in hpfs_readdir()

Tom Rini:

• USB: mark the scanner driver as obsolete

Ulrich Drepper:

• Fix 'noexec' behaviour

Index Mode   |   Flat Mode   |   Thread Mode   |   Thread Flat     Talkback(s) Name  and Date   At last...    andrew Dec 18, 2003, 13:05:49     Appreciative...    Nicholas Donovan Dec 18, 2003, 13:07:51     flaky disks ??    ac Dec 18, 2003, 13:08:16     No 3.0?    -bertox Dec 18, 2003, 13:16:31     Nice :-)    Jo Řiongen Dec 18, 2003, 13:34:16     uname    Joe Black Dec 18, 2003, 13:35:25     Congratulation!!!    Gunnar Dec 18, 2003, 13:38:09     Re: No 3.0?    marc Dec 18, 2003, 14:14:22     Congrats and Thanks    Dave Dec 18, 2003, 14:46:16     Linux 2004    Avenger Dec 18, 2003, 14:49:49     What's new in 2.6?    reformer Dec 18, 2003, 14:50:12     Re: No 3.0?    Mecworks Dec 18, 2003, 14:51:08     Many Thanks    greg&Stevens Dec 18, 2003, 14:51:34     Christmas Present    Carlos Vermejo Ruiz Dec 18, 2003, 15:07:01     Re: No 3.0?    Tang Kai Dec 18, 2003, 15:10:54     Thank you    NewMan Dec 18, 2003, 15:13:14     Re: What's new in 2.6?    Nicholas Donovan Dec 18, 2003, 15:49:58     Re: Re: No 3.0?    bystander Dec 18, 2003, 16:06:57     Thank you    Jonathan M. Prigot Dec 18, 2003, 17:38:19     Re: No 3.0?    Anil Wang Dec 18, 2003, 17:38:37     Congratulations and thanks!    Brian Wright Dec 18, 2003, 18:03:25     Re: Re: No 3.0?    eric Dec 18, 2003, 18:48:34     2.6 Compatible Apps - broken?    Marc Perkel Dec 18, 2003, 19:20:09     Re: 2.6 Compatible Apps - broken?    Frédéric L. W. Meunier Dec 18, 2003, 20:39:35     On my birthday too :)    Larry Johnson Dec 18, 2003, 20:59:49     Re: Re: No 3.0?    Kirk Dec 18, 2003, 21:04:13     Re: flaky disks ??    Zartan Dec 18, 2003, 21:36:50     Linux 2.6.0    Codifex Maximus Dec 18, 2003, 21:56:03     Thank you    george Dec 18, 2003, 22:01:19     thanks for the present    Zirong Wang Dec 18, 2003, 22:07:53     How long...    Christian Dec 18, 2003, 22:42:11     Downloaded, compiled and installed.    Brandioch Conner Dec 18, 2003, 22:55:20     Re: Christmas Present?    ELC Dec 18, 2003, 23:15:58     Good news..^^    Steven Shim Dec 19, 2003, 01:11:39     Re: Re: Christmas Present?    Threska Dec 19, 2003, 06:46:49     Re: flaky disks ??    Mike Fedyk Dec 19, 2003, 07:23:01     good!    alx Dec 19, 2003, 09:37:50     Nice Work!    Danilo Densa Dec 19, 2003, 12:08:49     why kernel-2.6.0?    mla Dec 19, 2003, 13:26:01     nice work! uh, ath64fx, how?    twallcx Dec 19, 2003, 13:35:30     Good    SEAL Dec 19, 2003, 13:52:06     Re: Re: 2.6 Compatible Apps - broken?    Jonathan M. Prigot Dec 19, 2003, 14:19:02     COMPATIBILITY    JDP Dec 19, 2003, 14:54:19     2.6 compatibility issues?    lebeziatnikov Dec 19, 2003, 16:31:38     Re: Congratulations and thanks!    mark Dec 19, 2003, 16:33:49     Re: Re: Congratulations and thanks!    Brian Wright Dec 19, 2003, 19:07:54     Re: why kernel-2.6.0?    Robby DS Dec 19, 2003, 20:06:58     Re: Good    Bojan Smojver Dec 20, 2003, 02:07:29     Re: COMPATIBILITY    joe Bravo Dec 20, 2003, 15:00:21     Re: No 3.0?    Jouni Dec 21, 2003, 00:45:02     It's to good to be true.    conceptx Dec 26, 2003, 19:31:19     Home | Search Talkbacks | Customize View    Top of Page   Enter your comments below: * Your Name: * Your Email Address: * Subject: CC: [will also send this talkback to an E-Mail address] * Comments: Tags allowed:<I>,<B> and <U>. See our talkback-policy for more about talkback content. Fields marked with * are required!