PROBLEM: (QAR 60606, QAR 58912) (Patch ID: OSF435-425257) ******** This patch fixes a problem with AdvFS in which the following panic occurs: clone: str_stripe_clone err A sample stack trace is as follows: 0 boot() 1 panic() 2 advfs_sad() 3 clone() 4 bs_cow() 5 bmtr_update_rec() 6 fs_update_stats() 7 msfs_close() 8 vn_close() 9 closef() 10 close() 11 syscall() 12 _Xsyscall() PROBLEM: (QAR 59953, QAR 59419) (Patch ID: OSF435-425249) ******** This patch fixes a problem that occurs on AdvFS systems. The system will panic with the following error message: malloc_overflow: guard space corruption A sample stack trace is as follows: 6 panic() 7 malloc_debug() 8 free() 9 _ms_free() 10 free_dmntbl_setname() 11 msfs_real_syscall() 12 msfs_syscall() 13 syscall() 14 _Xsyscall() PROBLEM: (57426, 57492, 57450, ECP EALC8003, 61553, BCGM501VR, HPAQ41HC8, 62831, 61388, 62617, 62299, 51568, HPAQ60W1F, 63703, 63686) (Patch ID: OSF435-020) ******** This patch fixes several problems: This patch fixes a problem with the chfsets command. When a root user exceeded the fileset quota (which root is allowed to do), the chfsets command reported negative values for the free and available blocks in the fileset. This patch fixes a problem with the AdvFS fs_write routine, which would mishandle partial writes after detecting an error. Now when the fs_write routine detects an error, it breaks out of the write page loop and decides either to exit immediately with an error (if no bytes have been written) or to commit the partial changes to disk and return the number of successfully-written bytes. This patch provides performance improvements for writes to AdvFS files which have had Atomic Write Data Logging enabled on them. Write performance improvements are for O_SYNC opens of such files and are realized for both local and NFS access. This patch fixes a problem with messages in system logs that reported AdvFS user and group quota limits. The messages were unclear: the user could not determine from them which users or groups were reaching the quota limits. Part of the problem was the term "inode," which is not an AdvFS entity. The term was replaced in the messages with "file." This patch fixes a problem in AdvFS, which causes a system panic when a truncate operation is performed on a file. The panic is: log half full Here's the stack trace: > 0 boot() ["../../../../src/kernel/arch/alpha/machdep.c":1890, ] 1 panic(s = 0xffffffff8bc3af98 = "release_dirty_pg: log half full") ["../../../../src/kernel/bsd/sub r_prf.c":834, 0xfffffc000028c024] 2 advfs_sad() ["../../../../src/kernel/msfs/bs/bs_misc.c":556, ] 3 release_dirty_pg() ["../../../../src/kernel/msfs/bs/ms_logger.c":2005,] 4 lgr_writev_ftx() ["../../../../src/kernel/msfs/bs/ms_logger.c":1576, ] 5 log_donerec_nunpin()["../../../../src/kernel/msfs/bs/ftx_routines.c":2825, ] 6 ftx_done_urdr() ["../../../../src/kernel/msfs/bs/ftx_routines.c":1246, ] 7 ftx_done_u() ["../../../../src/kernel/msfs/bs/ftx_routines.c":1060, ] 8 bmt_link_mcells() ["../../../../src/kernel/msfs/bs/bs_bmt_util.c":3770, ] 9 odm_create_xtnt_map() ["../../../../src/kernel/msfs/bs/bs_extents.c":1707, ] 10 dealloc_stg() ["../../../../src/kernel/msfs/bs/bs_stg.c":6388, ] 11 remove_stg() ["../../../../src/kernel/msfs/bs/bs_stg.c":5897, ] 12 stg_remove_stg_start() ["../../../../src/kernel/msfs/bs/bs_stg.c":5743, ] 13 bf_setup_truncation() ["../../../../src/kernel/msfs/bs/bs_access.c":4189, ] 14 msfs_setattr() ["../../../../src/kernel/msfs/osf/msfs_vnops.c":1725, ] 15 vtruncate() ["../../../../src/kernel/vfs/vfs_syscalls.c":3488, ] 16 ftruncate() ["../../../../src/kernel/vfs/vfs_syscalls.c":3418, ] 17 syscall() ["../../../../src/kernel/arch/alpha/syscall_trap.c":627, ] 18 _Xsyscall() ["../../../../src/kernel/arch/alpha/locore.s":1409, ] This patch fixes the following problems in AdvFS: 1.) AdvFS does not return an error when a user opens a file in O_SYNC mode and power is lost on the disk drive. 2.) A locking error in the AdvFS fs_write() routine. This patch fixes a problem in AdvFS locking code which causes the following panic: kernel memory fault The stack trace is listed below: 0 boot() 1 panic() 2 trap() 3 _XentMM() 4 bs_pinpg_clone() 5 bs_pinpg_ftx() 6 rbf_pinpg() 7 alloc_mcell() 8 bmt_alloc_prim_mcell() 9 new_mcell() 10 rbf_int_create() 11 rbf_create() 12 fs_create_file() 13 msfs_mkdir() 14 mkdir() 15 syscall() 16 _Xsyscall() This patch fixes two AdvFS problems: 1. An error message was misleading when a DIGITAL UNIX Version 4 system attempted to access a file domain created by DIGITAL UNIX Version 5. 2. A state field in an AdvFS data structure was initialized, but not maintained. PROBLEM: (QAR 61441,57532) (Patch ID: OSF435-025) ******** This patch fixes a problem with AdvFS performance. The patch provides a performance improvement to the msync system call when it is called for an AdvFS mmapped file. AdvFS msync processing is changed to only flush file dirty pages in the mmapped address range passed to the msync system call. Prior to this change, AdvFS would flush all dirty pages for the file. Threads which perform asynchronous I/O may modify the state of the associated buffer after the request gets enqueued onto the lazy queue. If the lazy queue gets bypassed, then it is possible for the I/O to complete before the issuing thread modifies the buffer. Once the I/O completes, the buffer could be reassigned. If the issuing thread still attempts to modify the buffer state, this can lead to a disk inconsistency and possibly a panic. PROBLEM: (BCSM91B1D, BCSM91NTC) (Patch ID: OSF435-058) ******** This patch corrects an AdvFS hang. PROBLEM: (MGO103758, DJOB91545, SOO101204) (Patch ID: OSF435-425513) ******** This patch fixes a problem where a system can panic with a kernel memory fault in overlay_xtnt_map() when any of the AdvFS migration utilities (migrate,balance, rmvol, or defragment) are run on an AdvFS domain. A typical stack trace looks like: _XentMM overlay_xtnt_map switch_stg migrate_normal mig_migrate bs_migrate msfs_real_syscall msfs_syscall PROBLEM: (QAR 67000, QAR 67281) (Patch ID: OSF435-100) ******** This patch fixes a problem in which a system using AdvFS can Kernel Memory Fault when truncating a frag file for a fileset that is not mounted. A typical stack trace would include: panic trap _XentMM lock_write bs_fragbf_thread PROBLEM: (QAR 67785, QAR 67460, CLDS MGO103947 ,BCSMC0NRQ, HPAQC0W3M, HPAQ10S59.) (Patch ID: OSF435-111) ******** This patch fixes a problem in which a system can hang because cleanup_closed_list() can go into a loop. PROBLEM: (QAR 65927 QAR 68369 CLD BCPMB0JP3) (Patch ID: OSF435-119) ******** Due to a problem with truncation during multiplication of 2 integers, the wrong offset was being calculated. This caused the update daemon to hang. PROBLEM: (HPAQC0B99) (Patch ID: OSF435-126) ******** This patch fixes a problem in AdvFS with auditing enabled. During a rmvol operation, the system can panic with a "kernel memory fault" with a stack trace that is similar to the following: > 0 boot() 1 panic(s = 0xfffffc00005b60a8 = "kernel memory fault") 2 trap() 3 _XentMM() 4 audit_rec_build() 5 audit_call() 6 msfs_audit_syscall() 7 msfs_real_syscall() 8 msfs_syscall() 9 syscall() 10 _Xsyscall() PROBLEM: (BCPM117VX, QAR 68804) (Patch ID: OSF435-134) ******** This patch fixes a problem where the "statfs" system call was reporting incorrect block usage on AdvFS filesets. As a side effect of this problem, the sendmail utility may sleep needlessly (waiting for space to become available). PROBLEM: (MGO103845, MGO103895) (Patch ID: OSF435-143) ******** This patch fixes an AdvFS Domain Panic that occurs with the following message on the console: "load_x_cache: bad status from bs_refpg of sbm" Example stack traces are as follows. Note: These are obtained from a system panic and not from the domain panic itself. 5 panic 6 advfs_sad 7 load_x_cache 8 sbm_find_space 9 alloc_from_bitmap 10 alloc_from_one_disk 11 stg_alloc_from_one_disk 12 alloc_copy_stg 13 migrate_normal 14 mig_migrate 15 bs_migrate 16 msfs_real_syscall 17 msfs_syscall 18 syscall 19 _Xsyscall OR 5 panic 6 advfs_sad 7 log_flush_sync 8 lgr_writev_ftx 9 log_donerec_nunpin 10 ftx_done_urdr 11 ftx_done_n 12 quota_deactivate 13 msfs_unmount 14 dounmount 15 unmount 16 syscall 17 _Xsyscall PROBLEM: (XIP100014, XIO100017) (Patch ID: OSF435-148) ******** This patch fixes a problem on systems using the AdvFS filesystem, where the system can panic with the panic string: "del_clean_mcell_list: no primary xtnt record". The stack trace will be similar to: advfs_sad del_clean_mcell_list bs_bfdmn_activate bs_bfdmn_tbl_activate fs_fset_get_info msfs_real_syscall msfs_syscall syscall _Xsyscall PROBLEM: (QAR 65739, 64945) (Patch ID: OSF435-066) ******** QAR 65739: The system can hang when inactivating an AdvFS domain. A domain is inactivated when the last fileset in the domain is unmounted or when a command like showfset is issued and no filesets in the domain are mounted. Inactivating a domain inactivates each volume in the domain. The fix allows more I/O to be started even though the volume is being inactivated. QAR 64945: Under some unusual circumstances (for example, mis administration or some ASE failovers), some volumes in a domain will not be specified in /etc/fdmns/. When this happens, activating the domain will change the state of the volumes specified in /etc/fdmns but not on other volumes that should belong to the domain. When the links in /etc/fdmns are restored, the domain will not be mountable because the volume states do not match. The fix prevents the state of the volumes from being changed unless all volumes in the domain conform to a prescribed set of requirements. PROBLEM: (QAR 64808, QAR 65442) (Patch ID: OSF435-067) ******** This patch fixes a panic in the AdvFS system. The panic has the following error message: lock_read: hierarchy violation The stack trace follows: 5 panic() 6 lock_fault() 7 lock_read() 8 u_map_fault() 9 vm_fault() 10 trap() 11 _XentMM() 12 nofault_bcopy() PROBLEM: (QAR 63709, EVT102691) (Patch ID: OSF435-074) ******** This patch changes the way some of the ADVFS advanced utilities (rmvol, migrate, balance and defragment) work internally. Under heavy I/O, the utilities could fail to migrate some files from one volume in an ADVFS domain to another. The errors for the customer seeing this problem will be similar to the following: balance: Balancing domain 'test_domain' balance: Can't move file /test/test.file balance: Error = E_INVOLUNTARY_ABORT (-1185) balance: Balanced domain 'test_domain' PROBLEM: (QAR 64393, 65683) (Patch ID: OSF435-081) ******** This patch fixes a problem whereby rmvol(8) did not correctly handle files that have more than one stripe on a volume and incorrectly assumed that there was only one stripe per volume. Informational messages similar to the following may be seen when running rmvol: rmvol: Striped file will be suboptimal. The rmvol utility may also fail with error messages similar to the following: rmvol: Error = EBAD_VDI (-1030) rmvol: Can't move file rmvol: Can't remove volume '' from domain '' PROBLEM: (QAR 58502,QAR 59094,QAR 61399,QAR 67023) (Patch ID: OSF435-094) ******** This patch provides the following fixes and enhancements to AdvFS: - AdvFS volumes were not setting the default I/O byte transfer size to the preferred size reported by the disk drives. This caused I/O consolidations to be smaller than is optimal for the disks. This patch now assigns the driver's preferred I/O transfer byte size to all new AdvFS volumes created with mkfdmn and addvol. - AdvFS chvol read and write transfer size range was increased. With this patch the transfer size range is now between 16 and 3276 512-byte blocks. - The read-ahead algorithm was modified to improve performance under certain conditions. The algorithm now sanity checks the number of pages that it would attempt to prefetch and apply the following restrictions when doing its calculations: o only read-ahead the number of pages remaining in the file o use a predetermined percentage of the buffer pool for use as read-ahead buffers. PROBLEM: (BCGM703PQ,BCPM70WFJ,HPAQ920JJ,BCGMC0NZ8,HPAQA225S,BCGM210JL, HPAQ20Z8V) (Patch ID: OSF435-150) ******** This patch fixes a problem where several processes accessing the same AdvFS file can hang with the following stack trace: thread_block ubc_lookup page_lookup bs_refpg_int bs_refpg fs_read msfs_read vn_read rwuio read syscall _Xsyscall PROBLEM (QAR 64688) (Patch ID: OSF435-113) This patch fixes kernel memory fault system panic in routine spec_relcaim. A sample stack trace is as follows: 0 stop_secondary_cpu() 1 panic() 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic() 6 trap() 7 _XentMM() 8 spec_reclaim() 9 vgone() PROBLEM (QAR 66544) (Patch ID: OSF435-113) This patch fixes a problem with executing the "file" command against a lat (BSD) special device in which the "file" process will hang. The system needs to be rebooted in order to remove the hung process. PROBLEM (QAR 67757) (Patch ID: OSF435-113) This patch fixes a problem on multiCPU systems where hangs can occur in the revoke system call when multiple threads attempt to call "revoke" at the same time. A sample stack trace is as follows: 0 thread_block() 1 clearalias() 2 revoke() 3 syscall() 4 _Xsyscall() PROBLEM: (QAR 66397) (Patch ID: OSF435-190) ******** This patch fixes a problem that caused the system to hang when AdvFS tests were run in lockmode 4. The fix allows xfer_xtnts_to_clone to recover after a crash. PROBLEM: (QAR 65628, 65698) (Patch ID: OSF435-191) ******** This patch fixes a problem with the AdvFS addvol command. Prior to this patch, if the advol command was interrupted and a second addvol command was run, the AdvFS domain would be rendered unusable. PROBLEM: (QAR 51397, QAR 58069, QAR 59749) (Patch ID: OSF435-197) ******** This patch fixes a problem that caused AdvFS system panics with a lock hierarchy violation. PROBLEM: (MGO104093,MGO104098,DSAT31W43, QAR 71350) (Patch ID: OSF435-210) ******** This patch corrects a problem in AdvFS which causes single-CPU systems to hang and causes multiple-CPU systems to panic with a "simple lock time limit exceeded" message specifying lock class name BfAccessTblMutex. This problem was originally reported when sys_check was being used to report on systems where there are more than 256 AdvFS filesets. The same problem could occur with any form of file access with that many filesets. PROBLEM: (QAR 70283) (Patch ID: OSF435-242) ******** This patch fixes the problem where the system panics if AdvFS detects an inconsistency in the free list of mcells that is kept on a per-volume basis in an AdvFS domain. The panic string seen with this panic is "alloc_mcell: bad mcell free list". PROBLEM: (UVO106494) (Patch ID: OSF435-257) ******** This patch fixes a problem where "update" takes too long to sync mmap files when using an AdvFS file system. PROBLEM: (QAR 65106) (Patch ID: OSF435-259) ******** This patch fixes the potential directory corruption,when system crashes during rmdir. PROBLEM: (QAR 66264) (Patch ID: OSF435-268) ******** This patch fixes the problem where the system panics whenever nextFlushSeq reaches the max.This fix allows nextFlushSeq (and other buffer lsn's) to roll over. PROBLEM: (QARS 70619 68822 72776 72391) (Patch ID: OSF435-271) ******** This patch fixes the following two problems in AdvFS: - When a "log half full" or "log full" problem occurs, an entire system will panic. With this patch, only the AdvFS domain will panic instead of bringing down the entire system. - The erorr message "ftx_bfdmn_recovery:bad record size\n N1 = 1" is received when the wordCnt, as returned by lgr_read, is not enough to hold the ftxDoneLRT record that preceeds each log record in a log page. This caused the log page trailer to overwrite the ftxDoneLRT record in a log record. This patch now leaves enough room to write a log header at the end of a log page. PROBLEM: (CLD ALC-08618, QAR 69288) (Patch ID: OSF435-274) ******** This patch corrects a problem where a "can't clear a bit twice" panic occurs after an unanticipated system crash and an improperly handled AdvFS recovery operation. Note: Although the system will have paniced with a "can't clear a bit twice" panic message, the AdvFS file domain is often still good. On the following reboot the system will not mount the affected AdvFS domain complaining that the domain is in an "inconsistent state". To recover the domain, use dbx to set the variable AdvfsFixUpSBM to 1: dbx dbx>a AdvfsFixUpSBM = 1 dbx>quit Then use the AdvFS verify utility to check the domain. If the recovery is successful, verify will report no errors and the domain will be mountable. Please remember to set AdvfsFixUpSBM back to zero when you have finished recovering the domain. PROBLEM: (MGO103900, QAR 71550) (Patch ID: OSF435-226) ******** This patch corrects a problem in AdvFS where unmounting a domain that is already in a panicked state could result in the following system panic message: log_flush_sync: pinpg error\n N1 = 5 Note: In this instance an I/O error (EIO = 5) caused the original domain panic. Stack trace: 6 advfs_sad() 7 log_flush_sync() 8 lgr_writev_ftx() 9 log_donerec_nunpin() 10 ftx_done_urdr() 11 ftx_done_n() 12 quota_deactivate() 13 msfs_unmount() Kernel Rebuild required. PROBLEM: (QAR 71271, QAR 71674) (Patch ID: OSF435-299) ******** This patch fixes a problem in AdvFS. AdvFS may skip filesystem recovery after aborted domain activation. PROBLEM: (QAR 67315, QAR 66478) (Patch ID: OSF435-306) ******** This patch fixes a problem in AdvFS. The system panics with the following error message: SMP Assertion failed A sample stack trace is listed below: 11 panic() 12 advfs_sad() 13 access_invalidate() 14 bfs_invalidate() 15 bfs_dealloc() PROBLEM: (CFS.67765,QAR 72623) (Patch ID: OSF435-312) ******** This patch corrects a kernel memory fault that occurs when entering the "mount -o dual" command. 9 _XentMM() 10 bs_bfdmn_sweep() 11 bs_bfdmn_activate() 12 bs_bfdmn_tbl_activate() 13 bs_bfset_activate_int() 14 bs_bfset_activate() 15 advfs_mountfs() PROBLEM: (QARS 67026 67442) (Patch ID: OSF435-314) ******** This patch fixes a problem in which it prevents a system panic if str_stripe_clone returns an error. PROBLEM: (QAR 69023) (Patch ID: OSF435-315) ******** This patch fixes a problem where the close_one_int() function enables the MIGTRUNC lock unnecessarily. PROBLEM: (QAR 74075) ******** This patch fixes a problem that may cause panics to occur when msfs_getpage() receives an error return from fs_write_add_stg() when attempting to write to an AdvFS domain that is out of disk space. PROBLEM: ('QAR 74052, QAR 73883') (Patch ID: OSF435-352) ******** This patch fixes a problem in AdvFS. A fileset is busy when attempting to unmount giving an EBUSY error even though the fileset has no open files. PROBLEM: ('QAR 73692, QAR 69021, QAR 74011 ') (Patch ID: OSF435-384) ******** This patch fixes a problem in the AdvFS system. A panic occurs with the following error message: lock_read: hierarchy violation PROBLEM: (QAR 75161) (Patch ID: OSF435-392) ******** This patch fixes a situation in which a domain that is being recovered can cause a slight Advfs memory leak. The problem can possibly result in a system panic whenever a domain is recovered via the mount command. The panic is due to a memory corruption. PROBLEM: (DJOB71733) (Patch ID: OSF435-409) ******** This patch fixes a problem where a single cpu system using AdvFS can hang in cleanup_closed_list(). PROBLEM: (MGO67225A,TKTBA0006,BCSMA1GK5,EVT79308A,STLBB3923) (Patch ID: OSF435-422) ******** This patch corrects AdvFS problems involving clone filesets. The statfs syscall (used by df) was incorrectly returning zero blocks USED for clones. The read-ahead code was incorrectly passing up opportunities to do read-ahead on clone filesets, resulting in a large performance penalty. PROBLEM: (MGO05514A, QAR 73107) (Patch ID: OSF435-300) ******** This patch corrects two problems in AdvFS property list handling: 1) Creation of property lists entries in AdvFS filesets with no available mcells will result in kernel memory fault (kmf). Abbreviated stack: 17 _XentMM() 18 msfs_pl_pin_cur() 19 msfs_pl_create_rec() 20 msfs_pl_findhead_setdata() 21 msfs_pl_set_entry() 22 msfs_setproplist_int() 23 msfs_setproplist() 24 setproplist() 25 proplist_syscall() 26 syscall() 27 _Xsyscall() 2) The get_proplist_entry function (used to disassemble the property list buffer returned by the "getproplist" system call) returned incorrect name length on property list names longer than 127 characters. PROBLEM: (QAR 67156,QAR 61985,QAR 66890) (Patch ID: OSF435-332) ******** This patch fixes the AdvFS race between extending and reading subextent maps and avoids the panic occured in advfs bs_get_bf_xtnt_map code (qar 61985). This patch also fixes the race with removing storage causing kernel memory fault (qar 66890). QAR 61985:Panic occurred in advfs bs_get_bf_xtnt_map code. stack trace: ----------- (dbx) t > 0 boot(0x400000000, 0x4, 0xfffffc00007a7330, 0x0, 0x4) ["../../../../src/kernel/arch/alpha/machdep.c":2350, 0xfffffc0000590d74] 1 panic(s = 0xfffffc00006f0748) ["../../../../src/kernel/bsd/subr_prf.c":1163, 0xfffffc00002883f4] 2 hardclock(pc = 0xfffffc000052e7c8, ps = (unallocated - symbol optimized away)) ["../../../../src/kernel/bsd/kern_clock.c":1163, 0xfffffc000025a3f0] 3 _XentInt(0x2, 0xfffffc000052e7c8, 0xfffffc00006d5af0, 0xfffffc00081a4000, 0xc00000cd0052f94a) ["../../../../src/kernel/arch/alpha/locore.s":1487, 0xfffffc000058d0f4] 4 vdealloc() ["../../../../src/kernel/vfs/vfs_subr.c":1374, 0xfffffc000052e7c4] 5 vrele(vp = 0x1d9) ["../../../../src/kernel/vfs/vfs_subr.c":2370, 0xfffffc000052f984] 6 mntbusybuf(mountp = 0xfffffc0002c83540) ["../../../../src/kernel/vfs/vfs_bio.c":1509, 0xfffffc0000527ab4] 7 boot(0x0, 0xfffffc0009920700, 0xfffffc0000000000, 0x2c0000002c, 0x32) ["../../../../src/kernel/arch/alpha/machdep.c":2305, 0xfffffc0000590c7c] 8 panic(s = 0xfffffc000076c050) ["../../../../src/kernel/bsd/subr_prf.c":1248, 0xfffffc00002885e4] 9 trap(a0 = (...), a1 = (...), a2 = (...), code = 0xfffffc00003fcfb4, exc_frame = 0xffffffff8cfe3 538) ["../../../../src/kernel/arch/alpha/trap.c":1877, 0xfffffc0000598af8] 10 _XentMM(0x0, 0xfffffc00003fcfb4, 0xfffffc00006d5af0, 0xffffffff8096e008, 0x1) ["../../../../src/kernel/arch/alpha/locore.s":2091, 0xfffffc000058d594] 11 bs_get_bf_xtnt_map(0xffffffff8cfe37a8, 0xfffffc00021f4008, 0xfffffc0001fbfc08, 0xfffffc00021f40 20, 0x1) ["../../../../src/kernel/msfs/bs/bs_params.c":578, 0xfffffc00003fcfb0] 12 msfs_real_syscall(0xfffffc00021f4008, 0xfffffc0009e16a80, 0x0, 0x0, 0x0) ["../../../../src/kernel/msfs/bs/bs_misc.c":2809, 0xfffffc00003f8bfc] 13 msfs_syscall(0x0, 0x0, 0x0, 0x41, 0xfffffc00005962f0) ["../../../../src/kernel/msfs/osf/msfs_syscalls.c":145, 0xfffffc00002d103c] 14 syscall(0x20, 0xfffffc000023e8a1, 0x1, 0x13e2e3588136e, 0x0) ["../../../../src/kernel/arch/alpha/syscall_trap.c":718, 0xfffffc00005962ec] 15 _Xsyscall(0x8, 0x3ff8123da08, 0x3ffc05cbe00, 0x60003, 0x11fff7190) ["../../../../src/kernel/arch/alpha/locore.s":1796, 0xfffffc000058d354] QAR 66890:"invalid memory read access" in imm_page_to_sub_xtnt_map(): stack trace: ----------- 5 panic(0xfffffc0000ae6300, 0xfffffc0000775698, 0x0, 0x46, 0x29211) ["../../../../src/kernel/bsd/ subr_prf.c":804, 0xfffffc000028a498] 6 trap(a0 = (...), a1 = (...), a2 = (...), code = 0xfffffffeae0bf490, exc_frame = 0xfffffffeae0bf 388) ["../../../../src/kernel/arch/alpha/trap.c":1747, 0xfffffc0000576644] 7 _XentMM(0x0, 0xfffffc00003eb6c4, 0xfffffc00007cb0e0, 0x5cb0, 0xfffffc00d86ec908) ["../../../../ src/kernel/arch/alpha/locore.s":1736, 0xfffffc000056aed4] 8 imm_page_to_sub_xtnt_map(0x0, 0xfffffc00003eb6c4, 0xfffffc00007cb0e0, 0x5cb0, 0xfffffc00d86ec90 8) ["../../../../src/kernel/msfs/bs/bs_inmem_map.c":2290, 0xfffffc00003eb6c0] 9 x_page_to_blk(0xfffffffeae0bf548, 0x5cb0, 0xfffffffe00c5d3f0, 0x800100000001, 0x100000010) [".. /../../../src/kernel/msfs/bs/bs_stg.c":6113, 0xfffffc000040497c] 10 x_page_to_blkmap(0x2000, 0x0, 0xfffffffe00e259a4, 0x0, 0x0) ["../../../../src/kernel/msfs/bs/bs _stg.c":5836, 0xfffffc0000404718] 11 x_page_mapped(0x0, 0x2, 0xfffffc000000003d, 0x1, 0xfffffffeae0bf568) ["../../../../src/kernel/m sfs/bs/bs_stg.c":6189, 0xfffffc0000404a9c] 12 bs_frag_has_stg(bfSetH = struct { setH = 0x5cb0 dmnH = 0x0 }, fragId = struct { frag = 0x2e587 type = BF_FRAG_6K }) ["../../../../src/kernel/msfs/bs/bs_bitfile_sets.c":2166, 0xfffffc00003c7a80] 13 msfs_getattr(vp = 0x1, vap = 0xfffffffeae0bf648) ["../../../../src/kernel/msfs/osf/msfs_vnops.c ":1475, 0xfffffc000043d8cc] 14 pacl_vnperm(0x367c099f000ebbfa, 0x8003000ebbfa, 0x0, 0x2000, 0x0) ["../../../../src/kernel/sec/ sec_acl.c":614, 0xfffffc000024f2a8] 15 paclaccess(0x0, 0xfffffc00d234fc80, 0xfffffc000024f1bc, 0xfffffc00a2ef8800, 0x1) ["../../../../ src/kernel/sec/sec_acl.c":906, 0xfffffc000024f7c4] 16 sp_vnaccess(0xfffffc000024f1bc, 0xfffffc00a2ef8800, 0x1, 0x1, 0xfffffc000043d308) ["../../../.. /src/kernel/sec/sec_acl.c":579, 0xfffffc000024f1b8] 17 msfs_access(vp = 0xfffffc00a2ef8800, cred = 0xfffffc007f201c00) ["../../../../src/kernel/msfs/o sf/msfs_vnops.c":1251, 0xfffffc000043d304] 18 vn_open(0xfffffc000051a83c, 0xfffffffeae0bf8f0, 0xfffffc0000000003, 0xfffffffeae0bf840, 0xfffff ffeae0bf838) ["../../../../src/kernel/vfs/vfs_vnops.c":614, 0xfffffc00005271b4] 19 copen(0x0, 0x3, 0xfffffc00d1f3b880, 0xfffffc008bc2d220, 0xfffffffeae0bf8e0) ["../../../../src/k ernel/vfs/vfs_syscalls.c":2420, 0xfffffc000051a900] 20 open(0xfffffc00d1f3b880, 0xfffffc008bc2d220, 0xfffffffeae0bf8e0, 0x12, 0xfffffc0000573d28) [".. /../../../src/kernel/vfs/vfs_syscalls.c":2347, 0xfffffc000051a7cc] PROBLEM: ('QAR 73644') (Patch ID: OSF435-374) ******** This patch fixes a problem with making a msfs_putpage() call. The length argument may get its upper bits truncated which will result in an incorrect length calculation. PROBLEM: ('QAR 51449, QAR 70650') (Patch ID: OSF435-353) ******** This patch fixes a panic in AdvFS which can have the following error messages: panic (cpu 1): bs_cow_pg: pin clone err -OR- panic (cpu 1): bs_cow_pg: cannot get blkMap