src/sys, branch upstream/2.0.5_cvsFreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=upstream%2F2.0.5_cvs1995-06-10T19:44:55ZThis commit was manufactured by cvs2svn to create tag1995-06-10T19:44:55Zcvs2svncvs2svn@FreeBSD.org1995-06-10T19:44:55Zurn:sha1:fbe312c9f723b704a542825383058d1a2eb63f94
'RELENG_2_0_5_RELEASE'.
This commit was manufactured to restore the state of the 2.0.5-RELEASE image.
Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.
Added a missing break which caused interface flag changes to panic the1995-06-09T18:12:09ZDavid Greenmandg@FreeBSD.org1995-06-09T18:12:09Zurn:sha1:d348442dd3672e3a8bf45ac2640539d9c8a376b5
machine.
Submitted by: Stefan Petri
1) SCSI_RESID_VALID was not getting set in xs->flags so even though the1995-06-09T18:06:53ZDavid Greenmandg@FreeBSD.org1995-06-09T18:06:53Zurn:sha1:64b0940b340e57507e904d46d0efbc3180243971
aic7xxx driver was doing the right thing, it was getting ignored by the
upper level scsi code. This may affect tape drives, so I consider this
a critical fix.
2) xs->status was not set to zero during the initialization of a command.
Although I don't think this should be the client's (ie the driver's)
responsibility, it seems that it currently is, so it needs to be cleared.
Without this change, the upper level scsi code will attempt to interpret
the sense information on every command complete (since xs->status is
usually left at 2, "check sense"). This gives a slight performance
increase, as well as stops fooling /sbin/scsi into thinking there was
an error on the command.
3) Document that we support the aic7850 controllers in the aic7870.c
header. Aic7870.c should probably become aic78xx.c sometime down the
road.
Submitted by: Justin Gibbs
Look only at the appropriate rtc clock/ram valid bit. The others are1995-06-09T03:29:17ZDavid Greenmandg@FreeBSD.org1995-06-09T03:29:17Zurn:sha1:307977af45e6cda4a6d3389cd9cb8122a0560a02
undefined and if they weren't 0, resulted in the sytem clock not being set.
Submitted by: Akira SAWADA
Return error if in_pcbladdr() fails. Not doing so could result in a panic1995-06-09T03:21:13ZDavid Greenmandg@FreeBSD.org1995-06-09T03:21:13Zurn:sha1:6ea0f35ef9d46a32638c061efe4b4733e05160e4
or unusual behavior under certain cicumstances.
Submitted by: Matt Dillon
Moved initialization of fdblk down a few lines so that tape is checked for1995-06-08T10:26:23ZDavid Greenmandg@FreeBSD.org1995-06-08T10:26:23Zurn:sha1:ca829154dae6e9b0ea7e013a189fb01835114d15
(and rejected) first. Fixes panic that results from fd->ft not being
initialized.
Submitted by: Joerg Wunsch
Backed out one part of rev 1.13. In this one case, two references to the1995-06-07T07:25:09ZDavid Greenmandg@FreeBSD.org1995-06-07T07:25:09Zurn:sha1:7f7d3a605224e44056ac74a5db8188223c56757e
vnode are gained, but only one reference to the object is gained. The
object reference is (correctly) lost by the nfsrv_vrele() at the exit
point of the nfsrv_link function.
The bug is easily seen by doing a standard "link" operation to a 2.0.5
server (ln foo bar). The system will immediately panic with "object
deallocated too many times".
This fixes the panic reported today by ohki@gssm.otsuka.tsukuba.ac.jp.
(will be) Reviewed by: John Dyson
Take ppp out of the GENERIC kernel to save space.1995-06-05T21:50:41ZJordan K. Hubbardjkh@FreeBSD.org1995-06-05T21:50:41Zurn:sha1:19e672d18edf9d40ae92980fdd76cdcf20571a14
We don't use it from GENERIC.
Removed eg driver, speaker, and vn devices to help reduce the size of the1995-06-05T17:15:42ZDavid Greenmandg@FreeBSD.org1995-06-05T17:15:42Zurn:sha1:9935f85660754fee5301ce2af7cd70a26529fda5
GENERIC kernel.
Reviewed by: Jordan Hubbard, Poul-Henning Kamp
Restore Andrew's change in rev 1.44 for t_timeout. I can't see how that1995-06-05T01:23:10ZDavid Greenmandg@FreeBSD.org1995-06-05T01:23:10Zurn:sha1:357a5ff6a8fe7de03b9060944363098521c33553
could have caused PR 445 unless the user specifically mis-configured
'comcontrol' in rc.serial. t_timeout is only set/cleared via the
TIOCSDRAINWAIT ioctl and defaults to 0.
Reviewed by: Andrew Chernov