Robert Watson has started the automatic posting of open issues for the upcoming 5.1 and 5.2 releases. The list for 5.1 is automatically posted to -current every other day, with the most up-to-date version found here. The list is divided into the following four sections: "Must Resolve Issues", "Desired Features", "Documentation items that must be resolved", and "Areas requiring immediate testing".
The list for 5.2 is divided into the same four sections, and also is automatically posted to -current, however at this time only posted once every other week. Robert explains, "Obviously, this list will evolve as our notion of 5.2-RELEASE evolves. I've already had some very useful feedback on this, some new items, item tweaks, etc--I'd welcome further feedback." The most up-to-date version of the 5.2 list can be found here.
From: Robert Watson
To: current AT freebsd.org
Subject: 5.1-RELEASE TODO
Date: Thu, 15 May 2003 09:00:14 -0400 (EDT)
This is an automated bi-daily mailing of the FreeBSD 5.1 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.1R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.1.
FreeBSD 5.1 Open Issues
Open Issues
This is a list of open issues that need to be resolved for FreeBSD 5.1. If
you have any updates for this list, please e-mail re AT FreeBSD.org.
Must Resolve Issues for 5.1-RELEASE
+------------------------------------------------------------------------+
| Issue | Status | Responsible | Description |
|-------------------+-------------+---------------+----------------------|
| | | | Kris Kennaway |
| | | | reports that he has |
| | | | seen several unique |
| | | | panics on the alpha |
| | | | machines, but since |
| Spurious alpha | -- | -- | gdb -k doesn't work |
| panics | | | on alpha I haven't |
| | | | been able to get |
| | | | more than a DDB |
| | | | traceback. No-one |
| | | | has looked into |
| | | | them. |
|-------------------+-------------+---------------+----------------------|
| gdb -k doesn't | -- | Mark Peek | gdb -k doesn't work |
| work on alpha | | | on alpha |
|-------------------+-------------+---------------+----------------------|
| | | | There are reports of |
| | | | alignment problems |
| ipfw/ipfw2 | | | with ipfw and/or |
| alignment issues | In progress | Luigi Rizzo | ipfw2 on 64-bit |
| on alpha/sparc64 | | | platforms |
| | | | (specifically alpha |
| | | | and sparc64). |
|-------------------+-------------+---------------+----------------------|
| | | | Kris Kennaway |
| | | | reports high |
| | | | instability of |
| | | | 5.0-CURRENT on ia64 |
| ia64 stability | -- | -- | machines, such as |
| | | | the pluto* machines. |
| | | | These problems need |
| | | | to be fixed in order |
| | | | to get a successful |
| | | | package build. |
|-------------------+-------------+---------------+----------------------|
| | | | ia64 serial console |
| | | | support is not |
| | | | currently |
| | | Marcel | functional, and |
| ia64 sio support | In progress | Moolenaar, | requires a reworking |
| | | Warner Losh | of the sio support |
| | | | to improve platform |
| | | | independence and bus |
| | | | handling. |
|-------------------+-------------+---------------+----------------------|
| | | | Brian Feldman has |
| | | | submitted patches to |
| | | | improve the |
| | | | consistency of the |
| | | | pathnames passed |
| MAC Framework | | | into the MAC |
| devfs path fixes | In progress | Robert Watson | Framework devfs |
| | | | labeling entry |
| | | | points. These |
| | | | patches need to be |
| | | | thoroughly reviewed |
| | | | and tested, then |
| | | | merged. |
|-------------------+-------------+---------------+----------------------|
| | | | If a network device |
| | | | driver, possibly any |
| Panic on | | | driver, is linked |
| load/unload a | | | into the kernel and |
| kernel module for | Patch | Maxime | then loaded and |
| a driver already | submitted | Henrion | unloaded as a |
| statically linked | | | module, the kernel |
| into the kernel. | | | will panic. This has |
| | | | been observed with |
| | | | both if_dc and |
| | | | if_fxp. |
|-------------------+-------------+---------------+----------------------|
| | | | Currently, the MD |
| | | | elements of KSE are |
| | | | present only for the |
| | | | i386 platform, |
| | | | limiting use of KSE |
| | | | to the i386 |
| | | | platform. It is |
| | | | highly desirable to |
| KSE support for | | Jake | make KSE available |
| sparc64, alpha, | -- | Burkholder, | on non-i386 |
| ia64 | | --, -- | platforms for |
| | | | 5.1-RELEASE so that |
| | | | KSE can see more |
| | | | broad exposure, and |
| | | | the performance |
| | | | benefits of KSE can |
| | | | be visible to users |
| | | | of the 64-bit |
| | | | FreeBSD |
| | | | architectures. |
|-------------------+-------------+---------------+----------------------|
| | | | Update the run-time |
| rtld-elf | -- | Alexander | link editor (rtld) |
| thread-safety | | Kabaev | thread-safe with |
| | | | libpthread. |
|-------------------+-------------+---------------+----------------------|
| | | | rpc.lockd(8) |
| | | | client-side and |
| | | | server-side NFS |
| | | | locking appears to |
| | | | have a number of |
| | | | serious bugs which |
| rpc.lockd(8) | | | prevent NFS locking |
| stability | In progress | Robert Watson | from working |
| | | | properly in a number |
| | | | of common scenarios. |
| | | | These bugs must be |
| | | | resolved to ship |
| | | | 5.1-RELEASE. Work is |
| | | | underway to classify |
| | | | and track the bugs. |
+------------------------------------------------------------------------+
Desired Features for 5.1-RELEASE
+------------------------------------------------------------------------+
| Issue | Status | Responsible | Description |
|----------------+-----------+----------------+--------------------------|
| | | | A.out support in the |
| a.out | | | base system was reduced; |
| toolchain port | -- | -- | the removed build chain |
| | | | components should be |
| | | | made into a port. |
|----------------+-----------+----------------+--------------------------|
| | | | Truss appears to contain |
| | | | a race condition during |
| | | | the start-up of |
| | | | debugging, which can |
| | | | result in truss failing |
| | | | to attach to the process |
| | | | before it exits. The |
| | | | symptom is that truss |
| | | | reports that it cannot |
| | | | open the procfs node |
| | | | supporting the process |
| | | | being debugged. A bug |
| Race | Errata | | also appears to exist |
| conditions in | candidate | Robert Drehmel | where in truss will hang |
| truss | | | if execve() returns |
| | | | ENOENT. A further race |
| | | | appears to exist in |
| | | | which truss will return |
| | | | "PIOCWAIT: Input/output |
| | | | error" occasionally on |
| | | | startup. The fix for |
| | | | this sufficiently |
| | | | changes process |
| | | | execution handling that |
| | | | we will defer the fix to |
| | | | post-5.0 and consider |
| | | | this errata. |
|----------------+-----------+----------------+--------------------------|
| | | | Kris Kennaway reports |
| | | | deadlocks involving the |
| | | | use of nullfs in the |
| | | | bento environment: |
| | | | buildworld -j4 with src |
| | | | and obj mounted via |
| nullfs | -- | -- | nullfs; the gcc |
| deadlocks | | | processes eventually |
| | | | deadlocked in the ufs |
| | | | state. DDB traceback |
| | | | showed two different |
| | | | codepaths. I've just |
| | | | repeated this, so the |
| | | | bug still exists. |
+------------------------------------------------------------------------+
Documentation items that must be resolved for 5.1
+------------------------------------------------------------------------+
| Issue | Status | Responsible | Description |
|-----------------+-------------+--------------+-------------------------|
| | | | We now use OPIE instead |
| Documentation | | Christian | of S/Key. The handbook |
| rottage: S/Key | In progress | Brueffer | doesn't cover OPIE as |
| | | | well as it covers |
| | | | S/Key. |
|-----------------+-------------+--------------+-------------------------|
| | | | The hardware notes for |
| | | | ia64 needs some large |
| ia64 Hardware | -- | -- | infusions of text. They |
| Notes | | | probably haven't been |
| | | | synched with reality |
| | | | for awhile. |
|-----------------+-------------+--------------+-------------------------|
| | | | As BUSDMA is now the |
| | | | required driver API for |
| | | | DMA access in hardware |
| | | | device drivers as of |
| | | | 5.1-RELEASE, we need to |
| busdma man page | In progress | Hiten Pandya | make sure it's properly |
| | | | documented. A man page |
| | | | is in progress and |
| | | | needs to be |
| | | | appropriately reviewed |
| | | | and committed prior to |
| | | | the release. |
+------------------------------------------------------------------------+
Areas requiring immediate testing
+------------------------------------------------------------------------+
| Issue | Status | Responsible | Description |
|-----------------+-----------+-----------------+------------------------|
| | | | The 20030228 vendor |
| Fresh ACPI-CA | | | sources have been |
| import | -- | -- | imported. Further |
| | | | testing is |
| | | | appreciated. |
|-----------------+-----------+-----------------+------------------------|
| | | | During the install, |
| | | | the iir controller |
| | | | appears to correctly |
| | | | probe, but finds no |
| | | | disk devices. The card |
| | | | in question is an |
| | | | Intel srcu32 RAID |
| iir driver | | | controller with 32Mb |
| fails to probe | -- | -- | RAM, Firmware revision |
| disks | | | 2.33.01. Intel |
| | | | developers have |
| | | | released an update |
| | | | driver, which has |
| | | | recently been adapted |
| | | | and imported into |
| | | | 5-CURRENT, and must be |
| | | | tested. |
|-----------------+-----------+-----------------+------------------------|
| | | | PAE support allows the |
| | | | use of up to 64GB of |
| PAE support for | | | RAM on Pentium Pro and |
| i386 | -- | -- | above systems. Virtual |
| | | | addresses are still |
| | | | constrained to |
| | | | 32-bits. |
|-----------------+-----------+-----------------+------------------------|
| | | | The recently upgraded |
| | | | if_wi driver is more |
| | | | tuned to Prism |
| | | | hardware than to |
| if_wi problems | | | Lucent hardware, |
| on Lucent | -- | -- | resulting in system |
| hardware | | | lockups and poor |
| | | | performance when using |
| | | | Lucent hardware. These |
| | | | problems are believed |
| | | | to be fixed but more |
| | | | testing is welcome. |
|-----------------+-----------+-----------------+------------------------|
| | | | For 5.1-RELEASE, the |
| | | | default file system |
| | | | type for newly created |
| | | | file systems is UFS2 |
| | | | rather than UFS1. |
| UFS2 as | | | newfs(8) and |
| installation, | -- | Robert Watson | sysinstall(8) have |
| newfs default | | | been updated to use |
| | | | this new default. |
| | | | Testing to make sure |
| | | | all goes well after |
| | | | the change (committed |
| | | | on April 20, 2003) is |
| | | | vital. |
|-----------------+-----------+-----------------+------------------------|
| | | | Kris Kennaway reports |
| | | | mutex panics in wait4 |
| | | | in the bento |
| | | | environment: |
| wait4 | | | "Impossible" mutex |
| "impossible" | -- | Tim J. Robbins | panic in wait4() |
| mutex panic | | | (reported to -current |
| | | | a while ago). Believed |
| | | | to be related to (and |
| | | | fixed along with) |
| | | | uidinfo "impossible" |
| | | | panic below. |
|-----------------+-----------+-----------------+------------------------|
| | | | Kris Kennaway reports |
| | | | that there appears to |
| | | | be a resource leak of |
| | | | uidinfo reference |
| uidinfo | | | counts that is causing |
| "impossible" | -- | Tim J. Robbins | the gohan machines to |
| panic | | | panic after about 18 |
| | | | days of load. |
| | | | Tim J. Robbins has |
| | | | committed a fix that |
| | | | is believed to solve |
| | | | the problem. |
|-----------------+-----------+-----------------+------------------------|
| | | | Support for pluggable |
| | | | directory services |
| | | | using NSS, including |
| | | | adaptations of current |
| | | | directory services |
| NSSwitch | | | (local databases, |
| support | -- | Jacques Vidrine | NIS), and support for |
| | | | new services (LDAP, |
| | | | Active Directory, |
| | | | etc). This change has |
| | | | been committed, and |
| | | | requires broader |
| | | | testing. |
|-----------------+-----------+-----------------+------------------------|
| | | | Starting in late |
| | | | April, reports of a |
| | | | new UFS panic, "panic: |
| | | | ffs_blkfree: freeing |
| | | | free frag" began to |
| | | | pop up with a high |
| | | | frequency in some |
| | | | environments. This |
| | | | problem appears to |
| | | | have been associated |
| | | | with a bug introduced |
| | | | in the VM system that |
| | | | has now been resolved. |
| panic: | Patch | Alan L. Cox | Users who updated to a |
| ffs_blkfree | committed | | kernel between |
| | | | approximately May 1 |
| | | | and May 4 will want to |
| | | | run a full foreground |
| | | | fsck on all file |
| | | | systems to make sure |
| | | | that no remaining free |
| | | | space accounting |
| | | | errors exist. However, |
| | | | we should be on the |
| | | | lookout for any |
| | | | recurrence of this |
| | | | problem due to its |
| | | | serious nature. |
|-----------------+-----------+-----------------+------------------------|
| | | | Due to TCP state |
| | | | efficiency |
| | | | improvements in the |
| | | | TIMEWAIT state, it is |
| | | | now possible for the |
| | | | PCB socket pointer to |
| | | | be NULL in situations |
| TIMEWAIT panic | | | it previously wasn't. |
| for network | Patch | | As a result, TCP |
| labeled MAC | committed | Robert Watson | responses generated in |
| policy modules | | | the TIMEWAIT state |
| | | | lacked properly |
| | | | initialized MAC |
| | | | labels, resulting in |
| | | | panics for network |
| | | | labeled MAC policies. |
| | | | A fix has been |
| | | | committed, and needs |
| | | | more broad testing. |
+------------------------------------------------------------------------+
----------------------------------------------------------------------
freebsd-qa AT FreeBSD.ORG
Copyright (c) 1995-2003 The FreeBSD Project. All rights reserved.
Last modified: 2003/05/14 14:21:54From: Robert Watson
To: current AT freebsd.org
Subject: 5.2-RELEASE TODO
Date: Thu, 15 May 2003 10:00:13 -0400 (EDT)
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
The live version of this list is available at:
http://www.FreeBSD.org/releases/5.2R/todo.html
Automated mailing of this list will continue through the release of
FreeBSD 5.2.
FreeBSD 5.2 Open Issues
Open Issues
This is a list of open issues that need to be resolved for FreeBSD 5.2. If
you have any updates for this list, please e-mail re AT FreeBSD.org.
Must Resolve Issues for 5.2-RELEASE
+------------------------------------------------------------------------+
| Issue | Status | Responsible | Description |
|----------------------+----------+--------------+-----------------------|
| | | | KSE M:N threading |
| | | | support is reaching |
| | | Julian | experimental yet |
| | | Elischer, | usable status on i386 |
| Production-quality | In | David Xu, | for 5.1-RELEASE. M:N |
| M:N threading | progress | Daniel | threading should be |
| | | Eischen | productionable and |
| | | | usable on all |
| | | | platforms by |
| | | | 5.2-RELEASE. |
|----------------------+----------+--------------+-----------------------|
| | | | FAST_IPSEC currently |
| | | | cannot be used |
| | | | directly with the |
| | | | KAME IPv6 |
| | | | implementation, |
| | | | requiring an |
| | | | additional level of |
| | | | IP tunnel indirection |
| | | | to protect IPv6 |
| | | | packets when using |
| | | | hardware crypto |
| FAST_IPSEC and KAME | -- | -- | acceleration. This |
| compatibility | | | issue must be |
| | | | resolved so that the |
| | | | two services may more |
| | | | easily be used |
| | | | together. Among other |
| | | | things, this will |
| | | | require a careful |
| | | | review of the |
| | | | handling of mbuf |
| | | | header copying and |
| | | | m_tag support in the |
| | | | KAME IPv6 code. |
|----------------------+----------+--------------+-----------------------|
| | | | The FreeBSD KAME IPv6 |
| | | | code is now |
| | | | substantially dated |
| | | | with respect to the |
| | | | KAME vendor source. |
| KAME Synchronization | -- | -- | The FreeBSD Project |
| | | | needs to take |
| | | | initiative in driving |
| | | | the merge of new bug |
| | | | fixes, features, et |
| | | | al. |
|----------------------+----------+--------------+-----------------------|
| | | | Almost all process |
| | | | debugging tools have |
| | | | been updated to use |
| | | | non-procfs kernel |
| | | | primitives, with the |
| | | | exception of |
| | | | truss(1). As procfs |
| | | | is considered |
| | | | deprecated due to its |
| truss support for | -- | -- | inherent security |
| ptrace | | | risks, it is highly |
| | | | desirable to update |
| | | | truss to operate in a |
| | | | post-procfs world. |
| | | | Dag-Erling Smorgrav |
| | | | had "work in |
| | | | progress" patches |
| | | | that will need to be |
| | | | completed and |
| | | | committed. |
|----------------------+----------+--------------+-----------------------|
| | | | Apple's Darwin |
| | | | operating system has |
| | | | fairly extensive |
| Merge of Darwin | | | improvements to |
| msdosfs, other fixes | -- | -- | msdosfs and other |
| | | | kernel services; |
| | | | these fixes must be |
| | | | reviewed and merged |
| | | | to the FreeBSD tree. |
|----------------------+----------+--------------+-----------------------|
| | | | Simple |
| | | | machine-independent |
| | | | console framework, |
| | | | based roughly on |
| | | | wscons from NetBSD, |
| Machine-independent | In | Jake | which will provide |
| console support | progress | Burkholder | better console |
| | | | support across |
| | | | architectures. Also, |
| | | | device drivers for |
| | | | peripherals relevant |
| | | | to UltraSPARC. |
|----------------------+----------+--------------+-----------------------|
| | | | Many systems |
| | | | supporting POSIX.1e |
| | | | ACLs permit a minor |
| | | | violation to that |
| | | | specification, in |
| | | | which the ACL_MASK |
| | | | entry overrides the |
| ACL_MASK override of | In | Robert | umask, rather than |
| umask support in UFS | progress | Watson | being intersected |
| | | | with it. The |
| | | | resulting semantics |
| | | | can be useful in |
| | | | group-oriented |
| | | | environments, and as |
| | | | such would be very |
| | | | helpful on FreeBSD. |
|----------------------+----------+--------------+-----------------------|
| | | | Significant parts of |
| | | | the network stack |
| | | | (especially IPv4 and |
| | | | IPv6) now have |
| | | | fine-grained locking |
| | | | of their data |
| | | | structures. However, |
| | | | it is not yet |
| | | | possible for the |
| | | | netisr threads to run |
| | | | without Giant, due to |
| Fine-grained network | In | Jeffrey Hsu, | dependencies on |
| stack locking | progress | Seigo | sockets, routing, |
| without Giant | | Tanimura | etc. A 5.2-RELEASE |
| | | | goal is to have the |
| | | | network stack running |
| | | | largely without |
| | | | Giant, which should |
| | | | substantially improve |
| | | | performance of the |
| | | | stack, as well as |
| | | | other system |
| | | | components by |
| | | | reducing contention |
| | | | on Giant. |
|----------------------+----------+--------------+-----------------------|
| | | | Move ATA comments |
| | | | into requests, so |
| | | | that they can be |
| | | | linked together, |
| | | | centralize request |
| | | | queue management |
| ATA driver | | | permitting direct DMA |
| structural | In | So/ren | of ATA commands. |
| improvements, | progress | Schmidt | These architectural |
| MPsafety | | | changes will also |
| | | | facilitate complete |
| | | | MP-safety of the ATA |
| | | | driver suite, and |
| | | | dramatically improve |
| | | | support for Promise |
| | | | RAID controllers. |
|----------------------+----------+--------------+-----------------------|
| | | | Productionable |
| | | | support for the AMD64 |
| | | | platform. Currently, |
| | | | AMD64 runs fully in |
| | | Peter Wemm, | 32-bit emulation |
| Tier-1 Support for | In | David | mode, and boots to |
| AMD64 Hammer | progress | O'Brien | single-user in 64-bit |
| | | | mode. We expect full |
| | | | production support |
| | | | for the AMD64 |
| | | | architecture in |
| | | | 5.2-RELEASE. |
|----------------------+----------+--------------+-----------------------|
| | | | To properly support |
| | | | AMD64, a compiler |
| | | | upgrade is required; |
| | | | however, the new GCC |
| | | David | 3.3 has a substantial |
| | In | O'Brien | number of new |
| GCC 3.3 upgrade | progress | Alexander | warnings that will |
| | | Kabaev | disrupt application |
| | | | support, preventing |
| | | | inclusion in |
| | | | 5.1-RELEASE. This is |
| | | | a must-have for |
| | | | 5.2-RELEASE. |
+------------------------------------------------------------------------+
Desired Features for 5.2-RELEASE
+------------------------------------------------------------------------+
| Issue | Status | Responsible | Description |
|-------------+--------+---------------+---------------------------------|
| | | | Currently, MAC protections are |
| | | | enforced only on locally |
| | | | originated file system |
| | | | operations (VOPs), and not on |
| | | | RPCs generated via the NFS |
| MAC support | | | server. Improvements in NFS |
| for NFS | -- | Robert Watson | server credential handling are |
| Server | | | required to correct this |
| | | | problem, as well as the |
| | | | introduction of new entry |
| | | | points to properly label NFS |
| | | | credentials and perform |
| | | | enforcement properly. |
|-------------+--------+---------------+---------------------------------|
| | | | All PCI drivers must use busdma |
| No busdmsa | | | for DMA; no use of vtophys() |
| PCI drivers | -- | -- | will be permitted for any |
| | | | recent device driver. ISA |
| | | | drivers may be exempt. |
+------------------------------------------------------------------------+
Documentation items that must be resolved for 5.2
+------------------------------------------------------------------------+
| Issue | Status | Responsible | Description |
+------------------------------------------------------------------------+
Testing focuses for 5.2-RELEASE
+------------------------------------------------------------------------+
| Issue | Status | Responsible | Description |
+------------------------------------------------------------------------+
----------------------------------------------------------------------
freebsd-qa AT FreeBSD.ORG
Copyright (c) 1995-2003 The FreeBSD Project. All rights reserved.
Last modified: 2003/05/09 20:13:19
From: Robert Watson
Subject: Re: 5.2-RELEASE TODO
Date: Thu, 15 May 2003 14:31:21 -0400 (EDT)
Obviously, this list will evolve as our notion of 5.2-RELEASE evolves.
I've already had some very useful feedback on this, some new items, item
tweaks, etc--I'd welcome further feedback. Any substantial discussion of
feature goals should be moved to arch@.
Changes to the list will be visible on the web site about every 12 hours,
but you can also check the list straight out of the www tree and locally
generate the html to look at. We're going to keep the 5.2-RELEASE todo
list posting every two weeks for now, and once we get closer to the
5.2-RELEASE date we'll bump it up.
Thanks,
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
robert AT fledge.watson.org Network Associates Laboratories