Loading the semsys module with modload

Next, let's see what the ipcaccess () routine should have looked like. To be able to examine ipcaccess() on a live system, we have to first make sure the module /kernel/sys/semsys is already loaded. If it is not, then we must load it.

You must be root to load a module into the kernel.

 Hiya...  modinfo  grep semsys  Hiya...  su  Password:   #  modload /kernel/sys/semsys  #  modinfo  grep semsys  80 fc5b8000  1b0c  53   1  semsys (System V semaphore facility)   #  adb -k /dev/ksyms /dev/mem  physmem 1e05  ipcaccess/10i  ipcaccess:   ipcaccess:      save    %sp, -0x60, %sp                   sethi   %hi(0xf015cc00), %l5                   or      %l5, 0x294, %l5          ! ipcaccess_info                   ld      [%l5 + 0x10], %l1                   tst     %l1                   be,a    ipcaccess + 0x3c                   restore                   ld      [%l5 + 0xc], %l1                   ld      [%l5], %l0                   cmp     %l1, %l0  $q  #

As a reminder, here are the first 10 instructions of the ipcaccess() routine from the customer's system crash dump.

 ipcaccess:      save    %sp, -0x60, %sp                   ld      [%i2 + 0x4], %o0                   orcc    %g0, %o0, %g0                   bne,a   ipcaccess + 0x1c                   ld      [%i0], %o2                   ba      ipcaccess + 0x7c                   unimp   0x0                   cmp     %o0, %o2                   be,a    ipcaccess + 0x6c                   ld      [%i0 + 0x10], %i0

Well, that's a surprise! The routines are not the same! How can that be?