Race Between Mir_close() And Mir_timer() Could Lead To Panic in NFS (Doc ID 1487369.1)

Last updated on JULY 11, 2017

Applies to:

Solaris SPARC Operating System - Version 10 10/08 U6 and later
Information in this document applies to any platform.

Symptoms

A system using NFS may panic with a stack similar to one these below.

   unix:panicsys+0x48
   unix:vpanic_common+0x78
   unix:panic+0x1c
   unix:trap+0x9e0
   unix:ktl0+0x48()
   trap data  type: 0x31 (data access MMU miss)
   <trap>unix:putnext+0x60
   rpcmod:mir_svc_policy_notify+0x74
   rpcmod:mir_timer
   genunix:callout_list_expire+0x5c
   genunix:callout_expire+0x1c
   genunix:callout_execute+0xc
   genunix:taskq_thread+0x1a4
   unix:thread_start+0x4()

or perhaps:

   unix:panicsys+048
   unix:vpanic_common+0x78
   unix:panic+0x1c
   unix:mutex_enter
   rpcmod:mir_clnt_idle_do_stop+0x10
   rpcmod:clnt_dispatch_notifyall+0x158
   rpcmod:mir_timer
   genunix:callout_list_expire+0x5c
   genunix:callout_expire+0x1c
   genunix:callout_execute+0xc
   genunix:taskq_thread+0x3b8

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms