OpenSS7 STREAMS Compatibility -- defects. 2008-10-31
$Id$
Copyright (c) 2001-2008 OpenSS7 Corporation.
Copyright (c) 1997-2000 Brian Bidulock
See the end for copying conditions (for this file).
6.5 Bugs
========
6.5.1 Defect Notices
--------------------
"OpenSS7 STREAMS Compatibility" could possibly contain unknown defects.
This is a "production" release. Nevertheless, some remaining unknown
defects could possibly be harmful. Validation testing has been
performed by the `OpenSS7 Project' and external entities on this
software for the set of systems listed in the release notes.
Nevertheless, the software might still fail to configure or compile on
other systems. The `OpenSS7 Project' recommends that you validate this
software for your target system before using this software. Use at
your own risk. Remember that there is NO WARRANTY.(1)
This software is production software. As such, it is stable on
validated systems but might still crash your kernel in unique
circumstances. Installation of the software on a non-validated
distribution might mangle your header files or Linux distribution in
such a way as to make it unusable. Crashes could possibly lock your
system and rebooting the system might not repair the problem. You can
possibly lose all the data on your system. Because this software
stands a chance of crashing your kernel, the resulting unstable system
could possibly destroy computer hardware or peripherals making them
unusable. You might void the warranty on any system on which you run
this software. YOU HAVE BEEN WARNED.
---------- Footnotes ----------
(1) See sections Disclaimer of Warranty and Limitation of Liability
under `GNU Affero General Public License',in the manual.
6.5.2 Known Defects
-------------------
With the exception of packages not originally created by the `OpenSS7
Project', the `OpenSS7 Project' software does not ship with known bugs
in any release stage except "pre-alpha". "OpenSS7 STREAMS
Compatibility" had no known bugs at the time of release.
6.5.3 Defect History
--------------------
This section contains historical bugs that were encountered during
development and their resolutions. This list serves two purposes:
1. It captures bugs encountered between releases during development
that could possibly reoccur (and the Moon is made of blue cheese).
It therefore provides a place for users to look if they encounter
a problem.
2. It provides a low overhead bug list between releases for
developers to use as a `TODO' list.
Bugs
.....
`008. 2008-10-19T19:57:41+0000'
mi_open_link() was not walking device lists correctly.
_*fixed*_ in `strcompat-0.9.2.7'.
`007. 2008-10-19T10:39:26+0000'
mi_open_link() was not returning the assigned device number in
devp when sflag was CLONEOPEN.
_*fixed*_ in `strcompat-0.9.2.7'.
`006. 2008-07-11T13:52:04+0000'
lis_alloc_sem() was not setting the supplied count against the
created semaphore, but was alway setting the semaphore to 1
(unlocked).
_*fixed*_ in `strcompat-0.9.2.7'.
`005. 2008-05-26T14:06:22+0000'
lis_register_strdev() was failing whenever nminor was greater than
zero or not an even multiple of 256. This was due to an error in
the logic checking for multiple majors. (Thanks to Omer Tunali
for reporting this bug.)
_*fixed*_ in `strcompat-0.9.2.7'.
`004. 2007-07-21T17:26:01-0600'
It was reported that, even with the fix below, validation test
suites for XEN kernels are failing. XEN kernels are, therefore,
not supported. (Thanks to Bryan Shupe at Flying J for reporting
this bug.)
_*noted*_ in `strcompat-0.9a.7.rc1'.
`003. 2007-07-21T17:22:10-0600'
It was reported that paddr_t is already defined in recent XEN
kernels, causing compile to fail for these kernels. (Thanks to
Bryan Shupe at Flying J for reporting this bug.)
_*fixed*_ in `strcompat-0.9a.7.rc1'.
A check was added to the configure script to check for the
existence of paddr_t.
`002. 2007-07-21T17:15:02-0600'
It was discovered that recent kernel on RHAS4 are defining
irq_handler_t but have the old 3 argument function template for
irq handlers. The detection logic assumed that if irq_hander_t
existed, that the newer 2 argument function template for irq
handlers were in effect. This caused builds to fail on these
RHAS4 kernels.
_*fixed*_ in `strcompat-0.9a.7.rc1'.
A check was added to the configure script to test whether the
irq_handler_t has the newer 2 argument template.
`001. 2007-01-12T11:40:15-0600'
A bug in the `mi_copyout(9)' function was discovered by
inspection. The function should complete the last stage of a
non-TRANSPARENT input-output control operation by returning an
`M_IOCACK(9)' message, but did not. This was fixed for release
`0.9.2.5'.
-----
=========================================================================
Copyright (c) 2001-2008 OpenSS7 Corporation
Copyright (c) 1997-2000 Brian Bidulock
All Rights Reserved.
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.
Permission is granted to copy and distribute modified versions of this
manual under the conditions for verbatim copying, provided that the
entire resulting derived work is distributed under the terms of a
permission notice identical to this one
Since the Linux kernel and libraries are constantly changing, this
manual page may be incorrect or out-of-date. The author(s) assume no
responsibility for errors or omissions, or for damages resulting from
the use of the information contained herein. The author(s) may not
have taken the same level of care in the production of this manual,
which is licensed free of charge, as they might when working
professionally.
Formatted or processed versions of this manual, if unaccompanied by the
source, must acknowledge the copyright and authors of this work.
-------------------------------------------------------------------------
U.S. GOVERNMENT RESTRICTED RIGHTS. If you are licensing this Software
on behalf of the U.S. Government ("Government"), the following
provisions apply to you. If the Software is supplied by the Department
of Defense ("DoD"), it is classified as "Commercial Computer Software"
under paragraph 252.227-7014 of the DoD Supplement to the Federal
Acquisition Regulations ("DFARS") (or any successor regulations) and
the Government is acquiring only the license rights granted herein (the
license rights customarily provided to non-Government users). If the
Software is supplied to any unit or agency of the Government other than
DoD, it is classified as "Restricted Computer Software" and the
Government's rights in the Software are defined in paragraph 52.227-19
of the Federal Acquisition Regulations ("FAR") (or any successor
regulations) or, in the cases of NASA, in paragraph 18.52.227-86 of the
NASA Supplement to the FAR (or any successor regulations).
=========================================================================
Commercial licensing and support of this software is available from
OpenSS7 Corporation at a fee. See http://www.openss7.com/
=========================================================================
vim: ft=README tw=72 nocindent nosmartindent formatoptions+=tcqlorn