Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 Jul 2023 13:14:20 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 272775] procfs "file" entry pointing to nothing?
Message-ID:  <bug-272775-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272775

            Bug ID: 272775
           Summary: procfs "file" entry pointing to nothing?
           Product: Base System
           Version: 13.2-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: pen@lysator.liu.se

I just noticed that one entry of /proc/<pid>/file which usually looks like a
symlink pointing to the real path of the process didn't point to anything?

# ps auxww|egrep win
root      3236    0.0  0.0   97940  104424  -  Ss   22:22       0:02.58
/liu/sbin/winbindd --daemon --configfile=3D/liu/etc/samba/smb.conf
...

# cat /var/samba/run/winbindd.pid=20
3236

# ls /proc/3236/
cmdline etype   fpregs  mem     notepg  regs    status
dbregs  file    map     note    osrel   rlimit

# /proc/3236/file -V
/proc/3236/file: Command not found.

# ls -l /proc/3236
total 0
-r--r--r--  1 root  wheel  0 Jul 28 15:00 cmdline
-rw-------  1 root  wheel  0 Jul 28 15:00 dbregs
-r--r--r--  1 root  wheel  0 Jul 28 15:00 etype

ls: /proc/3236/file: No such file or directory
lr--r--r--  1 root  wheel  0 Jul 28 15:00 file
-rw-------  1 root  wheel  0 Jul 28 15:00 fpregs
-r--r--r--  1 root  wheel  0 Jul 28 15:00 map
-rw-------  1 root  wheel  0 Jul 28 15:00 mem
--w-------  1 root  wheel  0 Jul 28 15:00 note
--w-------  1 root  wheel  0 Jul 28 15:00 notepg
-rw-------  1 root  wheel  0 Jul 28 15:00 osrel
-rw-------  1 root  wheel  0 Jul 28 15:00 regs
-r--r--r--  1 root  wheel  0 Jul 28 15:00 rlimit
-r--r--r--  1 root  wheel  0 Jul 28 15:00 status

Of all the processes listed in /proc, this was the only one displaying this
behavious. When I restarted winbindd the problem went away.

Is this the same/similar problem as with the fdescfs filesystem we've discu=
ssed
in issue 272127 regarding filesystem vnode cache?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272775-227>