From: Ulrich Drepper <drepper@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: ->pid in filesystem code
Date: Thu, 28 Aug 2003 12:12:38 -0700 [thread overview]
Message-ID: <3F4E5426.6050401@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I looked briefly through the filesystem code. That's all definitely out
of my league so I don't try to make a final call or change something.
Anyway, this is what I found, the owners of that code should probably
look at it. Filesystems not mentioned are fine. I've ignored uses of
- ->pid in print statements; it's ok, any maybe preferable, there.
cifs:
apparently uses current->pid to keep track of locking. This might
mean that the current implementation is actually getting things very
wrong, at least from the Unix semantics. Locking happens on process
basis. I count 11 uses of ->pid, all suspicious. Using this
filesystem with NPTL seems to be risky in the moment.
coda:
One use in upcall.c. Seems fishy if it is assumed that the code can
be executed by any process. If it is only meant to be used by the
userlevel part of CODA then it should be fine. Might be good to
add a comment, though.
intermezzo:
Wow, don't know where to start. A gazillion uses of ->pid. Some are
print statements but there are others where the value is assigned to
elements of some internal data structures. I think I would strongly
suggest to avoid this filesystem when using NPTL until it is clear
that there are no issues.
lockd:
In clntproc.c the ->pid value is used to generate some kind of token.
Again, the thread can go away and take the PID with it while the
process remains. Don't know whether this is a problem here.
nfs:
Should be ok. Only mentioned in nfsXproc.c where the PID of the
server is returned to the client.
umsdos:
The pid seems to be used for some kind of locking. Might be that
using ->pid is correct here. In that case it needs comments.
There rest seems to be fine. Including ext2/3 which use the ->pid value
for coloring.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/TlQm2ijCOnn/RHQRAmyWAKCBC+cPr3ebdoeiqpusTZPn6+3cVwCffBLS
6hWR3C2+8NKck8FxAAlZun8=
=9UyG
-----END PGP SIGNATURE-----
next reply other threads:[~2003-08-28 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 19:12 Ulrich Drepper [this message]
2003-08-29 8:17 ` ->pid in filesystem code viro
-- strict thread matches above, loose matches on Subject: below --
2003-08-29 7:05 Steve French
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F4E5426.6050401@redhat.com \
--to=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox