[odc] Daily src changes for 2007-06-20
ODC
auto at squish.net
Thu Jun 21 07:00:01 BST 2007
OpenBSD src changes summary for 2007-06-20
==========================================
etc/etc.alpha/MAKEDEV etc/etc.alpha/MAKEDEV.md
regress/sbin sbin/disklabel
sbin/pfctl share/man
sys/arch/alpha/alpha sys/arch/alpha/include
sys/arch/amd64/amd64 sys/arch/amd64/include
sys/arch/arm/arm sys/arch/arm/include
sys/arch/aviion/aviion sys/arch/aviion/include
sys/arch/hp300/dev sys/arch/hp300/hp300
sys/arch/hp300/include sys/arch/hppa/conf
sys/arch/hppa/dev sys/arch/hppa/hppa
sys/arch/hppa/include sys/arch/hppa64/hppa64
sys/arch/hppa64/include sys/arch/i386/i386
sys/arch/i386/include sys/arch/landisk/landisk
sys/arch/luna88k/include sys/arch/luna88k/luna88k
sys/arch/m88k/m88k sys/arch/mac68k/include
sys/arch/mac68k/mac68k sys/arch/macppc/include
sys/arch/macppc/macppc sys/arch/mips64/mips64
sys/arch/mvme68k/include sys/arch/mvme68k/mvme68k
sys/arch/mvme88k/include sys/arch/mvme88k/mvme88k
sys/arch/mvmeppc/include sys/arch/mvmeppc/mvmeppc
sys/arch/powerpc/powerpc sys/arch/sgi/include
sys/arch/sgi/localbus sys/arch/sgi/sgi
sys/arch/sh/include sys/arch/sparc/dev
sys/arch/sparc/include sys/arch/sparc/sparc
sys/arch/sparc64/dev sys/arch/sparc64/include
sys/arch/sparc64/sparc64 sys/arch/vax/include
sys/arch/vax/mscp sys/arch/vax/vax
sys/arch/vax/vsa sys/arch/zaurus/dev
sys/dev sys/dev/ata
sys/dev/ic sys/dev/isa
sys/dev/pci sys/dev/raidframe
sys/kern sys/net
sys/nfs sys/scsi
sys/sys sys/ufs/ufs
usr.bin/cvs usr.bin/ftp
usr.sbin/pkg_add
== etc =============================================================== 01/07 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/etc
etc.alpha/MAKEDEV
~ etc.alpha/MAKEDEV
> Regen (miod@)
etc.alpha/MAKEDEV.md
~ etc.alpha/MAKEDEV.md
> alpha kernel have wsmux but not the actual devices; PR #5469 from janjaap
> (miod@)
== regress =========================================================== 02/07 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/regress
sbin
~ pfctl/pf80.in ~ pfctl/pf80.loaded
~ pfctl/pf80.ok ~ pfctl/pf80.optimized
~ pfctl/pfail51.in ~ pfctl/pfail51.ok
> Allow "log" for nat rules without "pass".
> OK henning@, ``passt scho'' markus@ (mpf@)
== sbin ============================================================== 03/07 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/sbin
disklabel
~ editor.c
> if a 4.2BSD partition falls partly within the area defined by the
> 'b' command, subtract the overlapping space from the free space.
> fixes weird free space calculation on hppa, where converted lif
> labels start at sector 1, but the 'b' area skips the first cylinder.
> ok millert@ (otto@)
pfctl
~ parse.y
> Allow "log" for nat rules without "pass".
> OK henning@, ``passt scho'' markus@ (mpf@)
== share ============================================================= 04/07 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/share
man
~ man4/pciide.4
> Add support for VIA CX700/VX700 IDE.
> Tested by jcs@ on a model 2 oqo. (jsg@)
~ man4/man4.i386/npx.4
> "an NPX", not "a NPX"; (jmc@)
~ man4/man4.i386/cpu.4 ~ man4/man4.i386/intro.4
~ man4/man4.amd64/intro.4 ~ man4/man4.hppa/intro.4
> do not try to have cpu.4 list everything - the bus pages already do that;
> instead, make sure cpu.4 pages point to intro.4;
> prompted by a diff from Stefan Sperling (jmc@)
~ man4/man4.hppa/ssio.4
> tweaks; (jmc@)
~ man4/com.4
> space required before punctuation; (jmc@)
~ man4/usb.4
> Reflect recent changes (UPACKED -> __packed).
> ok jmc. (mbalmer@)
~ man4/pci.4
> add ssio(4); (jmc@)
~ man4/lpt.4
> Update for lpt at ssio. (kettenis@)
~ man9/disk.9 ~ man9/disklabel.9
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
~ man8/man8.alpha/MAKEDEV.8
> Regen (miod@)
== sys =============================================================== 05/07 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/sys
arch/alpha/alpha
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
~ conf.c
> alpha kernel have wsmux but not the actual devices; PR #5469 from janjaap
> (miod@)
arch/alpha/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/amd64/amd64
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/amd64/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/arm/arm
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/arm/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/aviion/aviion
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/aviion/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/hp300/dev
~ hd.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
~ hd.c
> These drivers were abusing b_cylinder to store device-specific information
> in strategy(), and were reusing it in start().
> I first considered introducing a b_rawblkno field in struct buf, as has
> been
> done in NetBSD, to stop this abuse.
> However, it does not cost more to simply move the device-specific
> ``was-b_cylinder'' computation to the start() routine. Plus we get type
> fixes
> (daddr64_t) for free, although this does not really matter for these
> pedro-sized devices. Thus we do not need to grow struct buf for these
> devices which really ought to live in your Attic (and my machineroom, of
> course).
> hp300 HP-IB tested, vax mfm not, but the logic is the same. (miod@)
arch/hp300/hp300
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/hp300/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/hppa/conf
~ GENERIC ~ files.hppa
> lpt at ssio (kettenis@)
arch/hppa/dev
~ ssio.c
> lpt at ssio (kettenis@)
+ lpt_ssio.c
> Add file such that a kernel with lpt at ssio actually compiles. (kettenis@)
arch/hppa/hppa
~ vm_machdep.c
> In vunmapbuf(), explicitely remove mappings before invoking uvm_km_free().
> Even if the latter would end up removing the mappings by itself, it would
> do so using pmap_remove() because phys_map is not intrsafe; but some
> platforms use pmap_kenter_pa() in vmapbuf(). By removing the mappings
> ourselves, we can ensure the remove function used matches the enter
> function
> which has been used.
> Discussed and theoretical ok art@ (miod@)
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/hppa/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/hppa64/hppa64
~ vm_machdep.c
> In vunmapbuf(), explicitely remove mappings before invoking uvm_km_free().
> Even if the latter would end up removing the mappings by itself, it would
> do so using pmap_remove() because phys_map is not intrsafe; but some
> platforms use pmap_kenter_pa() in vmapbuf(). By removing the mappings
> ourselves, we can ensure the remove function used matches the enter
> function
> which has been used.
> Discussed and theoretical ok art@ (miod@)
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/hppa64/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/i386/i386
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/i386/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/landisk/landisk
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/luna88k/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/luna88k/luna88k
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/m88k/m88k
~ vm_machdep.c
> In vunmapbuf(), explicitely remove mappings before invoking uvm_km_free().
> Even if the latter would end up removing the mappings by itself, it would
> do so using pmap_remove() because phys_map is not intrsafe; but some
> platforms use pmap_kenter_pa() in vmapbuf(). By removing the mappings
> ourselves, we can ensure the remove function used matches the enter
> function
> which has been used.
> Discussed and theoretical ok art@ (miod@)
arch/mac68k/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/mac68k/mac68k
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/macppc/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/macppc/macppc
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/mips64/mips64
~ pmap.c
> Protect pool operations with splvm. (miod@)
~ interrupt.c
> Make sure IPL_CLOCK blocks device interrupts. (miod@)
~ vm_machdep.c
> In vunmapbuf(), explicitely remove mappings before invoking uvm_km_free().
> Even if the latter would end up removing the mappings by itself, it would
> do so using pmap_remove() because phys_map is not intrsafe; but some
> platforms use pmap_kenter_pa() in vmapbuf(). By removing the mappings
> ourselves, we can ensure the remove function used matches the enter
> function
> which has been used.
> Discussed and theoretical ok art@ (miod@)
~ interrupt.c
> Do not hardcode imask[] size when intializing it. (miod@)
arch/mvme68k/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/mvme68k/mvme68k
~ vm_machdep.c
> In vunmapbuf(), explicitely remove mappings before invoking uvm_km_free().
> Even if the latter would end up removing the mappings by itself, it would
> do so using pmap_remove() because phys_map is not intrsafe; but some
> platforms use pmap_kenter_pa() in vmapbuf(). By removing the mappings
> ourselves, we can ensure the remove function used matches the enter
> function
> which has been used.
> Discussed and theoretical ok art@ (miod@)
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/mvme88k/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/mvme88k/mvme88k
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/mvmeppc/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/mvmeppc/mvmeppc
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/powerpc/powerpc
~ vm_machdep.c
> In vunmapbuf(), explicitely remove mappings before invoking uvm_km_free().
> Even if the latter would end up removing the mappings by itself, it would
> do so using pmap_remove() because phys_map is not intrsafe; but some
> platforms use pmap_kenter_pa() in vmapbuf(). By removing the mappings
> ourselves, we can ensure the remove function used matches the enter
> function
> which has been used.
> Discussed and theoretical ok art@ (miod@)
arch/sgi/include
~ intr.h
> Make sure IPL_CLOCK blocks device interrupts. (miod@)
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/sgi/localbus
~ macebus.c
> Make sure IPL_CLOCK blocks device interrupts. (miod@)
~ macebus.c
> Do not hardcode imask[] size when intializing it. (miod@)
arch/sgi/sgi
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/sh/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/sparc/dev
~ xd.c ~ xy.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it.. except
> these two drivers. knock out that code for now to let it compile while
> miod gets his fix ready for these drivers. (deraadt@)
~ presto.c ~ fd.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/sparc/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/sparc/sparc
~ vm_machdep.c
> In vunmapbuf(), explicitely remove mappings before invoking uvm_km_free().
> Even if the latter would end up removing the mappings by itself, it would
> do so using pmap_remove() because phys_map is not intrsafe; but some
> platforms use pmap_kenter_pa() in vmapbuf(). By removing the mappings
> ourselves, we can ensure the remove function used matches the enter
> function
> which has been used.
> Discussed and theoretical ok art@ (miod@)
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/sparc64/dev
~ fd.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/sparc64/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/sparc64/sparc64
~ vm_machdep.c
> In vunmapbuf(), explicitely remove mappings before invoking uvm_km_free().
> Even if the latter would end up removing the mappings by itself, it would
> do so using pmap_remove() because phys_map is not intrsafe; but some
> platforms use pmap_kenter_pa() in vmapbuf(). By removing the mappings
> ourselves, we can ensure the remove function used matches the enter
> function
> which has been used.
> Discussed and theoretical ok art@ (miod@)
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/vax/include
~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/vax/mscp
~ mscp_disk.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/vax/vax
~ vm_machdep.c
> In vunmapbuf(), explicitely remove mappings before invoking uvm_km_free().
> Even if the latter would end up removing the mappings by itself, it would
> do so using pmap_remove() because phys_map is not intrsafe; but some
> platforms use pmap_kenter_pa() in vmapbuf(). By removing the mappings
> ourselves, we can ensure the remove function used matches the enter
> function
> which has been used.
> Discussed and theoretical ok art@ (miod@)
~ disksubr.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
arch/vax/vsa
~ hdc9224.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
~ hdc9224.c
> These drivers were abusing b_cylinder to store device-specific information
> in strategy(), and were reusing it in start().
> I first considered introducing a b_rawblkno field in struct buf, as has
> been
> done in NetBSD, to stop this abuse.
> However, it does not cost more to simply move the device-specific
> ``was-b_cylinder'' computation to the start() routine. Plus we get type
> fixes
> (daddr64_t) for free, although this does not really matter for these
> pedro-sized devices. Thus we do not need to grow struct buf for these
> devices which really ought to live in your Attic (and my machineroom, of
> course).
> hp300 HP-IB tested, vax mfm not, but the logic is the same. (miod@)
arch/zaurus/dev
~ zaurus_flash.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
dev
~ vnd.c ~ ramdisk.c
~ flashvar.h ~ flash.c
~ ccd.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
dev/ata
~ wd.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
dev/ic
~ osiop.c
> Better recovery when osiop goes nuts and spits
> osiop0: osiop_select while connected?
> in loops. Before returning from the interrupt handler, whack the chip.
> Unfortunately, this causes the few i/o which were queued to time out,
> but this is better than spinning and eventually panicing. (miod@)
dev/isa
~ mcd.c ~ fd.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
dev/pci
~ pcidevs
> Add a few VIA devices found in jcs' model 2 oqo. (jsg@)
~ pcidevs.h ~ pcidevs_data.h
> regen (jsg@)
~ pciide.c
> Add support for VIA CX700/VX700 IDE.
> Tested by jcs@ on a model 2 oqo. (jsg@)
dev/raidframe
~ rf_openbsdkintf.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
kern
~ subr_disk.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
net
~ pf.c
> Allow "log" for nat rules without "pass".
> OK henning@, ``passt scho'' markus@ (mpf@)
nfs
~ nfs_vfsops.c
> READDIRPLUS is v3 only, bail out if the mount isnt a v3.
> Prevents weird things from happening.
> ok tedu@,pedro@ (thib@)
scsi
~ cd.c ~ sd.c
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
sys
~ disk.h ~ disklabel.h
> b_cylinder does not need to be set on the callpath down into drivers.
> cpu_disklabel can go away, since nothing anymore needs to use it; ok miod
> (deraadt@)
ufs/ufs
~ ufs_vnops.c
> remove an XXX comment;
> Basically the reason why we dont do VOP_ABORTOP()'s in NFS
> is that sys_rename() actually handles the garbage collection
> of the pathname buffers, the calls in ufs are actually fluff
> too, but will be delt with later.
> ok pedro@ (thib@)
== usr.bin =========================================================== 06/07 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin
cvs
~ history.c
> Add missing `his' command alias. OK joris at . (xsa@)
ftp
~ ruserpass.c
> Add missing return value checks for strdup() andd fgetc().
> From Nicholas Marriott. Reminded by ray at .
> ok ray@ jaredy@ (moritz@)
== usr.sbin ========================================================== 07/07 ==
http://www.openbsd.org/cgi-bin/cvsweb/src/usr.sbin
pkg_add
~ pkg_info ~ pkg_mklocatedb
~ OpenBSD/CollisionReport.pm ~ OpenBSD/PackingList.pm
~ OpenBSD/SharedItems.pm ~ OpenBSD/SharedLibs.pm
> sprinkle code to deal gracefully with absent packing-lists.
> makes it easier for people to recover after a disk crash that
> leaves /var/db/pkg half-empty. (espie@)
~ pkg_add.1 ~ pkg_info.1
> mention https protocol, for which support was added recently.
> ok espie@ (steven@)
===============================================================================
More information about the odc
mailing list