Re: rpc.lockd(8) seg faults on 5.2-RELEASE

On Feb 3, 2004, at 12:06, Don Lewis wrote:
>
> Probably not a NULL pointer because &ifl->filehandle will be the same
> value as (char *)ifl+offsetof(struct file_lock, filehandle), and
> LIST_FOREACH() will bail out when ifl is NULL.  It would be interesting
> to walk the lock list starting at nfslocklist_head and following the
> nfslocklist links so see if any of the link values look bogus.

hum, on my last core dump, nfslocklist_head->lh_first->le_next and 
le_prev are uninitialized pointers.

Other dumps have other results though, I'll look more into it tonight.

(using malloc.conf -> J)

(gdb) print *nfslocklist_head->lh_first
$3 = {nfslocklist = {le_next = 0xd0d0d0d0, le_prev = 0xd0d0d0d0},
   filehandle = {fh_fsid = {val = {-791621424, -791621424}}, fh_fid = {
       fid_len = 53456, fid_reserved = 53456,
       fid_data = '?' <repeats 16 times>}}, addr = 0xd0d0d0d0, client = {
     exclusive = -791621424, svid = 3503345872, oh = {n_len = 3503345872,
       n_bytes = 0xd0d0d0d0 <Address 0xd0d0d0d0 out of bounds>},
     l_offset = 15046755950319947984, l_len = 15046755950319947984},
   client_cookie = {n_len = 3503345872,
     n_bytes = 0xd0d0d0d0 <Address 0xd0d0d0d0 out of bounds>},
   client_name = '?' <repeats 1024 times>, nsm_status = -791621424,
   status = -791621424, flags = -791621424, blocking = -791621424,
   locker = -791621424, fd = -791621424}

Mvh,
Frode